Show HN: masterkey – secure interactive password manager using Go and NACL

github.com

47 points·roughly27··10 comments

> Passwords are always encrypted using a scrypt key derived from the input passphrase

If this is correct then I'm not sure if it's best approach. My understanding is that in for example keepass there is a separate random key that is used to encrypt the data, and then this key is encrypted using whatever method user uses.

Yes, this is so you can change the password without needing to encrypt everything again.

I'm always interested in seeing new open source password management solutions. Unfortunately being limited to user/pass/location is a deal-breaker for me. The only decent tool I've found that provides additional fields is KeePassX.

pass lets you add any field you want: https://www.passwordstore.org/

pass is very nice, but has some annyoing useability quirks.

Would you care to elaborate?

And there's a GUI as well available, https://qtpass.org/

I agree unfortunately.

There is one web app that has this potential, Siptrackweb.

I've looked closely at the code and it clearly has potential to add attributes, or additional fields, to password nodes in its database. But right now it does not offer this feature for passwords, only for other types of nodes like devices and device categories.

1Password allows for additional fields

Thanks for the feedback. I'll be adding support for additional fields soon.

Reply on news.ycombinator.com