Re: Re: 12.2.0.3 Autocrypt: GnuPG does not import public key from mail header?

This is a multi-part message in MIME format...

------------=_1780833916-43421-229
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: QUOTED-PRINTABLE
Content-length: 1426

Hi all,

I was on the receiving end of Gwens Mail. To explain the issue in detail.

We both had Autocrypt enabled, we both use GnuPG/Kleopatra.

Difference is, Gwen generated a key within the autocrypt menu, I did not, I
just choose my existing via GnuPG generated RSA-4096 Key (encryption, signi=
ng
and  authentification subkeys stored on an Yubikey, if that matters).

When Gwen send me a signed mail, I was able to import his public key via a =
new
menu dialog in the "check Open-PGP signature" button. I think it's new, nev=
er
saw this before. The key was than visible in Kleopatra as well. So, I think
Gwens mail had an autocrypt mail-header with his key.

When I replied to Gwen, there was no such menu-option for him. I guess me
reply did not had that mail-header and that has something to do, that I do =
not
generate a key in autocrypt settings or that me key is somehow not autocryp=
t-
conform.

In the autocrypt doc I read the following:
"What about other keys, that i have been using with other properties? (smar=
t-
card, RSA, =E2=80=A6)
You can still create a compatible header with a tool we will provide."

https://docs.autocrypt.org/other-crypto-interop.html#for-current-openpgp-us=
ers

Maybe thats my case here. But I don't know what "providing a tool" means.

So yeah, the question for me also is how does autocrypt with GnuPG actually
work especially if you want to use your existing key.

Thanks
June

------------=_1780833916-43421-229
Content-Type: text/plain; charset="UTF-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0

________________________________________________________
'Using TBBETA' information:
http://www.silverstones.com/thebat/TBUDLInfo.html

------------=_1780833916-43421-229--