Displaying 5 results from an estimated 5 matches for "cerfon".
2023 Jan 11
2
per-connection sshd doesn't always pass on SIGQUIT
On Thu, 29 Dec 2022, Philippe Cerfon wrote:
> Hey.
>
> On Thu, Dec 29, 2022 at 1:28 AM Damien Miller <djm at mindrot.org> wrote:
> > It's because the monitor process doesn't explicitly handle SIGQUIT.
>
> Are you going to merge the patch of yours?
Does it solve your problem?
-d
2014 Nov 23
2
can compression be safely used with SSH?
On Sat, 22 Nov 2014, Philippe Cerfon wrote:
> Hello.
>
> >Even if delayed compression is only activated after authentication,
> >the the fact that delayed compression will be used has already been
> >negotiated before authentication and can't be changed retroactively.
>
> Couldn't the server si...
2022 Dec 27
2
per-connection sshd doesn't always pass on SIGQUIT
Hey.
I've noticed the following behavior and wondered whether it's possibly
a bug or why it behaves like this:
When having a SSH connection, than it seems there may be two sshd
processes for that, one running as root the other as the user. As far
as I know this is because of privilege separation, like e.g.:
??sshd(2931)???sshd(10174)???bash(10180)
?
2022 Dec 29
1
per-connection sshd doesn't always pass on SIGQUIT
Hey.
On Thu, Dec 29, 2022 at 1:28 AM Damien Miller <djm at mindrot.org> wrote:
> It's because the monitor process doesn't explicitly handle SIGQUIT.
Are you going to merge the patch of yours?
Best wishes,
Philippe.
2014 Nov 18
5
can compression be safely used with SSH?
Hello.
At work we collect logs (via ssh) from all kinds of hosts on one
central node which has no connection to the internet and is tried to
kept secure.
The idea is, as you can imagine, that in case of a compromise we'd
have at least all the logs up to the break without any forgeries.
The logging is done continuously and compression is used.
Now the following is not really that much