I dislike how this leaks metadata by storing the site names in plaintext. I’d care more about people finding out I had a Neopets account than I would about the password to that (entirely hypothetical) account.
Also, is it possible to store a username for a site as well as a password? It doesn’t look like it from the examples. Sometimes remembering what username you used for a site is harder than the password.
[Comment removed by author]
A coworker who used crypt used a wrapper that passed everything through Crypt::Scrypt. Worked really well.
Also, is it possible to store a username for a site as well as a password? It doesn’t look like it from the examples.
Yes, you can store a username or any arbitrary data. See the section titled Usernames, Passwords, PINs, Websites, Metadata, et cetera.
See the section titled Usernames
Oh, duh. I searched the man page for “username” but not the website.
You can name the files whatever you like. You could create an encrypted file that was a map of random filenames to the account name if wanted. I’ve thought about creating a patch that would do that storing and lookup for you.
I’m not associated with pass, but I think that would be a much-welcomed optional feature, should you find the time to implement it.
You can store any data you want. However I do agree I don’t like storing the site names in plaintext, but in general I find pass a really handy tool. I have just migrated from keepassx2 to pass.
Saw it on Reddit and found this post while trying to submit it to Lobsters. Is the language still actively developed? The post is from March of this year.
It appears to be active. See: https://github.com/Whiley