Answer the question
In order to leave comments, you need to log in
How do you store passwords from servers?
Greetings!
At the moment, I have about 15 servers under control (most of them are virtual machines) and their number is constantly increasing. I try to make different passwords for root and key services (like mysql) for each of them. In total, it turns out 5-6 passwords per server. I log in with a key.
I store the password database in 1password, which suits me perfectly, but I suggest that it can be done better and more conveniently.
How and where do you store passwords from servers? How do companies like Yandex do it? Surely there is some universal solution.
Thanks in advance for your reply.
Answer the question
In order to leave comments, you need to log in
There are about 50 servers, everything is in my head. You just need to make convenient associations. When changed, the associations must be preserved.
Well, of course, who cares. Some and from 2-3 cannot keep in a head.
I have developed a simple associative algorithm for generating a password, the basis for which is the peculiarity of the server (for example, its functionality or its tree), if there are several identical servers, I number them (earlier with numbers, now with letters - passwords are longer). For example (for several sites on the same host):
host & site - it’s impossible not to remember - then a simple and the same way in all cases of rearranging letters (and adding numbers and punctuation marks) gives absolutely unreadable passwords. For example, domain&site in the most primitive version is converted to niamod&etis. Further - fantasy will tell you, there are no limits. At one time, I password-protected daily backups, adding a date to the password.
I have been operating this system for twenty years already, there were punctures (how could it be without them), but by sorting through the possible options, I quickly managed to find the required one.
I keep important servers in my head.
I write down not very important ones in large letters on a piece of paper and stick it to the monitor.
I have an entrance everywhere by keys, the key is password protected. Passwords from working services are random, I store them in a Vim-encrypted file, before that I tried to use OpenSSL for AES encryption, I realized that it was not convenient, because integration with vim is not set up everywhere (config is too lazy to edit everywhere ;-)), which greatly complicates life (and it’s hard to remember the command :-D - openssl enc -a / -d -aes-256-cbc). Yes, old versions of Vim only support zip encryption, which breaks quite quickly, but since 7.3 blowfish is used, so everything is fine.
ssh by keys, or the system itself remembers (Ubuntu), admin and phpmyadmin remembers the browser.
The user's home directory on the work machine is encrypted.
Something rare in browser notes (Opera), syncs with browser on tablet and phone. On a tablet, the home folder is also encrypted (Windows 8).
Passwords of 20/30 characters are absolutely random, with symbols as expected, they are not memorizable, brute-force cracking too.
Most admins don't store ssh passwords. They turn off the login with the root password, and they themselves go by the keys.
Used to use keepass, moved from it to 1password.
Plus a question about serious organizations like Yandex, I wonder how it is. Heard that there is LastPass Enterprise. Does anyone use it?
Random passwords (including different cases from the characters a-zA-Z0-9) are great to remember if you enter them for at least a month.
I myself use random passwords that I have not written down anywhere for 10-11 years. The problem with updating such random passwords is solved by adding 5-6 random characters to the beginning / end. Or parts of other random passwords from the head.
I don’t use third-party software and resources, because I simply don’t trust their authors.
I don't use keys.
I don’t understand why people downvote people who answered that they keep the same in their heads?
Imagine the situation:
you have access to the terminal through which you can physically disconnect (how to send init 0 and no one will wake you up :) ), you will periodically check the status of this terminal, like your life, health, immunity, etc.
Where do you "write down" the password from him? The value of the resource is such that an attacker can get rid of you once and for all.
*my longest random in the head is 29 characters, the shortest "stub" is 5 characters.
I make key files, disable the password requirement. I make backups :)
Passwords for all MySQL are stored in KeepAss.
try lastpass, autocomplete for browsers is convenient + for mobile platforms
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question