[Bug 1424] Cannot signal a process over a channel (rfc 4254, section 6.9)

bugzilla-daemon at bugzilla.mindrot.org bugzilla-daemon at bugzilla.mindrot.org
Sun Jan 20 09:50:36 EST 2008


https://bugzilla.mindrot.org/show_bug.cgi?id=1424


Darren Tucker <dtucker at zip.com.au> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |dtucker at zip.com.au




--- Comment #6 from Darren Tucker <dtucker at zip.com.au>  2008-01-20 09:50:33 ---
(In reply to comment #5)
> I don't think it makes sense to automatically pass some of these from
> the client to the server. E.g. SIGSEGV, SIGFPE, SIGILL, SIGBUS,
> SIGPIPE, SIGALRM and SIGABRT should be considered "internal" and never
> passed (or acted upon by the server).

The list of signals is specified in the RFC, but while we can generate
(and process) all of these, only the ones for which the client has a
signal handler will be automatically passed on.

I'm not entirely happy with the client interface, but it worked for
testing.  (Should also interop test with at least one other
implementation, I think PuTTY has it these days.)

-- 
Configure bugmail: https://bugzilla.mindrot.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
You are watching someone on the CC list of the bug.


More information about the openssh-bugs mailing list