How do you manage your server access details?

PremiumN

You cant trust it anywhere these days..so i refuse to put it anywhere online or on my pc

mickeyr

I just use SSH keys myself, but lastpass is a great service for securely storing credentials.

cassa

SSH keys on my 2 redundant home servers, protected with a password in my head

Gien

Using keepass' synced in dropbox with keyfilein another well known storage provider ex ovh hubic and a long passwordd

I use it to store my browsers logins too.. and it has an option to add files' so ssh keys are in the db.

Backs are stored pgp'd and added to treucrypt volume for safety

jar

My new response when asked how I store my passwords is "wouldn't you like to know." At this point I've managed to make myself a target for a few skids, and I've weaved such a stupidly complicated web around my access data, and that's really what you have to do now days. You can't be too careful, and you should use 2 factor authentication everywhere you can. No matter what, you always have a single point of failure. It's inevitable. Lock down that point of failure so hard it makes the NSA say "wtf man."

defiant

I use lastpass which is pretty awesome if you ask me. Also you could use a text doc in your Google drive just in case.

hostnoob

@ironhide said:
Don't login with your user/password in your server. Rather use ssh keys. Generate a ssh public/private key in your home maching (if not already created) and copy the public key in your server's ~/.ssh/authorized_keys file. For extra security you can use passphrase

You can then disable password based login in your server.

And then you can login anytime without being asked for user/password.

and if you're not at home or your HDD fails?

cnbeining

Chrome+Google Drive。。。

Everyone should disable password with SSH. Don't make those hacker's life too easy...

deptadapt

For most web sites I let Firefox remember the password and use a master password. The Firefox master password is kept in a keepassx database, along with all my other passwords.

For the past year I've been using Ansible as a software configuration management tool for my VPSs. I've been developing playbooks for every service that I deploy. For my playbooks I've been using the password lookup plugin for passwords used on servers, stuff like database credentials and Tripwire passphrases etc.

Basically when I execute the playbook it checks a specific path for a text file containing the password, and if it doesn't exist (deploying service for first time for example) then a random password is generated and stored in that file for next time. These password files get stored in a "passwords" directory with subdirectories organized by FQDN, all safely stored on multiple encrypted external drives that are only mounted for production deployments.

Usually I don't rely on the password lookup plugin to generate a password, for production deployments I generate and store them in a separate keepassx database before putting them in the passwords directory as text files.

I also disable SSH password authentication on everything

TarZZ92

Roboform + Excell

tommy

TarZZ92 said: Excell

Oh my

linuxthefish

Write the key down on pen and paper.