Dear Maintainer,
* What led up to the situation?
I need to use ksu to allow some users to access some accounts within
my network. Since their homes are in a NFS export, I cannot use the
~luser/.k5login approach.
* What exactly did you do (or not do) that was effective (or
ineffective)?
I have updated the krb5-user version to the testing one and it does
not solve the problem. I read the source code and the correct
behavior seems to be there as well.
* What was the outcome of this action?
It does not work. ksu showed the prompt to type password despite the
k5login_directory configuration.
* What outcome did you expect instead?
To login automaticaly just like it does with the ~luser/.k5login
setup.
Thank you for your hard work!
Will> I have updated the krb5-user version to the
Will> testing one and it does not solve the problem. I read the
Will> source code and the correct behavior seems to be there as
Will> well.
That question is asking how you configured k5login_directory.
What krb5.conf did you put it in, what section of krb5.conf.
How did you confirm it worked with something other than ksu.
As an example testing with ssh is likely to work better.
First, test with ssh to confirm .k5login with a local home directory
works.
Then configure k5login_directory and confirm that works with ssh.
Then describe that configuration and that it doesn't work with ksu.
Assuming this issue is ksu-specific, I suspect this probably has something to do with secure profile or some
of the things ksu does because it is setuid.