dealing with usernames containing whitespace

[Raymond Lillard]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



> On Tue, 2007-01-30 at 13:27 -0600, Gerald (Jerry) Carter wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Background: account names with whitespace such as "AD\Space Kadet"
>> cause failures in various shell scripts, initialization files,
>> Gnome, etc... because of the assumption that the IFS in base is
>> whitespace.  This patch introduces the 'winbind replacement character'
>> parameter which maps names like "Space Kadet" to "Space_Kadet".
>>
>> For example:
>>
>> $ ssh -l "ad\space kadet" localhost
>> Password:
>> Last login: Tue Jan 30 12:51:53 2007 from localhost


simo wrote:
> I think we need something to "fix" the problem, but I am not sure why
> you need something configurable, wouldn't it be less prone to misuse to
> have a parameter named something like:
>  winbind normalize names = yes/no
>
> This parameter always lower cases names and substitutes spaces with
> underscores* ?
>
> I like flexibility, but I don't like that much the winbind separator
> thing for example, where some users use \ others + and others even more
> strange ones, it gives us for more confusion than flexibility IMO.


What about Win users that put "_" in the file name?

I have trained "most" of my users to not put spaces
and other punctuation chars in file names.  I'd not
like to explain to those kind souls (who actually
listen to me) why their "_"s keep disappearing.

What about using a colon, which I believe is disallowed
in Windows, but allowed in Unix?

Regards,
Ray







-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFwAPUW6j0KQLSyTQRAllXAJ4tsCx8eBAYyrH2wpxh4JUKLJLfdACfc84z
bb6tpNtz66sZhv9A/aF1/S4=
=YA7h
-----END PGP SIGNATURE-----