Live data from Hacker News

Pass: The standard Unix password manager

passwordstore.org

91–100 of 213 posts

Re: Pass: The standard Unix password manager

#91

Pass user for many years, always loved it. There are a number of ways to integrate it into rofi too, so with the press of a few keys I can navigate to any site and login instantly. To squash a few concerns: - Leaking data - If someone types "pass" in your terminal it will show a list of sites that you've stored. I don't find this any less obvious than if someone had LastPass installed on their machine. - Trusting dif…

What people mean by leaking metadata is if you sync over git or dropbox you also leak the metadata to them. Whereas with 1password or something like it the sync server only sees an opaque blob.

Re: Pass: The standard Unix password manager

#93
post #15

Earlier quoted context omitted.

compared to other password managers which is just an encrypted database. pass uses normal folders to store your website/username information so in that way it is less protected.

Something to consider, sure. But the exposure is to anyone with access to your encrypted pass data. Which in the normal use case is going to be anyone with access to your user account, which means they could likely already see your shell and browser history.

Not if you want to access it on multiple devices, in which case the built-in solution is to use git. In that case your git server sees all the metadata.

Re: Pass: The standard Unix password manager

#95
post #85

Is there a way to synchronize this with 1Password via a plug-in? I would like to use pass as another backup of my 1Password database.

There are plugins for importing into pass from all kinds of password managers. ( https://github.com/roddhjav/pass-import#readme ) You could setup a cron job that polls 1Pass for your password CSV, imports the CSV into to pass, and commits the diff. Caveat that I don’t know how robust 1Password’s API is, or indeed if they have one. You might need to do the “gimme all my passwords in a CSV” step through a GUI, or a ver…

1password has a decent cli that's essentially a thin wrapper around their api. It mostly outputs json.

Re: Pass: The standard Unix password manager

#96

I don't use pass myself (I have severe NIH[1]), but its design has inspired me many times over: very, very few tools rise to the challenge of adhering to the Unix philosophy without cargo-culting it, and pass is one of them. I highly recommend that people looking to write engineer-friendly tools study its manpage[2]. [1]: https://github.com/woodruffw/kbs2 [2]: https://git.zx2c4.com/password-store/about/

Similarly, I wrote "hunter2" [0] to manage my passwords, for places where I'm still forced to use passwords. Although I didn't know of "pass" when I wrote it, it accomplishes the same goals. One difference is that it doesn't rely on PGP keys but just uses bare RSA keys from a smartcard. This is because the vast majority of authentication systems I work with use an X.509 certificate with an RSA key pair, hardly anything uses a password any more (since doing so requires a lot of paperwork).

[0] https://chiselapp.com/user/rkeene/repository/hunter2/

Re: Pass: The standard Unix password manager

#97
post #71

I love the simplicity of Pass, but I wanted just a few more features, like being able to store (and retrieve) extra data easily. Unstructured data below the initial password wasn't really enough for me. I ended up taking huge inspiration from Pass, but writing my own implementation[1] with a few more features that increased it's usefulness for my use cases. I posted it a while ago on here[2] and Reddit[3], but it bas…

In my pass files, I put the password as the first line, optional username as second line, then I format the rest of the file as a YAML doc. So you can decrypt the file, scan for the first "---" and then everything after that is YAML (or multiple YAML docs if you have more "---").

Regardless, cool little set of programs you have!

Re: Pass: The standard Unix password manager

#98
post #47

I've been using pass for several years now and I recommend it to my friends, but I usually get weird looks when I say I store my passwords in a git repo (it's not as bad as it sounds!). Here's why: - I host my git repo on my desktop computer (through SSH), so it's not exposed anywhere except if you have SSH access to my computer. (A lot of people seem to think git = GitHub which is not true). So if your git repo is n…

You could also store it in a Keybase [1] repo. [1] https://keybase.io/

Isn't that now owned by Zoom?

Re: Pass: The standard Unix password manager

#99

Been planning to switch to pass for a while now because it looks nice! Is there a comfortable way to store+access arbitrary files and/or attachments with pass?

    # pipe an arbitrary file into pass
    cat ~/Desktop/test-image.png | pass insert -m test-image
    
    # get the arbitrary file out of pass
    pass show test-image > /tmp/test-image.png

Re: Pass: The standard Unix password manager

#100

I love the idea of Pass, but from what I've seen of the UX (not talking looks) it doesn't really compare to the ease of use of products like 1Password (which I suspect was the catalyst for this being reposted). Does anyone have any contrary experiences when shared across iOS, Linux, and macOS devices + browsers?

I don't use Windows, but I very easily use pass across multiple Linux, Mac, and Android devices. Sometimes I forget to git push something, but that's pretty rarely an issue for me. Set up requires a bit more work than 1Password, etc. but I still think it's pretty easy to set up.

On my computer, I actually like the UI more than anything else because I use ZSH completion for pass and FZF for history search and thus copying any password is just like 5 keystrokes on average.

Post reply on HN