https://bugzilla.mindrot.org/show_bug.cgi?id=3598
Damien Miller changed:
What|Removed |Added
Attachment #3711||ok?(dtuc...@dtucker.net)
Fla
https://bugzilla.mindrot.org/show_bug.cgi?id=3598
--- Comment #6 from Darren Tucker ---
(In reply to Damien Miller from comment #5)
> Other options
> include implementing LoginGraceTime in the monitor mainloop
That's non-trivial since some of the potential timeouts are prior to
the monitor mainl
https://bugzilla.mindrot.org/show_bug.cgi?id=3598
--- Comment #5 from Damien Miller ---
nerfing sigdie would mean that we lose the following log messages:
auth-pam.c: sigdie("PAM: authentication thread exited
unexpectedly");
auth-pam.c: sigdie("PAM: authentication thread
https://bugzilla.mindrot.org/show_bug.cgi?id=3598
--- Comment #4 from Darren Tucker ---
(In reply to Damien Miller from comment #3)
> IMO the problem is fundamentally that we're doing operations in a
> signal handler that are unsafe on some platforms.
That's true but I don't think it's the probl
https://bugzilla.mindrot.org/show_bug.cgi?id=3598
Damien Miller changed:
What|Removed |Added
CC||d...@mindrot.org
--- Comment #3 from Dami
https://bugzilla.mindrot.org/show_bug.cgi?id=3598
--- Comment #2 from mzhan017 ---
Darren,
Yes, you're correct.
We could be blocked in the first syslog call, even without the dead
lock.
But still could face the issue of the number of process/memory usage
kept increasing.
Is it possible to defen
https://bugzilla.mindrot.org/show_bug.cgi?id=3598
Darren Tucker changed:
What|Removed |Added
CC||dtuc...@dtucker.net
--- Comment #1 from D
https://bugzilla.mindrot.org/show_bug.cgi?id=3598
Bug ID: 3598
Summary: Dead lock of sshd and Defunct of sshd
Product: Portable OpenSSH
Version: 9.1p1
Hardware: ix86
OS: Linux
Status: NEW
Severity: normal
