[6672] in Kerberos
Re: krlogin/krlogind usage of OOB data is broken
daemon@ATHENA.MIT.EDU (Barry Jaspan)
Fri Feb 16 11:15:26 1996
Date: Fri, 16 Feb 96 11:02:06 EST
From: Barry Jaspan <bjaspan@bbnplanet.com>
To: Tim Shepard <shep@ginger.lcs.mit.edu>
Cc: kerberos@MIT.EDU
In-Reply-To: [6658]
I would like to add a small comment to this thread. I'm sure that OOB
data handling with krlogin is broken. But I do not believe that is
the bug that causes ^C to kill the session.
When I investigated this bug, I found that the real problem was that
rlogind was not disassociating itself from the process group that
included login and/or the user's shell. Thus, when a user typed ^C to
rlogin, it got sent to rlogind, which wrote it to the pgrp's terminal,
which generated a SIGTERM for the process group. rlogind receieved
the signal because it was in the pgrp, so it exited.
I recall that this was only a problem with one of sh or csh, but not
both, because those two shells handle pgrps for their children
differently; but I don't remember the details.
Fixing rlogind to create a new pgrp (typically with setsid(), after
closing the pty) for the user's shell fixed the problem.
Barry
