Re:Ask HN: How To: Store and share passwords in a company?
by insane_dreamer on Monday September 02, 2024 @12:00PM
(#41426549)
> never send credentials over plaintext, such as email or Slack
Slack works for us in a very small (<5) number of trusted long-time remote devs, but with two important conditions:
1. New/updated password(s) to be shared are in an encrypted Keypass file (encrypted with a preset and prearranged password that was only shared once offline). Recipient merges into their local keypass file.
We use many AWS services so obv all those are handled with AWS Secrets and IAM, so we only need to save the login pwd externally. And for services which support multi-user, Google, GitHub, etc., each user has their own pwd. So not many passwords need to be shared in the above manner. In daily use I keep KeyPass open and copy/paste passwords into the browser when needed -- nothing stored online.
Slack works for us in a very small (<5) number of trusted long-time remote devs, but with two important conditions:
1. New/updated password(s) to be shared are in an encrypted Keypass file (encrypted with a preset and prearranged password that was only shared once offline). Recipient merges into their local keypass file.
2. Confirm recipient is online, send, confirm receipt, delete immediately afterwords.
We use many AWS services so obv all those are handled with AWS Secrets and IAM, so we only need to save the login pwd externally. And for services which support multi-user, Google, GitHub, etc., each user has their own pwd. So not many passwords need to be shared in the above manner. In daily use I keep KeyPass open and copy/paste passwords into the browser when needed -- nothing stored online.