Bug 115332

Summary:	smbpasswd removes all user descriptions from smbpasswd file if user is deleted
Product:	Red Hat Enterprise Linux 3	Reporter:	David Lawrence <dkl>
Component:	samba	Assignee:	Simo Sorce <ssorce>
Status:	CLOSED WONTFIX	QA Contact:	David Lawrence <dkl>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3.0	CC:	samba-bugs-list
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:	2007-10-19 19:30:13 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:

Description David Lawrence 2004-02-10 21:41:38 UTC

Description of problem:
When migrating from /etc/passwd to a smbpasswd file using
mksmbpasswd.sh, it places the user description as the last slot on
each line. When performing other actions such as enabling/disabling,
changing passwords, etc. the values are left untouched. When you
delete a user using the -x <username> switch, it removes the user
description from each line. You can see this by viewing the smbpasswd
file in a text editor. Funny though if you do a pdbedit -v <username>
it still shows the desc so it must be pulling it from /etc/passwd if
the desc field in smbpasswd is blank.


Version-Release number of selected component (if applicable):
samba-3.0.2-4.3E

Comment 1 Simo Sorce 2007-10-15 21:52:26 UTC

This seem to be a very old bug, but I spotted it only today.
If mksmbpasswd.sh does that, it is wrong, the smbpasswd file syntax has no place
for the user description.

Comment 2 RHEL Program Management 2007-10-19 19:30:13 UTC

This bug is filed against RHEL 3, which is in maintenance phase.
During the maintenance phase, only security errata and select mission
critical bug fixes will be released for enterprise products. Since
this bug does not meet that criteria, it is now being closed.
 
For more information of the RHEL errata support policy, please visit:
http://www.redhat.com/security/updates/errata/
 
If you feel this bug is indeed mission critical, please contact your
support representative. You may be asked to provide detailed
information on how this bug is affecting you.