https://bugzilla.mindrot.org/show_bug.cgi?id=3558
--- Comment #12 from Darren Tucker ---
(In reply to Damien Miller from comment #11)
> Maybe we could provide a "visudo" like tool to wrap config editing
> in sshd -T?
I like that even less than leaving it as is.
--
You are receiving this mail b
https://bugzilla.mindrot.org/show_bug.cgi?id=3558
--- Comment #11 from Damien Miller ---
Sure, but the current behaviour has the benefit of being obvious and we
do provide hooks to verify the config before reloading.
Maybe we could provide a "visudo" like tool to wrap config editing in
sshd -T?
https://bugzilla.mindrot.org/show_bug.cgi?id=3558
--- Comment #10 from Darren Tucker ---
The message doesn't go to the user sending the SIGHUP now (unless
you're arguing "when it stops working they'll eventually get the
message").
--
You are receiving this mail because:
You are watching the ass
https://bugzilla.mindrot.org/show_bug.cgi?id=3558
--- Comment #9 from Damien Miller ---
I don't like this because the message doesn't (can't) go to the user
sending the SIGHUP, only the system log. So if the intended config
change was really important (e.g. one with security consequences) but
con
https://bugzilla.mindrot.org/show_bug.cgi?id=3558
Darren Tucker changed:
What|Removed |Added
Attachment #3689||ok?(d...@mindrot.org)
Flags|
https://bugzilla.mindrot.org/show_bug.cgi?id=3558
Jim Knoble changed:
What|Removed |Added
CC||jmkno...@pobox.com
--- Comment #7 from Jim K
https://bugzilla.mindrot.org/show_bug.cgi?id=3558
Damien Miller changed:
What|Removed |Added
CC||d...@mindrot.org
--- Comment #6 from Dami
https://bugzilla.mindrot.org/show_bug.cgi?id=3558
--- Comment #5 from Darren Tucker ---
Left to its own devices, sshd will leave existing connections up when
sshd is restarted, including in the case where the restart fails. If
your active connection was terminated on a failed restart that's
prob
https://bugzilla.mindrot.org/show_bug.cgi?id=3558
--- Comment #4 from Ulrich Windl ---
May the issue is a systemd one: From the past I know you can restart
sshd without loosing your connection. Maybe (I didn't verify) systemd
kills all sshd processes if the main process died.
If so, the solution
https://bugzilla.mindrot.org/show_bug.cgi?id=3558
--- Comment #3 from Darren Tucker ---
The config is either valid or isn't. Even if we did make it accept
increasingly vague directives there will still be invalid configs.
Many SysV-style init scripts checked the config before committing to a
re
https://bugzilla.mindrot.org/show_bug.cgi?id=3558
Dmitry Belyavskiy changed:
What|Removed |Added
CC||dbely...@redhat.com
--- Comment #2 fr
https://bugzilla.mindrot.org/show_bug.cgi?id=3558
Darren Tucker changed:
What|Removed |Added
CC||dtuc...@dtucker.net
--- Comment #1 from D
12 matches
Mail list logo
