Earlier quoted context omitted.
You could also store it in a Keybase [1] repo. [1] https://keybase.io/
Isn't that now owned by Zoom?
Holy crap, you're right.
Pass: The standard Unix password manager
111–120 of 213 posts
Re: Pass: The standard Unix password manager
#112Who decided that this is somehow a standard?
People who use it, like any other standard.
Re: Pass: The standard Unix password manager
#113I've just recently started to use 1password and here're my thoughts:
- Amazing support and fast response on their forums from the reps
- Works across Linux (my desktop), Mac and iPhone and Safari and Chrome browsers
- Has CLI
- Syncs instantly (unlike Chrome and iCloud Keychain)
- Supports TOTP (no - it does not completely defeat the purpose of 2FA, there are multiple aspects to it)
I am also aware of the risk I'm taking by trusting a 3rd party commercial company with my credentials.
Re: Pass: The standard Unix password manager
#114I love pass but I have been having very weird issues lately with gpg agent taking ages to ask me my password to decrypt the database. Really annoying and googling has not yielded fixes. Worse the dev doesn’t use GitHub so getting in touch is a giant pain in the ass.
Re: Pass: The standard Unix password manager
#115Re: Pass: The standard Unix password manager
#116Here are some of the pros of the Pass: * It leaks meta-data. That might sound a con, but in exchange you get the ability to extract a password without decrypting and thus exposing other passwords. There is isolation. * It’s more convenient than a single file password manager. You type ‘’pass -c goo’’ for your Google account, instead of clicking on your password manager, typing password, searching in data base, findin…
> For example, if you store your database on a cloud, say, Dropbox, Dropbox could switch your Dropbox.com file with google.com file That's sad- could we include a hash to detect stuff like this?
[deleted]
Re: Pass: The standard Unix password manager
#117Who decided that this is somehow a standard?
It's an amusing reference to the cheeky line from the historic Unix man page for `ed`; "the standard Unix editor".
RE: who decided.. well, the presence of `ed` was a requirement for an OS to be accredited as POSIX-compatible, so that's presumably why `ed` decided to describe itself as 'the standard'. But `ed` fell so far out of favor once screen-based editors (`vim`, `emacs`, etc) became commonly available that the "the standard" line which continued to hang around in ed's documentation became a bit of a Unix in-joke.
The modern GNU version of the `ed` tool describes it as "line-oriented text editor" instead of as "the standard Unix text editor". And only briefly mentions the old phrase in an apologetic explaining why that old phrase was used in the past.
So the short version of the answer: it's not. It's an in-joke which is attempting to draw to mind a comparison of this software against older, simpler Unix tools like `ed`. Which IMHO is totally valid, if you say pass is to lastpass as ed is to vscode. Simpler tool, possibly easier to use for keyboard-focused folks, focuses on doing just one thing and doing it well, etc.
Re: Pass: The standard Unix password manager
#118I'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…
So your git repo and GPG key are stored on the same device? What happens when that device is stolen?
Re: Pass: The standard Unix password manager
#119Earlier quoted context omitted.
Not sure what any of the above have to do with this app... "- i share these random passwords with my team (ugh... git i guess huh!)" Git doesn't mean you "share" anything. First, you can use a private repo, second your passwords are encrypted. Unless you give the master key, nobody "shares" your passwords, even if they have access to the git repo.
I'm saying the tool works for a subset of uses for generated encrypted password stores. Unless I misunderstand and this is entirely for secret sharing between servers, in which case I retract everything I said.
If your team has GPG keys (they should if they're signing Git commits) then pass works great for teams as well. You can encrypt to multiple GPG key IDs so many users and decrypt passwords from a shared git repo.
Re: Pass: The standard Unix password manager
#120here's why this is a bad idea: - i generate random passwords for myself (yay) - i share these random passwords with my team (ugh... git i guess huh!) - i share some of these random passwords with my family (you try teaching a 6 year old git, and a 37 year old woman who already doesn't want to change her habits) - i use these passwords on my home computer (windows), work computer (osx), android, ios Yeah, not going to…
Gopass allows you to share passwords and encrypt with multiple GPG keys.
As does pass itself.