This issue could have been avoided if SSH used certificates like TLS does, but SSH uses a Trust on First Use model which can lead to users blindly accepting new keys.
The solution is to deploy the private key to every front-end server and have it call out to an HSM-backed service to request new SSH host certificates signed by a private key in the HSM. Clients configured to trust the signing key will trust the certificate without manual intervention.
The main obstacle is that client tooling does not support this well, and so the most important improvement to the SSH ecosystem would be to make it easier to use certificates.
Let's keep in touch!
Stay updated with my latest posts and news. I share insights, updates, and exclusive content.
Unsubscribe anytime. By subscribing, you share your email with @faun and accept our Terms & Privacy.
Give a Pawfive to this post!
Only registered users can post comments. Please, login or signup.
Start writing about what excites you in tech — connect with developers, grow your voice, and get rewarded.
Join other developers and claim your FAUN.dev() account now!
The FAUN watches over the forest of developers. It roams between Kubernetes clusters, code caves, AI trails, and cloud canopies, gathering the signals that matter and clearing out the noise.
Developer Influence
3k
Influence
302k
Total Hits
3711
Posts
Hey, sign up or sign in to add a reaction to my post.
Join thousands of other developers, 100% free, leave anytime.
Hey there! 👋 I created FAUN.dev(), an effortless, straightforward way for busy developers to keep up with the technologies they love 🚀
Aymen @eon01
Founder of FAUN.dev()
Join thousands of developers and engineering teams who use FAUN.dev() to stay up-to-date with the technologies they love, without the overwhelm.