Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Good evening,

I'm thinking about implementing some way to manage passwords for our Linux/Windows servers based solely on security concerns and an ever growing number of servers.

How do you do it? How would you do it if you had the opportunity? What I have in mind is perhaps a key server with groups and dual authentication, or perhaps a key-ring of sorts?

share|improve this question
Active Directory. – jscott Feb 10 '12 at 13:46
Active Directory is in use for office clients and such, but for multiple offshore servers, we need something else. – Lars Feb 10 '12 at 13:54
RODCs, LDAP, there's a lot more to AD than "office clients". – jscott Feb 10 '12 at 13:58
Worth taking an extra look then, thanks. – Lars Feb 10 '12 at 13:59
You are asking how to manage authentication of user accounts rather than managing a list of passwords right? – dunxd Feb 10 '12 at 14:09
up vote 0 down vote accepted

Alternatively I would look at something like keepass or passwordsafe, which a secure password manager. It's easy to use and can be quite helpful when needing to keep track of a series of different applications, servers, websites and etc..


Password safe

share|improve this answer
Thank you, thank you. – Lars Feb 13 '12 at 7:28
@Lars no problem, I use keepass for work. – onxx Feb 13 '12 at 15:24

Do you mean like active directory ? Currently that's how we do it, winbind + active directory. Given the choice (here) i'd use pam_ldap+active directory, and in a pure *nix setup i'd use openldap, maybe with kerberos if needed.

edit: oh and on a small network (like at home) puppet is usually pretty good, or maybe nis.

share|improve this answer
As I told jscott, these are servers offshore, and I'd like to use something more safe then just one single user and pass basically. – Lars Feb 10 '12 at 13:55
I'm with Sirex, AD is the way to go. You can throw AD on any little server, set up zones within domains and/or multiple domains within a forest, you can control which parts of the LDAP DB are synced where, there is a stripped-down limited-data version specifically for remote sites that are vulnerable and thus need a minimum surface of exposure, and it already works with every windows box, ever. Don't reinvent a weak, vulnerable, wobbly wheel when 20 years of MIT and Microsoft engineering is at your fingertips. – Mark Feb 10 '12 at 14:01
It's hard to tell without knowing your environment, but our offshore offices (and hence servers) have a domain controller for each group, typically 1 failover pair per country. Depends on your setup though, and what the servers "do". It depends largely on how many users and servers your talking about, how spread out they are (logically) and what your budget on money and time is. – Sirex Feb 10 '12 at 14:02
Thanks to both of you, I will make sure to dig down in to Active Directory properly before trying out different solutions. – Lars Feb 10 '12 at 14:27

You should still use something like Active Directory and set up a VPN between all offshore sites and your main office. The VPN will keep the traffic secure, while still allowing centralized management of credentials.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.