Bug 590021 - smbclient segfaults when connecting to rhel5 samba server
smbclient segfaults when connecting to rhel5 samba server
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: samba (Show other bugs)
All Linux
high Severity high
: rc
: ---
Assigned To: Guenther Deschner
: Regression
Depends On:
Blocks: 580448
  Show dependency treegraph
Reported: 2010-05-07 10:29 EDT by Ales Zelinka
Modified: 2010-11-11 09:55 EST (History)
2 users (show)

See Also:
Fixed In Version: samba-3.5.2-58.el6
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-11-11 09:55:54 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
backtrace (7.34 KB, text/plain)
2010-05-07 10:32 EDT, Ales Zelinka
no flags Details
coredump (1.38 MB, application/octet-stream)
2010-05-07 10:35 EDT, Ales Zelinka
no flags Details

  None (edit)
Description Ales Zelinka 2010-05-07 10:29:59 EDT
Description of problem:
$ smbclient '\\\share' -U guest% -c ls
Domain=[WINLANDG] OS=[Unix] Server=[Samba 3.0.28-1.el5_2.1]
Server not using user level security and no password supplied.
Segmentation fault (core dumped)

This works well with smbclient from rhel5.

Version-Release number of selected component (if applicable):

	workgroup = WINLANDG
	security = SHARE
	passdb backend = tdbsam
	path = /var/lib/samba-share
	read only = No
	guest ok = Yes
Comment 1 Ales Zelinka 2010-05-07 10:32:02 EDT
Created attachment 412364 [details]
Comment 2 Ales Zelinka 2010-05-07 10:35:36 EDT
Created attachment 412365 [details]
Comment 3 Dmitri Pal 2010-05-10 10:13:38 EDT
Already fixed upstream.
Comment 7 releng-rhel@redhat.com 2010-11-11 09:55:54 EST
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.

Note You need to log in before you can comment on or make changes to this bug.