trying to resurrect discussion about "Cannot signal a process over a channel (rfc 4254, section 6.9)"

[Iain Morgan]

On Thu, Jul 05, 2018 at 08:26:06 +0200, Thierry Parmentelat wrote:
> Hi everybody
> 
> I’d like to resurrect the discussion on a known issue with the openssh server, regarding signal delivery as described in rfc4254
> 
> This has been originally reported about ten years ago in this thread:
> https://bugzilla.mindrot.org/show_bug.cgi?id=1424
> 
> I am taking he liberty to copy a few people who contributed that thread over time
> 
> The discussion does not seem to expose the reasons that lead to the feature being held back for so long
> I do share Thomas’s feeling that separating the server and client aspects would be a good way to restart from a clean slate
> 
> This is why I would suggest to first address the server side of the matter, which turns out to be our team’s major and single concern here, like I believe all/most of the other requestors
> 

At one point, I had wondered about separating out the client and server
support as well. At first glance, that would seem to help move things
forward and would address most of the reported use cases. However, I
have some users who would need the client support as well.

I suspect that adding the server support first might be a problem for
the developers. Such a feature would need regression and unit tests, and
those would be easier to implement if the client has support for the
feature.

It would be nice to know what the precise technical issues are that have
prevented support for this from being added. From what I recall, it
seemed like the delay was largely due to details of the client
behaviour, and possibly some feature creep. 

-- 
Iain Morgan