Re: Brace yourself: User-friendly but broken OpenPGP is here

2020-08-30 Thread Werner Koch via Gnupg-users
On Sun, 30 Aug 2020 00:50, Johan Wevers said: > Sorry, I see from Vincent's mail that GnuPG already does this but it > might be the keycard that is causing this. Right, smartcards are pretty strict in what they accept as input. Thus you can't use certain keys on a smartcard for different purpos

Re: Brace yourself: User-friendly but broken OpenPGP is here

2020-08-29 Thread Johan Wevers
I wrote: > It would be nice if GnuPG implemented an override option to use this key > for decryption anyway. Sorry, I see from Vincent's mail that GnuPG already does this but it might be the keycard that is causing this. -- ir. J.C.A. Wevers PGP/GPG public keys at http://www.xs4all.nl/~johanw/

Re: Brace yourself: User-friendly but broken OpenPGP is here

2020-08-29 Thread Vincent Breitmoser via Gnupg-users
> A closer inspection of the key ID showed that it was encrypted with my master > key. A key that is not marked to be used for encryption. So how the heck did > that happened? I believe what you're experiencing here is actually a direct consequence of a GnuPG policy decision: Subkeys that don't

Re: Brace yourself: User-friendly but broken OpenPGP is here

2020-08-29 Thread Johan Wevers
On 29-08-2020 16:17, Sheogorath via Gnupg-users wrote: > A closer > inspection of the key ID showed that it was encrypted with my master > key. A key that is not marked to be used for encryption. It would be nice if GnuPG implemented an override option to use this key for decryption anyway. The al

Brace yourself: User-friendly but broken OpenPGP is here

2020-08-29 Thread Sheogorath via Gnupg-users
Hello to everyone, Today I got an encrypted email from a friend that turned out to be undecryptable in first place. After my evolution integration failed, I checked manually using gpg --decrypt. This provided me with the lovely statement of: gpg: encrypted with 4096-bit RSA key, ID FCB98C2A3EC6F