Live data from Hacker News

Pass: A standard Unix password manager

passwordstore.org

41–50 of 212 posts

Re: Pass: A standard Unix password manager

#41
post #37

Anybody else here simply hashing their master password with the domain name of the website? I think this is something the browser should offer by default.

If your master password leaks you are exposed on every website where you used this scheme (and you should then change every password), so on the security side this is inferior to a master password granting access to uncorrelated passwords.

Re: Pass: A standard Unix password manager

#42
post #36

Earlier quoted context omitted.

Clearing the clipboard protects against the user. A password manager effectively can't protect against other applications on the same machine. IMO that makes the universality of the clipboard more valuable than the safety of using alternate input methods. Though since there are plenty of things that block pasting passwords, those alternate options are appreciated.

to be honest, I can trust myself with clipboard but not what is running on my machine.

Then you can't use that machine. Not with a password manager, not without.

Re: Pass: A standard Unix password manager

#44
post #37

Anybody else here simply hashing their master password with the domain name of the website? I think this is something the browser should offer by default.

What about websites that require to have special characters in your password, since the hash is just HEX? What about multiple accounts on the same website, same password?

Re: Pass: A standard Unix password manager

#45
post #41
post #37

Anybody else here simply hashing their master password with the domain name of the website? I think this is something the browser should offer by default.

If your master password leaks you are exposed on every website where you used this scheme (and you should then change every password), so on the security side this is inferior to a master password granting access to uncorrelated passwords.

Well, you can add a salt to this scheme.

I know, it's not perfect, but it beats carrying around password files between devices.

Re: Pass: A standard Unix password manager

#46
I use pass and love it. It provides a lot of flexibility. To fix the "website metadata is leaked in filenames" issue, I use another project by Jason, ctmg[0]. I changed the pass directory to be one directory deeper, encrypted it and just do `ctmg open` when I boot to open my password list (similar to unlocking a keypassX store) then use pass as normal. On shutdown, the opened folder is re-encrypted automatically. You could also set a ctmg close on a timer if you don't want the list to be available during your entire session after open.

Other things I do:

* store all the files as .toml files so I can rip specific keys with a custom script.

* Have a directory for web so `pass web` will give me all websites. Have a script to fill username pass for each.

* Have a directory for contacts. Then wrote a script to generate vCard files by crawling and pulling keys, base64 profile images and all.

* use syncthing to keep all devices up to date.

It's pretty slick workflow IMHO

[0] https://git.zx2c4.com/ctmg/about/

Re: Pass: A standard Unix password manager

#48
post #37

Anybody else here simply hashing their master password with the domain name of the website? I think this is something the browser should offer by default.

Yes, I do something like this, along with storing the password requirements and username/domain in localStorage and allowing it to sync between devices: https://webpass.rkeene.org/

Re: Pass: A standard Unix password manager

#49
post #20

Pass is pretty awesome, but nowadays I've switched to gopass: https://github.com/justwatchcom/gopass - much better support for teams, structured secrets, binary secrets and quite a few other improvements. Oh, and it's (mostly) drop-in compatible.

Looks nice. Unfortunately I would never use it for teams as it doesn't have audit logs. These are very useful in case a user is compromised - you can lookup which passwords he accessed and only change those. Same goes if the user left the team and u want to make sure all accesses are revoked.

"you can lookup which passwords he accessed"

Really? What if s/he just decrypted the file themselves and had a look at the content, rather than using the convenient wrapper that a password manager provides?

Re: Pass: A standard Unix password manager

#50
post #36

Earlier quoted context omitted.

to be honest, I can trust myself with clipboard but not what is running on my machine.

Then you can't use that machine. Not with a password manager, not without.

so you know and trust every piece of software that is running on your machine?
Post reply on HN