News for hackers. Stuff that matters.
Re:pass – the standard Unix password manager by blueflow on Friday June 17, 2022 @05:16AM (#31775836)
I mean, if the attacker has writable access to your vault, he likely can observe you handling the unencrypted password or steal all your gpg key material after you unlocked it. This makes the "No binding between keys/values", "No authentication of values" and "My passwords are emails?" sections moot.
Re:pass – the standard Unix password manager by upofadown on Friday June 17, 2022 @06:41AM (#31776320)
>I mean, if the attacker has writable access to your vault, he likely can observe you handling the unencrypted password or steal all your gpg key material after you unlocked it.

To be clear here, only if that implies access to the memory you control, otherwise, no. GPG is pretty good about local file access by an attacker and pass maintains that on platforms where that is possible.

Re:pass – the standard Unix password manager by blueflow on Friday June 17, 2022 @06:56AM (#31776432)
I would not assume the memory separation on x86 to be reliable.
Re:pass – the standard Unix password manager by gnull on Friday June 17, 2022 @09:01PM (#31786389)
Access to the vault ≠ access to unlocked vault. This is the whole point of storing anything encrypted on your disk.

The password managers don't protect against a malware running on your laptop with root privileges and attaching to your processes. They protect against someone taking the disk out of your computer and trying to extract the passwords.

Re:pass – the standard Unix password manager by blueflow on Saturday June 18, 2022 @05:23AM (#31788416)
But if they have the disk and modify is, its still them who have the disk. So the "No binding between keys/values" and "No authentication of values" still dont work out, either. And they are able to modify the contents on my disk, they'd be easier off installing a rootkit, pass cant protect against that.