I've written my second(!) go project, an ssh certificate authority for 
forwarded ssh connections.

https://github.com/rorycl/sshagentca

The idea for the project came from Peter Moody's posting about uber's pam 
module for ssh forwarded agents with certificates:
https://medium.com/uber-security-privacy/introducing-the-uber-ssh-certificate-authority-4f840839c5cc
The facebook post about using certificate principals for zones is also 
interesting:
https://engineering.fb.com/security/scalable-and-secure-access-with-ssh/

It's a small project, but can make a big difference to ssh-related 
workflows, providing time-scoped, user-specific ssh certificates.

I'd be grateful for some ideas on how to improve the code. I'm specifically 
interested in how one might go about auditing the project from a security 
standpoint.

Rory

-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/golang-nuts/e5ce0979-3bd3-4b60-a6a1-94c25e625fc6%40googlegroups.com.

Reply via email to