4 ms·
I was saddened to read the release notes that state: "OpenSSH is a 100% complete SSH protocol 2.0 implementation..." This bug[0] calling out the fact that Ope
by spudlyo 10y ago
I was saddened to read the release notes that state:
"OpenSSH is a 100% complete SSH protocol 2.0 implementation..."
This bug[0] calling out the fact that OpenSSH doesn't implement section 6.9 of RFC 4254 (which allows you to send signals to remote processes) has been open since 2008, complete with community submitted patches that implement that part of the protocol.
My recent pet Golang project[1] is a parallel remote command executor that uses OpenSSH, and I would really love the ability to better manage remote processes I execute via SSH.
[0]: https://bugzilla.mindrot.org/show_bug.cgi?id=1424 https://bugzilla.mindrot.org/show_bug.cgi?id=1424
[1]: https://github.com/spudlyo/metassh https://github.com/spudlyo/metassh
- drvdevd 10y agoI mostly jumped to the bottom of the bug discussion thread there, but there doesn't seem to be much opposition to adding this, just comments deferring this to other releases. Are they just requesting that patch submitters do some extra work to get it in there?
- spudlyo 10y agoI think they've been wanting to get this patch into OpenSSH for years, but for whatever reasons it just never happened. I assumed it was a community patch, but it was actually written by Darren Tucker, who is an OpenSSH dev. There was some conversation about if it was appropriate to pass on certain signals, but that's about it. After Darren cleaned up some client UI issues that bugged him, he even suggested that we might see the patch in 5.4.