Re: Cipher Preferences Ignored for Kyber keys?

--===============5675224668245685180==
Content-Type: multipart/signed;
 boundary=d34fb8a77602c83a625ae018e7057acbc96ebaaa6e0a52e077a6bc0ba4c8;
 micalg=pgp-sha512; protocol="application/pgp-signature"

--d34fb8a77602c83a625ae018e7057acbc96ebaaa6e0a52e077a6bc0ba4c8
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=UTF-8

On Sun Jul 26, 2026 at 12:07 AM BST, scuffbox via Gnupg-users wrote:
> On upgrading to 2.5.x (2.5.20 and 2.5.21) recently to test Kyber keys,=20
> I have noticed that any preferences relating to cipher choice are=20
> being ignored.
>
> AES256 appears to be used for encryption to Kyber subkeys regardless=20
> of the contents of the public key's cipher preferences and the local=20
> config's personal-cipher-preferences.

Indeed. This is a deliberate behaviour, see the discussion on issue=20
https://dev.gnupg.org/T7472.

When all the keys we are encrypting to are Kyber keys, then AES-256 is=20
forcefully used regardless of the preferences.

You can still force the use of any other supported encryption algorithm=20
with the `--cipher-algo` option.

- Damien

--d34fb8a77602c83a625ae018e7057acbc96ebaaa6e0a52e077a6bc0ba4c8
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iJEEABYKADkWIQSAzBuNBMJi3f7hmAxvfw+R0Tj8ewUCamYbKBsUgAAAAAAEAA5t
YW51MiwyLjUrMS4xMiwwLDMACgkQb38PkdE4/Ht87QEA3kRV1NEbHlIzeBZRo773
4spklFBfErQqePC6Kv8sDFcA/2zk5P06nvMOL+epbNnPhH9DR+aYV0tdvAfsQWtl
hNEG
=ws/v
-----END PGP SIGNATURE-----

--d34fb8a77602c83a625ae018e7057acbc96ebaaa6e0a52e077a6bc0ba4c8--


--===============5675224668245685180==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Gnupg-users mailing list
[email protected]
https://lists.gnupg.org/mailman/listinfo/gnupg-users

--===============5675224668245685180==--