Skip to content

Consider modernizing guidelines/openssh.md to actually "modern" openssh #198

@thomas-nilsson-irfu

Description

@thomas-nilsson-irfu

Currently the Guidelines for OpenSSH configurations, i.e. the guidelines/openssh.md is listing settings for "Modern (OpenSSH 6.7+)". Given that OpenSSH 6.7 was released over 11 years ago (2014-10-06), it is perhaps time to do a bigger overhaul with in these guidelines and move the "OpenSSH 6.7+" section to "Intermediate" and current "Intermediate" to "Historical / Old".

I see a few reasons why there such an overhaul may be needed and really be the best solution forward:

  1. Currently "best practice" of supported Ciphers and Key exchange etc. are not mentioned at all. For instance the post quantum recommended sntrup761x25519-sha512 algorithm (supported since OpenSSH 9.0, dated 2022) nor mlkem768x25519-sha256 (OpenSSH 9.9) are mentioned at all.
  2. If anyone is following the guide today (on an actual "modern" install) it would arguably make their install less secure.
  3. Actually modern OpenSSH (10.0) will display a lot of warnings to users if not using a PQ algorithm, potentially causing a bit of confusion for less technically literate users.
  4. It's been over 11 years since 6.7 was actually to be considered "modern". In terms of IT security that is a long time...

There is currently a few issues here in Github about making small fixes here and there, such as #170, #176 and #192 just to mention a few. I would consider them more of a band-aid solution, it is time to properly fix the "Modern" configuration, and move historical recommended configurations to "Historical".

Some ref:

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions