I am trying to work out a system where a principle
*/[EMAIL PROTECTED]
has access to login to an account (guess which one) or su to that
account. I noticed a few years ago David Cross merged in a patch with
alpha support for wildcards in the .k5login file, but that's the last I
ever saw of
Michael,
Would you be interested in a pam authorisation (not authentication) module that
allowed you to store and manage this account name mapping information centrally in an
ldap directory (or other central repository of information) ? You would not need to
manage .k5login files in user home
=?ks c 5601-1987?B?s6rAsby6?= [EMAIL PROTECTED] writes:
Our system using kerberos-1.3.1
But 'rlogin -f' or 'rlogin -F' option occurs error!!!
example
[dev1:/tmp/krb5-1.3.1/doc] kinit -f skyhawk
Password for [EMAIL PROTECTED]:
[dev1:/tmp/krb5-1.3.1/doc] rlogin -F -x -l account hostname
