4 ms·

Setting up regular publishing of CRLs is just part of setting up a CA. Is there some extra complexity with ssh here, or are you (rightfully) just complaining ab

• semi 2y ago
  There's extra complexity with ssh, it has its own file of revoked keys in RevokedKeys and you'll have to update that everywhere. see https://man.openbsd.org/ssh-keygen.1#KEY_REVOCATION_LISTS https://man.openbsd.org/ssh-keygen.1#KEY_REVOCATION_LISTS for more info And unlike some other sshd directives that have a 'Command' alternative to specify a command to run instead of reading a file, this one doesn't, so you can't just DIY distribution by having it curl a shared revocation list.
• janosdebugs 2y ago
  The hard part is making sure every one of your servers got the CRL update. Since last I checked OpenSSH doesn't have a mechanism to remotely check CRLs (like OCSP), nor does SSH have anything akin to OCSP stapling, it's a little bit of a footgun waiting to happen.
  • tiberious726 2y ago
    Oh wow... That's pretty nuts. I guess the reason is to make it harder for people to lock themselves out of all their servers if OSCP or whatever is being used to distribute the CRL is down.
    • janosdebugs 2y ago
      Not necessarily. There is a fork of OpenSSH that supports x509, but I remember reading somewhere that it's too complex and that's why it doesn't make it into mainline.