Improperly handling multi-recipient gpg-id

Open nazarewk opened this issue 3 years ago • 0 comments

current handling of gpg-id does not allow multiple recipient unlike pass itself

results in https://github.com/mdellweg/pass_secret_service/issues/34

my .gpg-id is:

% cat .gpg-id

0xEE8138A849922FE4!
0x1A2FFAA521ABECD3!
0xF7C76D9F5FC281A4!
0xBB8AEFC757E79220!

i see in logs:

gpg: 0xEE8138A849922FE4!\n0x1A2FFAA521ABECD3!\n0xF7C76D9F5FC281A4!\n0xBB8AEFC757E79220!: skipped: Invalid user ID
gpg: [stdin]: encryption failed: Invalid user ID

Oct 26 '22 09:10 nazarewk