> What are best practices to manage private and public keys as well as all these usernames/password for the web ui's? Use a password database to store credenti

> What are best practices to manage private and public keys as well as all these usernames/password for the web ui's? Use a password database to store credentials for username + password. For 2FA, ideally some U2F device like a Yubikey, I think. Keys shouldn't be stored in a DB. The public half of a key is fine to share around. The private half should never be copied anywhere. The SSH key should have a password, though; that password should be in your password database, too. > How many SSH keys BitBucket (and I'd guess GitHub) don't support using the same SSH key for multiple users. (IIUC, the key is used to determine which user is accessing the repo). So you'll need at least one per user. >> I need to access these repos from about 30 different git client machines. Weird. Why? In what way? For deploying code to these machines, or as 30 different workstations?