If you’re not using SSH certificates you’re doing SSH wrong
Interesting reading, but it kind of glosses over the important problems for me. For example:<p>Do all OS distributions have new enough openssh, is it ever built with missing support by default?<p>what extensions are necessary in the certs to be trusted for ssh
or the CA cert (is your average test CA cert going to be valid for ssh without tweaking)?<p>Do any (or all?) cloud server products regularly accept cert based configuration just as they accept public key lists?<p>How will this interact with other features like using a pkcs mechanism for a token key?<p>If revoking does work, that means the system will deny cert based auth when it has internet connectivity problems? If it wont isnt building more general pools of certs more dangerous than restricting systems to specific lists of public keys?<p>Also questions like what does an eaves dropper see in the clear and how does it differ from what they see with raw public key?<p>(I find it insane that ssh ultimately ends up with a weaker trust model than a pretty average website in a typical install due to less certainty and clarity about what a normal certificate based configuration should look like.)