3 ms·
I'm not sure is this really is much of an improvement. SSH keys (as opposed to ssh certs) have lots of trust issues, the main one being no way to properly revok
by e12e 12y ago
I'm not sure is this really is much of an improvement. SSH keys (as opposed to ssh certs) have lots of trust issues, the main one being no way to properly revoke a key, or for a key to expire.
I'm not sure adding this to the ssh server is better than just telling people to use DNS RR-records (or use ssh certs, which narrows the problem to one of distributing the ssh CA cert).
http://www.openssh.com/txt/rfc4255.txt http://www.openssh.com/txt/rfc4255.txt
http://www.iana.org/assignments/dns-sshfp-rr-parameters/dns-sshfp-rr-parameters.xhtml http://www.iana.org/assignments/dns-sshfp-rr-parameters/dns-...
I've yet to get around to managing my ssh keys via "ssh ca/ssh certs" (certs are relatively new -- at least when still running some Debian Old-stable LTS boxes...). Looks like this might help:
https://github.com/cloudtools/ssh-ca https://github.com/cloudtools/ssh-ca
As far as I can tell, there is no support to store SSH (CA) Certs in DNS -- which is a shame. Would've made sense to just have a SRV-record for the (sub)domain?