undefined | Better HN

0 pointskoolba10y ago0 comments

> The main knock against KeePass for teams is that it's all or nothing.

... and the binary format makes KeePass merges impossible. Even if it's just you, if you have multiple computers you need to make sure you have the latest copy before adding something.

That's what's nice about pass, it plays nice with git, rsync, and just about everything else. Last write wins per credential. If you tack on history with git (or ZFS snapshots!) you have a central copy that you can share among a team.

Someone should make a slick UI atop a pass directory with a browser plugin.

0 comments

3 comments · 1 top-level

aeorgnoieang10y ago· 2 in thread

Thanks for pointing out `pass`!

I've been manually merging a set of Password-Safe-format password files (one for each of my many computers) and I've been thinking about alternatives for a long while. I was actually thinking about how I could combine encrypted files with Git to get history and painless merging – I'm glad to know that someone else had the same ideas!

drdaeman10y ago

Pass has one limitation - having filenames in plaintext. This could or could not be an issue for local repositories, but this is definitely an issue for remotes.

Sadly, Android client (which is quite good otherwise) doesn't support git-remote-gcrypt.

aeorgnoieang10y ago

> having filenames in plaintext

Why is this a limitation? Are you stating that each file in the 'repo' is encrypted separately? I figured it was the entire repo as a directory, in which case, when it's 'at rest', the whole thing is encrypted as a blob.

1 more reply

j / k navigate · click thread line to collapse