-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 10/09/2013 12:20 PM, Chris Hartman wrote:
Well, in a related development, it appears there is a hardware
issue with the testing PC- bad hard disk. Will replace, reinstall
OS, and re-test.
However, there is definitely a case sensitivity issue happening.
My other hosts only have an issue when logging in with Guest as
opposed to guest. Guest causes /home/guest to be created despite
what's in the unixHomeDirectory attribute; then I'm always dropped
in / because "Could not chdir to home directory /tmp/Guest: No such
file or directory." I imagine this because sssd is lowercasing
usernames but PAM isn't? "getent passwd guest" always returns the
same result:
guest:*:1596000501:1596000514:Guest:/tmp/Guest:/bin/bash
Hmm, maybe I misunderstood something here. I just re-read in your
original mail that this home directory was specified in LDAP, not as
part of the fallback_homedir processing. So that makes sense for why
it's leaving it capitalized; we always take that string from LDAP
literally, regardless of case-sensitive operation.
So if that's the case, I'm somewhat at a loss for why it would be
creating /home/guest at all (instead of what's in the passwd entry,
which is /tmp/Guest and is therefore the directory that the shell
tries to use).
Can you show me *exactly* what 'getent passwd Guest' returns and then
also what 'getent passwd guest' shows on the same system? They are
*supposed* to have identical output, whatever that output ends up being.
However, I suspect that this is going wrong somewhere. I really need
to see those two outputs side-by-side, please.
If I login in with guest, everything works as expected (after the
cache is cleared). It seems strange that I'm even allowed to auth
with both guest and Guest. Shouldn't one fail? Is this a bug or
feature?
When you log in as 'guest', what is the output of "echo $HOME"?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (GNU/Linux)
Comment: Using GnuPG with Thunderbird -
http://www.enigmail.net/
iEYEARECAAYFAlJX8OcACgkQeiVVYja6o6MOEACeL479v5eLIcWM40ksjU80aMuI
uOIAoKIQtkz/XEMP5i53X1injirir/lX
=bZJh
-----END PGP SIGNATURE-----