4 ms·
For the structure I "solved" that problem by creating folders with three main files: Websites/foo.com/username Websites/foo.com/password Websites/f
by stevekemp 1y ago
For the structure I "solved" that problem by creating folders with three main files:
Websites/foo.com/username
Websites/foo.com/password
Websites/foo.com/email
Sometimes I add "/notes" with unstructured text contents, and for a few special cases I created a file "/json" with some machine-readable things in JSON format.
It's not perfect, and I do dislike the way that the metadata isn't encrypted, but on the whole I'm happy with the solution.
- integralid 1y agoYeah, but that's just your convention. I, for example, store password in private/foo.com/foo-com-login The first line of that file is password, the rest are optional notes. I think using first line for password and the rest for metadata was intended originally. I love pass, but I agree that it would be nice to have an established standard of where to put username etc.
- rendaw 1y agoYeah sure, but then are the conventions you came up with shared by all the tools in the ecosystem too (ex: browserpass)? Since the keystone (pass) declined to provide strong guidance, you end up with fragmentation and incompatibility.
- waynesonfire 1y agoI view this as a feature.