Bug 117604

Summary: Comments listed as samba users in access lists
Product: [Fedora] Fedora Reporter: David Lawrence <dkl>
Component: system-config-sambaAssignee: Brent Fox <bfox>
Status: CLOSED RAWHIDE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: rawhide   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2004-03-05 21:29:15 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 114963    
Attachments:
Description Flags
smbpasswd none

Description David Lawrence 2004-03-05 18:46:05 UTC 
Description of problem:
When editing a shares permissions by clicking on the access tab and
then choosing "Only allow access to specific users", several users
show up in the user list which look like they are comment lines from
the smbpasswd database. So there are several users which are named "#"
or "# SMBPassword file". If you choose any of these "#" users just out
of curiousity, when viewing the generated smb.conf file, there is no
valid users line at all. But it is properly there if you only select
real users.

Version-Release number of selected component (if applicable):
system-config-samba-1.2.3-1
Comment 1 Brent Fox 2004-03-05 20:47:56 UTC 
Can you attach your smbpasswd file?
Comment 2 David Lawrence 2004-03-05 20:50:40 UTC 
Created attachment 98328 [details]
smbpasswd
Comment 3 David Lawrence 2004-03-05 20:52:34 UTC 
Additional note. This file is created with mksmbpasswd.sh when
creating a smbpasswd file from scratch using /etc/passwd. Normally if
you have an empty file and just add users with smbpasswd -a, then you
would not see
the commented lines. But regardless, I suppose the commented lines
could  just be skipped.
Comment 4 Brent Fox 2004-03-05 21:29:15 UTC 
Should be fixed in system-config-samba-1.2.4-1.  Thanks for your report.