This sounds like Smallstep to me.
Show HN: I built a simple, open-source tool to manage servers and SSH keys
21–30 of 97 posts
Re: Show HN: I built a simple, open-source tool to manage servers and SSH keys
#22I feel like some of these things are solved problems. We store our SSH authorized keys in LDAP, cache it with NSLCD. Backup keys are pushed during setup, rotated regularly. Everything audited through separate systems.
Re: Show HN: I built a simple, open-source tool to manage servers and SSH keys
#23Earlier quoted context omitted.
If you're managing a ton of servers manually, this makes a lot of sense.
If you’re managing a ton of servers you are already using ansible or packer or salt or something.
You’d be surprised… a lot of especially legacy setups are very duct-taped together. Heck recently as last year I needed a three machine cluster and just did it manually instead of ansible.
I could definitely see the use of a tool like this if it was fleshed out a bit more.
Re: Show HN: I built a simple, open-source tool to manage servers and SSH keys
#24That's a sensitive area for someone unknown to be touching.
You have no information about who you are or what you've done and you expect me to trust you with ssh keys and remotes?
The go.sum is concerning as well because now I need to trust all of those.
Re: Show HN: I built a simple, open-source tool to manage servers and SSH keys
#25What's the point of having different ssh key per server?
You are .pub is meant to be shared; even publicly. It's fine to have one ssh key for everything. It's also hard to think about a scenario where one ssh key in your machine is compromised, but not the others.
Re: Show HN: I built a simple, open-source tool to manage servers and SSH keys
#26What's the point of having different ssh key per server? You are .pub is meant to be shared; even publicly. It's fine to have one ssh key for everything. It's also hard to think about a scenario where one ssh key in your machine is compromised, but not the others.
> What's the point of having different ssh key per server?
Identity protection perhaps. A public key could reveal that the same person is accesing two or more servers. Different keys per server hide that information.
Re: Show HN: I built a simple, open-source tool to manage servers and SSH keys
#27What's the point of having different ssh key per server? You are .pub is meant to be shared; even publicly. It's fine to have one ssh key for everything. It's also hard to think about a scenario where one ssh key in your machine is compromised, but not the others.
Reads like some misguided attempt at improving security.
Maybe OP also moves private keys around and doesn't know private key ideally should never leave single machine and if you setup new laptop to connect to your servers one should generate new private key and upload new pub key and for backup ideally one should have spare laptop already set with keys.
Re: Show HN: I built a simple, open-source tool to manage servers and SSH keys
#28r/DIWhy material.
Re: Show HN: I built a simple, open-source tool to manage servers and SSH keys
#29Earlier quoted context omitted.
Thanks! - No need to remember server IPs - Viking gives you an overview with simple machine ls and key ls commands - A more modern and intuitive API - Works consistently across all platforms - Close to the Docker API Sure, it’s only the first release. It may not seem like much now, but with feedback, the project will move closer to the goal.
Essentially you wrap via CLI what you can code in ~/.ssh/config, I'm not so sure how this could be comfy.
Right, I don't see the point of this at all. If anything it seems like more of a pain in the ass than just using ssh directly.
Re: Show HN: I built a simple, open-source tool to manage servers and SSH keys
#30Earlier quoted context omitted.
> It links up addresses to host names so that you don’t have to remember ip addresses of servers. Um.
Just imagine that DNS doesn't exist. Or hosts files. Or `~/.ssh/config`...
Well I can imagine working in a cheapo shop where you cannot have public technical domain or setting up DNS is "too much to spend on".
But hostfile well if you have to share it with 2-3 other people might be a hassle?