Mailing List Archive

[Bug 396] sshd orphans processes when no pty allocated
http://bugzilla.mindrot.org/show_bug.cgi?id=396





------- Additional Comments From markus@openbsd.org 2003-06-05 00:09 -------
sending signals could be dangerous, depending on the permissions
of the sending process, e.g. a root-owned sshd sending to
a setuid process. but i'm not sure. we had similar code there before.





------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
[Bug 396] sshd orphans processes when no pty allocated [ In reply to ]
http://bugzilla.mindrot.org/show_bug.cgi?id=396





------- Additional Comments From dtucker@zip.com.au 2003-06-05 00:40 -------
Maybe I'm being thick but I don't see
how this could be dangerous (or, at
least, any more dangerous than the
SIGHUP it would get anyway if it had a
pty).



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
[Bug 396] sshd orphans processes when no pty allocated [ In reply to ]
http://bugzilla.mindrot.org/show_bug.cgi?id=396





------- Additional Comments From markus@openbsd.org 2003-06-05 00:49 -------
hm, i'm not sure, but it might behave different if it had a pty. but
perhaps i'm mixing up things.

in any case, the kill should be done from within session.c
on session cleanup, i think.



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
[Bug 396] sshd orphans processes when no pty allocated [ In reply to ]
http://bugzilla.mindrot.org/show_bug.cgi?id=396





------- Additional Comments From fdjsouthey@uwaterloo.ca 2003-06-18 07:56 -------
Just for comparision, the man page for 'rsh' states:

"Interrupt, quit and terminate signals are propagated to
the remote command;"

It seems reasonable to me for ssh to behave like rsh in this respect.



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.