Quoting Marc Lehmann ([EMAIL PROTECTED]): > Package: login > Version: 1:4.0.3-35 > Severity: normal > > > Directly after a fresh reboot eeboot, "rsh rebooted-host" results in an > immediate connection close, and the syslog on the remote host says: > > Oct 5 06:12:36 cerebro in.rlogind: Connection from [EMAIL PROTECTED] for > root > Oct 5 06:12:36 cerebro pam_rhosts_auth[452]: allowed to [EMAIL PROTECTED] > as root > Oct 5 06:12:36 cerebro login[453]: (pam_unix) session opened for user > root by root(uid=0) > > Oct 5 06:12:36 cerebro login[453]: unable to determine TTY name, got > /dev/pts/1 > Oct 5 06:12:36 cerebro in.rlogind[452]: Closing connection with [EMAIL > PROTECTED] > > "/dev/pts/1" looks like a perfectly fine tty name to me. Subsequent rsh > calls work fine. > > I think at least the error message should be clearer, right now it is > wrong, as it did correctly determine the tty name, and something else
Can you try reproducing this with login and passwd packages from sid ? Etch (testing) currently still has the old 4.0.3 version we had in sarge and the gap with 4.0.12 which is in sid is huge. It also seems that you're trying to rsh from root to root on another host. Despite being highly insecure, have you checked the contents of /etc/securetty on the target machine? I actually think that the "unable to determine TTY name" from login is maybe not *the* cause of the problem.
