3 ms·
I wrote a pass equivalent for KeePass for this very reason [0]. It doesn't leak any metadata because everything is contained in a single file and it's compatib
by Evidlo 6y ago
I wrote a pass equivalent for KeePass for this very reason [0].
It doesn't leak any metadata because everything is contained in a single file and it's compatible with the rest of the KeePass ecosystem.
[0]: https://github.com/Evidlo/passhole/ https://github.com/Evidlo/passhole/
- dopidopHN 6y agoHi, I keep reading that argument in that thread about the metadata being leaked and I feel left out of the party. How is it leaking? Why do we have to care and could some mapping of the file name to a encrypted key on map-table solve that ?
- merlincorey 6y agoA common way to use `pass` is to store things like `organization/domain/username` so for example it might be `goldmansachs/github.com/alphacoder` which is telling us that you do some work for Goldman Sachs who store stuff on Github and your username is alphacoder.