pass-tomb

I imagine it might be obvious for most users and potential users of pass, and being in line with the unix philosophy, it might be by design, but still, since I didn't see it mentioned in the documentation, it's worth mentioning: By itself, Passwordstore will not encrypt file names or directory names (which by convention represent the names of the service/site you have an account with). That might not pose a problem if no one else has access to the machine that hosts your git repo, but if that's not the case (even if it's a private repo on whatever platform), you might want to use either Tomb or git-crypt-remote to have full end-to-end encryption. There are even some tools that glue tomb and pass together (https://github.com/roddhjav/pass-tomb for one), though I'm not sure what's the situation is like when it comes to mobile integration wi

There's also the pass-tomb extension [0] which stores the directory in a tomb [1]. [0] https://github.com/roddhjav/pass-tomb [1] https://www.dyne.org/software/tomb/

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

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

That is what something like Gocryptfs would be good at masking: https://wiki.archlinux.org/index.php/Gocryptfs Or there is an extension called pass-tomb: https://github.com/roddhjav/pass-tomb

I remember reading somewhere that Pass could be used with libsodium (or age), but I cannot find the source now, sorry. One difference I see between this and pass is that spicypass is storing all the credentials in a single file. If you don't want to leak metadata with pass you have to add pass-tomb[1]. Anyway I just use pass (gopass actually) and I have no problems, it's a great improvement over a text editor. [1] https://github.com/roddhjav/pass-tomb

You could always use pass-tomb, which is an extension that stores the entire tree encrypted. https://github.com/roddhjav/pass-tomb#readme

I also started using pass when migrating. I've been nothing but happy with it. It's fast, easy to host either at home, or through Bitbucket or Github, and has clients (which IMO could all be better) for just about everything i need. I wish the iOS app would support tombs/vaults though. https://github.com/roddhjav/pass-tomb#readme

I stopped as well, but went for a different setup: Tomb [1] and Pass [2]. There's even a combination of the two: pass-tomb [3], but I don't use it. No cloud, only USB keys. The thing is, I lost two of these USB keys! Had to rotate my passwords ;) [1]: https://github.com/dyne/Tomb [2]: https://github.com/zx2c4/password-store [3]: https://github.com/roddhjav/pass-tomb

>The only downside is that filenames are stored unencrypted in git repository so Bitbucket can see what sites do I use but can't see usernames or passwords (obviously). there's an extension to fix that: https://github.com/roddhjav/pass-tomb

Yes, the contents of the git repository holding your pass files are encrypted, meaning that the file names are not visible to anyone without the private key (you). You may also want to look at https://github.com/roddhjav/pass-tomb

Since pass supports extension, you can make your setup less complex using pass-tomb. 'pass-tomb' keep the whole tree of password encrypted inside a tomb, see https://github.com/roddhjav/pass-tomb

This "issue" has been fixed with the pass extension 'pass-tomb' that keep the whole tree of password encrypted inside a tomb See https://github.com/roddhjav/pass-tomb However keep in mind it's not always a big "issue", for instance only looking at your browser history will retrieve the same knowledge.

This "issue" has been fixed with the pass extension 'pass-tomb' that keep the whole tree of password encrypted inside a tomb See https://github.com/roddhjav/pass-tomb