Dear Nicolas, >> But mainly, "exec login" cannot possibly work in a PAM environment, but >> will fail/die and "lose" the user session; users should not be tricked >> into doing that. Presumably the user logged in with login (e.g. telnet, >> may not apply for ssh or xterm); then login done a fork before running >> the shell; any utmp entry refers to the PID of the parent login. > > I don't get your point. > At least when login was setuid on debian, "exec login" used to work on PAM > environments.
Please do the simple test (which "works" regardless whether login is setuid or not): any...@anywhere:~$ /usr/bin/telnet bari Trying 129.78.69.145... Connected to bari.maths.usyd.edu.au. Escape character is '^]'. Debian GNU/Linux 4.0 bari.maths.usyd.edu.au login: psz Password: ... p...@bari:~$ /bin/login No utmp entry. You must exec "login" from the lowest level "sh" p...@bari:~$ exec /bin/login No utmp entry. You must exec "login" from the lowest level "sh" Connection closed by foreign host. any...@anywhere:~$ Surely your memory of "used to work" is wrong? Cheers, Paul Paul Szabo p...@maths.usyd.edu.au http://www.maths.usyd.edu.au/u/psz/ School of Mathematics and Statistics University of Sydney Australia -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
