[Bug 17829] Re: swat rewrites fields incorrectly

[Jelmer Vernooij]

Re-opening - this bug is still open upstream, and while there have been
changes in this area of the code I'm pretty sure none of them have
affected the rewriting of fields in SWAT.

** Changed in: samba (Ubuntu)
       Status: Incomplete => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/17829

Title:
  swat rewrites fields incorrectly

Status in Samba:
  Confirmed
Status in “samba” package in Ubuntu:
  Confirmed

Bug description:
  When SWAT re-parses the config file after making changes, it parses and displays
  some of the fields incorrectly. This has a nasty side-effect: if you change a
  different field, and then click "Commit" again, the broken, incorrectly parsed
  values get committed to the smb.conf file, potentially breaking your Samba
  configuration.

  Here are the fields I've found with problems:

  All mode and mask fields assume that the field will be in the format 0###. If
  you want directories to be created with the sguid bit, for example, and enter in
  2777, it will commit this value to the conf file and then read it back in as
  02777, which breaks Samba's interpretation of that config entry.

  All entry fields (or, at the very least, admin users, read list, and write list)
  misinterpret user and group names with spaces in them. You should be able to put
  in entries like '@group name', and indeed, SWAT will translate it to that format
  if you put in something like @"group name", but when SWAT reads these back in,
  it translates them to: '@group, name'.

  There's probably others, but these are the ones I run into most
  frequently.

To manage notifications about this bug go to:
https://bugs.launchpad.net/samba/+bug/17829/+subscriptions