PAM not required for ticket retention

Posted by Pepijn Oomen Tue, 08 Mar 2005 18:52:51 GMT

After yet another day of changing sshd_config, pam configuration and an infinite amount of restarts of the SSH daemon, I found a more elegant way of actually getting a SSH enabled host to work as a basecamp for users that are not able to generate proper Kerberos tickets on their local workstation (that is, Windows 2000 users not connected to an AD domain).

Read more...

Posted in  | Tags , , ,

Using PAM with Kerberized SSH

Posted by Pepijn Oomen Mon, 07 Mar 2005 20:51:00 GMT

This one I actually only solved today, after struggling with a Debian Woody installation and comparing this with a previously installed Sarge. On Sarge I found that enabling the libpam-krb5 module did not seem to have the desired effect, that is, retaining the ticket given when the use authorizes itself. The provided upstream README says:

session module: This is complete (both functions just return success).

Read more...

Posted in  | Tags , , ,

The three-headed dog

Posted by Pepijn Oomen Sun, 06 Mar 2005 17:55:41 GMT

Traditionally Unix uses a passwd file to lookup user information. More recent versions use a separate shadow file for password storage. Although the passwords are not stored in cleartext, both methods do perform a security risk. On a reasonably large network this also provides a maintenance burden since all accounts need to be defined and maintained on each system.

Read more...

Posted in  | Tags , , ,