Bug 460274 - system-config-samba writes malformed lines into username mapping file
system-config-samba writes malformed lines into username mapping file
Product: Fedora
Classification: Fedora
Component: system-config-samba (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: Nils Philippsen
Fedora Extras Quality Assurance
: Triaged
Depends On:
  Show dependency treegraph
Reported: 2008-08-27 05:24 EDT by Nils Philippsen
Modified: 2009-12-18 01:20 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-12-18 01:20:04 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Nils Philippsen 2008-08-27 05:24:04 EDT
+++ This bug was initially created as a clone of Bug #460271 +++

Description of problem:
When user sets windows username to an empty string, system-config-samba writes line "username = " into the username mapping file. 

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

How reproducible:

Steps to Reproduce:
1.add user via system-config-samba (it will force you to add windows name)
2.edit the user, delete the windwos username, confirm
3.smbclient -L localhost -Usomeuser%hispassword
Actual results:
- malformed line with no windwos username is written into the username mappings file (/etc/samba/smbusers usually)
- error messages in samba logfile (/var/log/samba/smbd.log usually):
[2008/08/27 04:50:09, 0] smbd/map_username.c:map_username(149)
  Bad username map entry.  Unable to build user list.  Ignoring.

Expected results:
No line written to the file when windows username is set to an empty string.
Comment 1 Bug Zapper 2008-11-25 21:52:08 EST
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle.
Changing version to '10'.

More information and reason for this action is here:
Comment 2 Nils Philippsen 2009-04-27 09:37:18 EDT
fixed in git: a9d837c2501e757aafda366a825c91c6f3bc5f43
Comment 3 Bug Zapper 2009-11-18 07:38:26 EST
This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '10'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 10's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 10 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
Comment 4 Bug Zapper 2009-12-18 01:20:04 EST
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

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