https://bugzilla.mindrot.org/show_bug.cgi?id=2764
Jedd <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #3 from Jedd <[email protected]> --- Hi Damien, Thanks for replying. I can't agree with you more. The situation that Arvindo is describing happens in Cygwin installed in Windows. Here's a simple explanation on what we've experienced... Initially, getpwnam will return the username in the case that it was supplied in e.g. "jediknight" will return "jediknight" or "Jedikight" will return "Jediknight" then several days or weeks after...getpwnam will start returning the username in a specific case e.g. "JEDIknight" which does not match active directory's (AD). If it matches active directory's then all is well since we will just consistently follow the case that was specified there. Weirder still it can change to "JediKnight", my guess is it has something to do with the Windows login but I don't exactly know how it happens. The thing is we don't generate "/etc/passwd" since we rely in Cygwin authenticating the user in AD. Although it is one workaround, the problem that we have with that is that if a new user was created by the client they might experience the issue again unless a new passwd is generated. The thing is we wanted to make it simple for them e.g. not generate passwd when they create a user. Anyways our idea is to have openssh have a flag to enable/disable username case sensitivity. By default it is case sensitive and it is applied under Cygwin ifdef. I created a pull request for you to review. Thanks a lot! Regards, Jedd -- You are receiving this mail because: You are watching the assignee of the bug. You are watching someone on the CC list of the bug. _______________________________________________ openssh-bugs mailing list [email protected] https://lists.mindrot.org/mailman/listinfo/openssh-bugs
