Gnupg-users Digest, Vol 220, Issue 11

[Chris Taylor]

Hello,

Please unsubscribe me from this list.

Chris


On 10/01/2022 15:08, gnupg-users-request at gnupg.org wrote:
> Send Gnupg-users mailing list submissions to
> 	gnupg-users at gnupg.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> 	http://lists.gnupg.org/mailman/listinfo/gnupg-users
> or, via email, send a message with subject or body 'help' to
> 	gnupg-users-request at gnupg.org
>
> You can reach the person managing the list at
> 	gnupg-users-owner at gnupg.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Gnupg-users digest..."
>
>
> Today's Topics:
>
>     1. AW: GPG key generated on Windows... (Robert Flosbach)
>     2. Re: AW: GPG key generated on Windows... (Werner Koch)
>     3. Re: one ecc key-pair for both encryption and signature?
>        (Bernhard Reiter)
>     4. Re: Yubikeys and GnuPG 2.2/2.3 (Werner Koch)
>     5. Fwd: gpg: onepass_sig with unknown version 105
>        (Gilberto F. da Silva)
>     6. Re: one ecc key-pair for both encryption and signature?
>        (Robert J. Hansen)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sun, 9 Jan 2022 10:25:39 +0100
> From: "Robert Flosbach" <r.flosbach at gmx.de>
> To: <gnupg-users at gnupg.org>
> Subject: AW: GPG key generated on Windows...
> Message-ID: <003a01d8053a$de2469c0$9a6d3d40$@gmx.de>
> Content-Type: text/plain;	charset="UTF-8"
>
> Thank you very much for your help!
>
> For future reference and people having the same issue: gpg2.3 introduced a new packet type 20 which provides authenticated encryption with associated data (AEAD) [1]. A key generated with gpg2.3 supports this encryption type and encryption in Windows (using the current Gpg4win 4.0.0) defaults to AEAD for a key generated with default settings. Since AEAD/type 20 is not supported yet by version 2.2, decryption on linux distros is not possible using version 2.2.X from their repositories.
>
> [1] https://tools.ietf.org/id/draft-ietf-openpgp-rfc4880bis-06.html#rfc.section.5.16
>
>
>
>
> ------------------------------
>
> Message: 2
> Date: Sun, 09 Jan 2022 12:14:27 +0100
> From: Werner Koch <wk at gnupg.org>
> To: Robert Flosbach via Gnupg-users <gnupg-users at gnupg.org>
> Subject: Re: AW: GPG key generated on Windows...
> Message-ID: <87h7adtb3g.fsf at wheatstone.g10code.de>
> Content-Type: text/plain; charset="us-ascii"
>
> On Sun,  9 Jan 2022 10:25, Robert Flosbach said:
>
>> For future reference and people having the same issue: gpg2.3
>> introduced a new packet type 20 which provides authenticated
>> encryption with associated data (AEAD) [1]. A key generated with
>> gpg2.3 supports this encryption type and encryption in Windows (using
>> the current Gpg4win 4.0.0) defaults to AEAD for a key generated with
> There are two ways to change this: the first is to change the
> preferences on your key (using 2.3's --edit-key) and the second is to
> put
>
> --8<---------------cut here---------------start------------->8---
> ignore-invalid-option personal-aead-preferences
> personal-aead-preferences none
> --8<---------------cut here---------------end--------------->8---
>
> into gpg.conf .  From the man page:
>
>    --personal-aead-preferences string
>    
>      Set the list of personal AEAD preferences to string.  Use gpg
>      --version to get a list of available algorithms, and use none to set
>      no preference at all.  This allows the user to safely override the
>      algorithm chosen by the recipient key preferences, as GPG will only
>      select an algorithm that is usable by all recipients.  The most
>      highly ranked cipher in this list is also used for the --symmetric
>      encryption command.
>
> (the ignore-invalid-option line allows to use the same gpg.conf
>   also with gpg 2.2)
>
>
> Shalom-Salam,
>
>     Werner
>
>