Earlier quoted context omitted.
I like and use pass regulary, but it has some inconveniences. - It doesn't encrypt the paths to the passwords - It doesn't use a structural language for the password files, so additional information like username has to be stored in the path of the password - It doesn't work with (Update: X.509) smartcards/gpgsm - It's written in bash. That has pros and cons...
> - It doesn't use a structural language for the password files, so additional information like username has to be stored in the path of the password only the first line of an encrypted file is considered to be the password. So you can just but your username or any other account-related information on the following lines. > - It doesn't encrypt the paths to the passwords To elaborate: One of the problems with this ap…
> only the first line of an encrypted file is considered to be the password. So you can just but your username or any other account-related information on the following lines.
I didn't know that. But what I would have preferred was copying the username with one command and copying the password with another.
>> - It doesn't work with smartcards/gpgsm
> What do you mean by that? I use pass with my yubikey as a gpg "smartcard"?
I haven't tried that with a yubi key, but with a corporate X.509 id card. And that needed gpgsm. I had to patch pass in order for it to work, because gpgsm uses different parameters that gpg.