From gnupg-devel Wed Nov 22 08:15:02 2023 From: Bernhard Reiter Date: Wed, 22 Nov 2023 08:15:02 +0000 To: gnupg-devel Subject: Re: [PATCH gnupg] doc: update default-new-key-algo to ed25519 Message-Id: <202311220915.03215.bernhard () intevation ! de> X-MARC-Message: https://marc.info/?l=gnupg-devel&m=170064108317498 MIME-Version: 1 Content-Type: multipart/mixed; boundary="--===============3953043479276760795==" --===============3953043479276760795== Content-Type: multipart/signed; boundary="nextPart14174700.e18dIhCJB8"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit --nextPart14174700.e18dIhCJB8 Content-Type: multipart/mixed; boundary="Boundary-01=_GibXlNXbezobCNc" Content-Transfer-Encoding: 7bit Content-Disposition: inline --Boundary-01=_GibXlNXbezobCNc Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline > The problem for me is "the value of what was the previous default" is > awkward; I suggest instead saying "the previous default value" there. New patch attached, thanks. > Is this an awkward phrasing to optimize TeX typesetting? I don't know as I somehow kept the structure of the original sentence. =46eel free to improve the phrasing as the important part is that the chance in default is reflected here. (A potential additional improvement could be= =20 that it is generated into that place of the documentation, so it is not=20 forgotten next time the default is changed.) Regards, Bernhard --Boundary-01=_GibXlNXbezobCNc Content-Type: text/x-diff; charset="iso-8859-1"; name="0003-doc-update-default-new-key-algo-to-ed25519.patch" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="0003-doc-update-default-new-key-algo-to-ed25519.patch" =46rom 047b9ee39f5850e4ee332a766d32fe924960e7ee Mon Sep 17 00:00:00 2001 =46rom: Bernhard Reiter Date: Fri, 17 Nov 2023 16:58:53 +0100 Subject: [PATCH] doc: update default-new-key-algo to ed25519 * adust gpg.texi to mention the default for `--default-new-key-algo`, which was changed to ed25519 with ff31dde456f32950f0df6c974b4c41f1d650d6= 8f. =2D-- doc/gpg.texi | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/gpg.texi b/doc/gpg.texi index 17de880ea..bc60c4a47 100644 =2D-- a/doc/gpg.texi +++ b/doc/gpg.texi @@ -3775,9 +3775,9 @@ absolute date in the form YYYY-MM-DD. Defaults to "0". This option can be used to change the default algorithms for key generation. The @var{string} is similar to the arguments required for the command @option{--quick-add-key} but slightly different. For =2Dexample the current default of @code{"rsa2048/cert,sign+rsa2048/encr"} =2D(or @code{"rsa3072"}) can be changed to the value of what we currently =2Dcall future default, which is @code{"ed25519/cert,sign+cv25519/encr"}. +example the current default of @code{"ed25519/cert,sign+cv25519/encr"} +can be changed to the previous default: +@code{"rsa3072/cert,sign+rsa3072/encr"}. You need to consult the source code to learn the details. Note that the advanced key generation commands can always be used to specify a key algorithm directly. =2D-=20 2.30.2 --Boundary-01=_GibXlNXbezobCNc-- --nextPart14174700.e18dIhCJB8 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- iQGzBAABCgAdFiEEvdlX+cT+D9xYPc1tK3ujv5vDpVQFAmVduIYACgkQK3ujv5vD pVT+/gv/cbLnkoWuxZ+LtcG9t0ObqrqHStjCZRdLj0ofjPzd5wJwS6yx81ewc6f2 N4PS0xShWpozd8Rd4F5MJGoqT012NmhuRXL9AN/EK0Bok8MI8JQK9bxVIRQ9M//D GLuHfsrLLEXpZMmZ9K/ucjI0GFBJ22qZPWb3djRDHeEudpOuqkvAkhT6ltwxInzi nBao/e8CT6VJg+DVaumD/LCmkRy40vp51/vzsaSiJfz6xe6aHG/LwFy9qKsHviDd lNzMAX7tbTP/JghgNsCdmMCdsP4AoMlxr169gz3jIhCfhkOs7i7h+tmDSap4wzju t1m/FtX2dR02rWdo/BLCAcJHtsJU4N6vgoRf6YGX4GXoE8GtKpqEXZmnndqlO4+q KFQ1b9Kr+Du3+7km1XWm+rsQfafsYmj2iMzFudxYEEY6euhC6Vw+Z045/vl7mT+C MqE/Ifxk/N8aKbSEU9lHiD/AB9nMl83ryeE0sudt7hQerTBkx2sfjeRPtMAHc2IJ G4EUq9i8 =/2n2 -----END PGP SIGNATURE----- --nextPart14174700.e18dIhCJB8-- --===============3953043479276760795== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Gnupg-devel mailing list Gnupg-devel@gnupg.org https://lists.gnupg.org/mailman/listinfo/gnupg-devel --===============3953043479276760795==--