This is also true @jlehtone , but most people know about the configurations listed directly and explicitly in the /etc/ssh/sshd_config file and when the ssh packages are updated it doesn’t matter which file has your updates there will be an rpmsave file created. As such, you will realize the package was updated and you may need to copy back your configurations (most of the time not); so leaving your custom changes in a file that is regularly checked makes it easier for troubleshooting than putting the custom changes into a file that is rarely reviewed if at all.
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| Having issues with security hardening | 6 | 2309 | November 1, 2023 | |
| Hmac-md5-96 bit need to be disable | 3 | 2898 | February 9, 2024 | |
| STIG- Configure SSH Client to Use FIPS 140-2 Validated Ciphers: openssh.config | 4 | 1334 | March 14, 2024 | |
| Bug in crypto-policies re ssh key exchange algorithms: should I report upstream? | 1 | 1263 | January 6, 2023 | |
| Custom crypto backend file for second sshd process | 1 | 637 | August 19, 2024 |