On Thu, Apr 20, 2017 at 11:00 AM, Scott Neugroschl <scott_n@xxxxxxxxx> wrote: > > On Wed, Apr 19, 2017 at 1:02 PM, navern <livingdeadzerg@xxxxxxxxx> wrote: > >> Is there any available tool with this for pre-evaluating the resulting sshd_config for fatal errors? I'm not demanding: I'm thinking "that could be really, really useful". > > What's wrong with "sshd -t"? Good reminder, thank you. I'm still slightly concerned about deploying a new, broken configuration and being unable to get in to fix it. You'd have to *stage* the deployment, first into a test environment against which you can run "sshd -t", and then deploy them robustly and without dangling bits to be sure that the test environment correlated well to the production enviornment. But that's for fascist control in environments where you can't get hands and eyes at the keyboard on the local system, and especially if you're getting complex with your "include" files. _______________________________________________ openssh-unix-dev mailing list openssh-unix-dev@xxxxxxxxxxx https://lists.mindrot.org/mailman/listinfo/openssh-unix-dev
