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
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
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
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
https://bugzilla.mindrot.org/show_bug.cgi?id=3558
Darren Tucker changed:
What|Removed |Added
Attachment #3689||ok?(d...@mindrot.org)
