Displaying 3 results from an estimated 3 matches for "bleyfuesz".
2018 Aug 01
2
trying to resurrect discussion about "Cannot signal a process over a channel (rfc 4254, section 6.9)"
FWIW, now that privsep is mandatory I have no objection to including
signal support in sshd.
On Wed, 25 Jul 2018, Yonathan Bleyfuesz wrote:
> Hi all,
>
> I would like to propose some ideas to revivify this subject.
>
> -First, we could add support on the client to send signal thanks to the escape characters.
> (code : https://github.com/JawaGL/openssh-portable/commit/5bc9e6bc959b1b0f89d7ca7b4b04d7c37079fef0...
2018 Jul 13
2
trying to resurrect discussion about "Cannot signal a process over a channel (rfc 4254, section 6.9)"
...cerning the environment that should be use for the test suite ?
Also in the RFC it is said :?Some systems may not implement signals, in which case they SHOULD ignore this message? . So I think the proposed patch should have some kind of whitelisting.
Thanks in advance for the answers,
Yonathan Bleyfuesz
> On 6 Jul 2018, at 00:19, Iain Morgan <imorgan at nas.nasa.gov> wrote:
>
> On Thu, Jul 05, 2018 at 23:42:55 +0200, Thierry Parmentelat wrote:
>>
>>> At one point, I had wondered about separating out the client and server
>>> support as well. At first glan...
2018 Jul 05
3
trying to resurrect discussion about "Cannot signal a process over a channel (rfc 4254, section 6.9)"
> 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