boredsquirrel OP , 4 months ago

With pass, each password lives inside of a gpg encrypted file whose filename is the title of the website or resource that requires the password. These encrypted files may be organized into meaningful folder hierarchies, copied from computer to computer, and, in general, manipulated using standard command line file management utilities.

This sounds cool, but relies completely on OpenPGP. That is secure enough, right?

But this also means

• no metadata security
• no usernames
• no comment

It is cool, but only having a single entry means you can not replace the website with a more anonymous placeholder.

For sure this tool sounds pretty great! Especially encrypting everything seperately is very nice.

But sometimes getting a name might already be too much.

Also to avoid big brother connecting all data, I normally have an entry like

<span style="color:#323232;">Entry: MSOffice
</span><span style="color:#323232;">username: [email protected]
</span><span style="color:#323232;">password: •••••••••••••••••••••
</span><span style="color:#323232;">URL: xxxxx
</span><span style="color:#323232;">Comment:
</span><span style="color:#323232;">   Username: xxxxxxxxx
</span><span style="color:#323232;">   name: albert einstein
</span><span style="color:#323232;">   birthday: 2.6.1956
</span><span style="color:#323232;">   Security question 1 2 3
</span><span style="color:#323232;">   TOTP backup keys: xxxx
</span><span style="color:#323232;">   Random comment
</span>

This is all not possible, which means I would need the same username everywhere, or remember it (I dont, I have 300 Keepass entries).

In KeepassXC I have a single file. Hackers would need to bruteforce only one. But at least they wouldnt know exactly what they want to decrypt.