Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Pass: A standard Unix password manager

passwordstore.org

Post reply on HN
Print view View original

161–170 of 212 posts

Re: Pass: A standard Unix password manager

#161

Post by arthulia »

guillaume20100 wrote: post #158

I recommend using Pass or Keepass, because we can see the source code. But like all these password managers, you need to synchronize your password vault. If you do not want to synchronize your vault among all your devices, but still want to have a unique password per site, try LessPass[1]. LessPass is a stateless open source password manager. Disclaimer I am the creator of LessPass [1] https://lesspass.com/

This is pretty brilliant. My biggest concern is that if my password for a site gets compromised, it gets a lot more complicated. Presumably I'd have to memorize a separate master password for retrieving the new password for that site.

Re: Pass: A standard Unix password manager

#162

Post by [deleted] »

guillaume20100 wrote: post #158

I recommend using Pass or Keepass, because we can see the source code. But like all these password managers, you need to synchronize your password vault. If you do not want to synchronize your vault among all your devices, but still want to have a unique password per site, try LessPass[1]. LessPass is a stateless open source password manager. Disclaimer I am the creator of LessPass [1] https://lesspass.com/

[deleted]

Re: Pass: A standard Unix password manager

#163

Post by [deleted] »

guillaume20100 wrote: post #158

I recommend using Pass or Keepass, because we can see the source code. But like all these password managers, you need to synchronize your password vault. If you do not want to synchronize your vault among all your devices, but still want to have a unique password per site, try LessPass[1]. LessPass is a stateless open source password manager. Disclaimer I am the creator of LessPass [1] https://lesspass.com/

[deleted]

Re: Pass: A standard Unix password manager

#164

Post by prophesi »

arthulia wrote: post #161
guillaume20100 wrote: post #158

I recommend using Pass or Keepass, because we can see the source code. But like all these password managers, you need to synchronize your password vault. If you do not want to synchronize your vault among all your devices, but still want to have a unique password per site, try LessPass[1]. LessPass is a stateless open source password manager. Disclaimer I am the creator of LessPass [1] https://lesspass.com/

This is pretty brilliant. My biggest concern is that if my password for a site gets compromised, it gets a lot more complicated. Presumably I'd have to memorize a separate master password for retrieving the new password for that site.

They have a counter option that you can increment which allows you to generate a completely different password for the same site.

Re: Pass: A standard Unix password manager

#165

Post by arthulia »

prophesi wrote: post #164
arthulia wrote: post #161

Earlier quoted context omitted.

This is pretty brilliant. My biggest concern is that if my password for a site gets compromised, it gets a lot more complicated. Presumably I'd have to memorize a separate master password for retrieving the new password for that site.

They have a counter option that you can increment which allows you to generate a completely different password for the same site.

But then you have to remember the counter setting for that website. So it's almost the same problem; I could just add a 1 to the end of my master password for that website.

Re: Pass: A standard Unix password manager

#166

Post by prophesi »

arthulia wrote: post #165
prophesi wrote: post #164

Earlier quoted context omitted.

They have a counter option that you can increment which allows you to generate a completely different password for the same site.

But then you have to remember the counter setting for that website. So it's almost the same problem; I could just add a 1 to the end of my master password for that website.

No, the counter would be saved by LessPass. Every time you look up the password for that site, it'll already know what the counter is set to for that site.

This blog post[0] shows how LessPass lets you change passwords per site, and get around tricky password requirements.

[0] https://blog.lesspass.com/lesspass-how-it-works-dde742dd18a4

Re: Pass: A standard Unix password manager

#167

Post by hansjorg »

arthulia wrote: post #165
prophesi wrote: post #164

Earlier quoted context omitted.

They have a counter option that you can increment which allows you to generate a completely different password for the same site.

But then you have to remember the counter setting for that website. So it's almost the same problem; I could just add a 1 to the end of my master password for that website.

I've just installed it and haven't yet used it, but as far as I can tell from the docs, the counter is stored as part of the syncable profile for a site.

The profile is also used to store other site-specific attributes, like if it has some weird password rule that requires pure alphanumeric or a specific password length.

Re: Pass: A standard Unix password manager

#168

Post by pavon »

YorickPeterse wrote: post #27
alex_duf wrote: post #26

I don't like the fact someone with access to my hard-drive can figure out all the services I'm using just by looking at the filenames. It's convenient yes, but I prefer one encrypted file that contains it all.

This shouldn't really be an issue if you're using full disk encryption.

Encryption only protects files at rest. The vast majority of attacks are against live systems connected to a network, where full disk encryption won't help you one bit. It is a nice extra layer of protection for when a device is lost/stolen, but I don't consider it a primary form of protection for any important data.

Re: Pass: A standard Unix password manager

#169

Post by DavideNL »

marcv81 wrote: post #21
fwx wrote: post #2

How does this compare to other popular solutions? Specifically, KeepassX / Keepass2 which are the most common solutions I've seen most Unix / Linux users employ. Can we objectively state which one is a better solution?

Objective difference: KeePass encrypts the names of the websites where you have accounts. I would not want to live without this feature.

https://github.com/roddhjav/pass-tomb

Re: Pass: A standard Unix password manager

#170

Post by mmagin »

alexnewman wrote: post #155

I use pass on all my devices. IOS, chromebook and cli. I freaking love it! passforios is still on testflight but so good. Only a few issues with passforios: - It forgets my github password everytime i upgrade - I honestly don't like the fact that I can't turn off the pin. 4 digits with unlimited retries. - It can't merge sometimes. I think they should be more aggressive about git rebase

Thanks for mentioning it. I previously couldn't have my passwords available from my phone.

I created a seperate ssh key and did this on my server https://superuser.com/a/444899

Post reply on HN