5 ms·
That's just not how it works, and it never has. One of the main purposes of the .d files is to avoid modifying the distro's sshd_config file, so you don't have
by HumanOstrich 2y ago
That's just not how it works, and it never has. One of the main purposes of the .d files is to avoid modifying the distro's sshd_config file, so you don't have to resolve conflicts during an OS upgrade. Commenting your overrides in the sshd_config? That's backwards.
Downstream distros sometimes want to override the default settings. That's what .d is for. It doesn't violate the dogma "principle of least surprise", especially if you run `man sshd_config` and learn the first thing about sshd's config files.
- Brian_K_White 2y ago[flagged]
- HumanOstrich 2y agoChild? Do you condescend based on principle or dogma? ¯\_(ツ)_/¯
- Brian_K_White 2y ago[flagged]
- HumanOstrich 2y agoThere isn't a comment specifically saying that including more config files can override values, so I'll give you that. However, it does have comments explaining exactly how to override default values. It looks like what the OP of this thread is attempting should work unless they messed up something else. I'm looking at a couple sshd_config files on my servers, and the Include directive for the overrides is the first non-comment line in the file. Having that Include be first means that changing any settings in the sshd_config file will override anything set by sshd_config.d/* files. What in the heck are these people doing to break their config? There really is no legitimate issue here.