Today I explored ssh-audit, a tool designed to audit SSH configurations. Although it’s an excellent tool, I found the hardening guides somewhat lacking. Hence, I decided to write a detailed walkthrough, ensuring the ssh/sshd configurations are easily readable.
  • RegalPotoo@lemmy.worldEnglish
    9·
    1 year ago

    Cool,.but from the post it seems like all it does is:

    • Recommend disabling old algorithms, which you would have already done if you followed a modern hardening guide like https://infosec.mozilla.org/guidelines/openssh
    • Detect if you are running a known-vulnerable version of OpenSSH, which wouldn’t be an issue if you keep good patch hygiene and install your SSH server through you operating systems’ package manager

    So what’s the point? Who is this for?

    • jwhardcastle@dmv.socialEnglish
      15·
      1 year ago

      Scripting, to confirm that a large fleet of boxes are all running according to your policy. Verification that the config you want is actually the config you have.