Has anyone build a hash style password manager. hash(website name + global password + increment) = password to use? or something like it
Show HN: Passbox – Another password manager using Bash and GPG
31–34 of 34 posts
Re: Show HN: Passbox – Another password manager using Bash and GPG
#32Earlier quoted context omitted.
I suppose it just depends what you look for in a password manager. I tried lots of solutions from Last Pass, KeepassX to pass but i prefer the scriptability and portability of a command line based password manager and i'm not overly bothered about mobile and browser.
You're right, and don't take this as a challenge, I'm honestly wondering: How come you aren't bothered? I ask because I can't image apart from: a. I use short or cryptically unsafe passphrases, b. I use passphrases and type them easily, c. I only need to log in a few times. Am I forgetting others?
http://git.zx2c4.com/password-store/tree/contrib/dmenu/passm...
It types the selected password via xdotool.
Re: Show HN: Passbox – Another password manager using Bash and GPG
#33Earlier quoted context omitted.
Downside of pass is that the filenames are in the open. Thus, metadata (which sites you have account on) is not secured. Linked one seems to store everything in a single encrypted file. Upside is that it has ton of implementations readily available - browser integration, mobile apps, etc. Linked one (passbox) is just a bash script at the moment, if one wants to use it across multiple devices and platforms, the experi…
> Downside of pass is that the filenames are in the open. The "entry" names (which I think would correspond to filenames in `pass`) appear to be passed on the command line here; they'll likely get swept up in your shell's history file, unless you're careful. (And thus, are essentially in the open, just like pass.) That said, I think most shells make their histfiles 600, so they're not directly readable. (And I think…
But, yeah, if one forgot to add pass there, the metadata will be leaked.
Re: Show HN: Passbox – Another password manager using Bash and GPG
#34Earlier quoted context omitted.
> Downside of pass is that the filenames are in the open. The "entry" names (which I think would correspond to filenames in `pass`) appear to be passed on the command line here; they'll likely get swept up in your shell's history file, unless you're careful. (And thus, are essentially in the open, just like pass.) That said, I think most shells make their histfiles 600, so they're not directly readable. (And I think…
There is HISTIGNORE for a reason ;) But, yeah, if one forgot to add pass there, the metadata will be leaked.