Hi everyone! I know it’s been a while since I posted here but I’ve been pretty busy working at Google and what not between all of the vacations :). Anyway, I’ve had a little free time lately and I managed to put together what I think is a pretty cool site called KeeStand.
KeeStand is a cloud-based (Google AppEngine) password storage system similar to LastPass but open source and free. Here are some cool features:
- All encryption/decryption of your passwords is done locally (in JavaScript). This means that my server never sees any of your passwords!
- Authentication is provided by storing salted and repeatedly SHA-256 hashed versions of your password. Encryption is provided via the AES-256 algorithm. These functions are implemented in the Stanford JavaScript Cryto Library.
- You can import your passwords stored locally in comma-separated values form into KeeStand.
- You can export your passwords stored in KeeStand to comma-separated values form, readable in Excel or Google Docs.
- If you choose to delete your account, it is immediately and irrevocably destroyed.
- Since KeeStand is open source, you can verify that it works the way I say it does by looking at the (not too horribly organized) source code.
When you visit KeeStand for the first time, choose a username and password. If the username has already been selected, it will not let you log in. After the first log in, continue to log in using the same credentials to see your saved passwords.
My previous solution for saving passwords involved a GPG-encrypted text file that just had all the info all over the place. The problem was that every time I signed up for a new website or service I would have to:
- Decrypt the file.
- Edit the file.
- Encrypt the file.
- Copy the file all over the web/my computers to make sure it didn’t burn up in a fire.
KeeStand has reduced this to:
- Log in to KeeStand.
- Add/edit a password.
- Click the save button.
I know the interface for KeeStand is a little rudimentary right now (coming soon: groups! reordering your password list! custom fields!), but I thought some of you might want to give it a try so I’m putting it out there. Please let me know if you find problems or if there are features you would like to see!