Documentation and password storage for a web hosting company

Question

I am in the process of designing and building a documentation and password storage point with the following ingredients:

• Suffice from service outages
• Automatic backups
• Keeping security and simplicity in mind -- maybe integrating it with yubikey
• Remotely accessed

I have already checked the following:

• How are you documenting your work, processes and environment?

• Good internal wiki software

But none really answers to my question.

1. How are you organizing your office/services/passwords?
2. How do you access this service and what happens when this service is down ?

My idea is to build:

• 2 small local server with mediawiki or a wiki variant that supports yubikey, accessed by a stepping stone via SSH.
• Automatic sync of data between the two servers. --I guess it's possible.

I would like to hear your opinions, obstacles and bad experiences that you had/have with a similar implementation.

Thank you.

Answer 1

I use KeyPass. It's open source, runs on every platform I'd care about*, and requires no installation** and each database is one small, AES 256-bit encrypted file. License is GNU Public, so I know it's future proof. Supports certificate authentication or a master password. Lots of thought went into security.

Features a nice, folder hierarchy and you can attach documents to each entry. I'm finding I'm using this to deliver passwords/documentation to my clients when a project wraps up.

*Windows (.NET framework required), Linux/Mac mono required, but there's a port I haven't tried yet. **obviously you'll need to install mono/.NET to run it.