Live data from Hacker News

Ask HN: How do you manage shared company passwords?

news.ycombinator.com

61–65 of 65 posts

Re: Ask HN: How do you manage shared company passwords?

#61

I've ran into this problem, but most of the time the passwords were shared orally A good solution would also be able to manage private SSH keys as well

For what purposes do users need to share private SSH keys? The trusted keys file can hold an arbitrary number of public keys.

Re: Ask HN: How do you manage shared company passwords?

#62
post #61

I've ran into this problem, but most of the time the passwords were shared orally A good solution would also be able to manage private SSH keys as well

For what purposes do users need to share private SSH keys? The trusted keys file can hold an arbitrary number of public keys.

Yeah, sharing is a bad example, it's more like passing keys (to be added) or passing control to another person that will log in and add new keys

Re: Ask HN: How do you manage shared company passwords?

#63

There isn't a perfect solution, but LastPass Entrprise or a similar service is probably the closest you're going to get. KeePass is great, but it's a single user solution. --Even I have to be careful about forgetting to save the database after adding a new entry at work and then going home and adding something else there. You shouldn't even be entertaining the idea of a Google Docs sheet or an Excel file in Dropbox w…

LastPass Enterprise is working well enough for our organisation. The only thing I dislike about it is that I have a personal LastPass account and can’t keep them both logged in at the same time through the browser plugin.

Of course, today a colleague pointed out that from within your enterprise account you can ‘link your personal account’ from the let sidebar. That was my last gripe really (apart from the front-end code needing an overhaul).

Re: Ask HN: How do you manage shared company passwords?

#65
post #18

We use plain GPG-encrypted files stored in our version control system (git/svn). The files get encrypted with all the public keys of the users who have access to these files, and can be decrypted with their private keys then. Not perfect, but works.

We do this too. The trick is making sure everyone keeps everyone else's public keys up to date and signed in their clients, because if you edit the file and re-encrypt it for everyone else to read, it's easy to overlook that GPG ignored one of the recipients due to you not having their key signed, etc.

None of us are fluent enough in GPG practices to do this stuff off the top of our heads, though, so our management of these files involves a lot of rote "here's how to re-encrypt the file" or "here's how to import the new guy's key" instructions. It's pretty clunky.

Post reply on HN