Bug 2318 - Setting non-ascii password with LDAP backend works wrong
Setting non-ascii password with LDAP backend works wrong
Product: Samba 3.0
Classification: Unclassified
Component: Extended Characters
x86 Linux
: P3 normal
: none
Assigned To: Volker Lendecke
Samba QA Contact
Depends on:
  Show dependency treegraph
Reported: 2005-02-07 06:57 UTC by Robin Rosenberg
Modified: 2005-02-18 07:21 UTC (History)
0 users

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Robin Rosenberg 2005-02-07 06:57:26 UTC
If I set a password with non-ascii characters from windows it will work in  
windows, but not linux.  
The Linux boxes, inkluding the samba server (PDC) runs ISO-8859-1 and the 
conversion works fine in filenames etc. If I set the password using 
smbldap-passwd I can  use that password both in windows and in PAM-enabled apps 
and the LDAP-enabled ones I use. Setting the passsword from windows work in 
windows only. 
If I figure out the UTF-8 encoding of the password I can log in ISO-8859-1 
Linux apps by entering those character codes.
Comment 1 Gerald (Jerry) Carter 2005-02-17 08:36:35 UTC
volker, could perhaps you or guether test this when 
you get some time?  Thanks.
Comment 2 Björn Jacke 2005-02-18 04:08:24 UTC
there's no way to make this work, if you want non-ASCII characters in passwords,
you *need* to switch to UTF-8 on your Linux box because keyboard input needs to
be UTF-8, when you type username/password.
Comment 3 Robin Rosenberg 2005-02-18 05:53:10 UTC
Why? the ISO-Latin<>UTF-8 conversion works everywhere else. Why not for    
As I see it the UNIX charset has to be taken into account when  
passwords are stored via samba. 
Comment 4 Björn Jacke 2005-02-18 06:22:29 UTC
there is no such conversion in Linux (we are not talkin about samba here). If
you are in UTF-8 mode everything you type is UTF-8 and your terminal (hopefully)
knows how to display things right in UTF-8. If it's not in UTF-8 mode it is
still displayed right when your terminal is in non-UTF-8 mode. There is *no*
conversion here. One could of course introduce a conversion for your tty you are
using but that would break old passwords which are possibly non-ASCII,
non-UTF-8. If you want to use things like non-ASCII, you see here why
unification with UTF-8 and eleminating legacy 8bit locales is the only sane
thing to do.
Comment 5 Robin Rosenberg 2005-02-18 07:21:24 UTC
I see that the BUG is really everywhere else (pam,nss,app xxx,app yyy etc). 
Since stuff is stored as UTF-8 in samba it is quite logical the same applies to 
the password.  
And I agree going to UTF-8 is the sane thing in the future, but there are a     
number of other widely use apps here that need to get fixed first. Not that 
many so I'm hopeful. 
Thanks for helping me clear the fog.