Earlier quoted context omitted.
Sarcastic remarks like "if [mostly good things] aren't principles for your security practice" an strawman arguments seem a bit provocative for this type of debate.
There was absolutely nothing sarcastic about that remark. I wouldn't snark at 'jerf. Most security practices don't have those principles for SSH. Thanks for calling it out though; if you read it that way, they might have too, which would be a little mortifying.
Poll HN: Do you use SSH certificates (not mere public-key authentication)?
151–156 of 156 posts
Re: Poll HN: Do you use SSH certificates (not mere public-key authentication)?
#152Earlier quoted context omitted.
Yes. Hesiod is safer than DNS TXT once secured by DNSSEC, because I envision mass blocking of DNS TXT in the near future.
Good luck with that. DNS TXT records are used for a lot of infrastructure right now, from DMARC/SPF/DKIM to DNS-01 validation through LetsEncrypt afaik.
Re: Poll HN: Do you use SSH certificates (not mere public-key authentication)?
#153Earlier quoted context omitted.
> How is this more secure than simply creating new certificates and replacing the old ones is the authorized_keys files? It’s more convenient for me than updating authorized_keys. When I build a new machine, for example, I first generate a new SSH keypair on the machine. Then I copy the server and user public keys to the CA. Once I drop them in the right folder, certificates get generated automatically and served ove…
How do you implement emergency certificate revocation?
I have no mechanism at the moment for revoking host keys, which is a harder problem to solve as it would involve updating a number of laptops, phones, etc. that may not be powered on at a given time, but that’s less of a problem since if I knew a host key had been compromised I wouldn’t be logging into it anyway.
Re: Poll HN: Do you use SSH certificates (not mere public-key authentication)?
#154Re: Poll HN: Do you use SSH certificates (not mere public-key authentication)?
#155Earlier quoted context omitted.
You could simply choose a short TTL, or your tool could check for e.g. "some-name._sshkeys.whatever.tld" as well as "_revoked.some-name._sshkeys.whatever.tld" to handle revocation instantly
You could also just stick it behind a https GET and probably skip a bunch of bother.
In that case, use the SSL certs directly. You'd have add support OpenSSH of course, or just convert the certificates to SSH format, but it would be architecturally much simpler.
As to the original question here, the benefit compared to other PKI alternatives (including the SSH PKI in the original question) is that revocation is much easier.
Re: Poll HN: Do you use SSH certificates (not mere public-key authentication)?
#156Earlier quoted context omitted.
How do you implement emergency certificate revocation?
I have another Raspberry Pi sitting next to my desk, with a keyboard and a tiny screen, dedicated to systems administration. My user on this machine has an SSH key that on every machine logs into an account with sudo access. To revoke a user key, I run a script from this machine that logs into each host and updates sshd’s RevokedKeys. I have no mechanism at the moment for revoking host keys, which is a harder problem…
Now you have two critical systems to protect instead of one: the Raspberry Pi and the CA.