Whether you just need to feel in power or you actually use shells for day-to-day tasks, the Secure Shell [SSH] is probably the most important administrative access tool to your servers. It's also one of the least secured mission-critical services on most UNIX servers. Why? Because for some reason people are still using mere passwords to protect their root accounts. That's not quite as bad as using telnet, but not by too much. You might as well be using plain FTP to transfer data to your server... oh, wait, that's another article.
Using passwords for your remote servers exposes you to a whole class of unnecessary security risks, which are easily avoided by either switching to SSH identities or SSH certificates. This article will cover both, since they're conceptually very similar. We'll be working very closely with OpenSSH's configuration files, hopefully explaining some of the more intimidating options you might encounter.
more here...........https://ef.gy/hardening-ssh
Using passwords for your remote servers exposes you to a whole class of unnecessary security risks, which are easily avoided by either switching to SSH identities or SSH certificates. This article will cover both, since they're conceptually very similar. We'll be working very closely with OpenSSH's configuration files, hopefully explaining some of the more intimidating options you might encounter.
more here...........https://ef.gy/hardening-ssh