After looking into this, I realize I misspoke. We're still using the
default RedHat EL 3.0's sshd, as well as Debian's vendor binaries. I
forgot that we want to be able to ssh to our machines if our fileservers
holding the packages aren't available because of
[your_favorite_disaster_here]. :)
O
On 10/17/06, Kevin Scott Sumner <[EMAIL PROTECTED]> wrote:
With just some configuration changes, the kdc authentication, token-gettingand ticket-getting all worked out of the box once-upon a time... although,we now have compiled our own version of ssh/sshd.
This seems sort of unavoidable if you wan
Andreas,
We're running RHEL 3 (various update) clients and I've got a few personal
Debian etch boxes getting PAGs and tokens on login. We also use MIT
Kerberos 5 KDCs for authentication.
A few things to look out for/check:
-- There may be a seperate PAM config file for sshd in /etc/pam.d. (Or,
Hello,
I'm trying to get sshd running in a way that
it generates tokens at login-time when
users provide their passwords.
Here are the client parameters:
Platform: i386 Fedora Core 5
Kernel: 2.6.17-1.2187_FC5smp
Client-RPMS from ATRpms:
openafs-kmdl-2.6.17-1.2187_FC5smp-1.4.1-17.
