From sbergman at redhat.com Thu Nov 5 16:38:01 2020 From: sbergman at redhat.com (Stephan Bergmann) Date: Thu, 5 Nov 2020 16:38:01 +0100 Subject: Fallout from _AC_UNDECLARED_WARNING in autoconf 2.70beta Message-ID: One issue I encountered in the wild (when building LibreOffice, with its zoo of bundled 3rd-party projects) with (the latest git trunk for) autoconf 2.70beta is related to how gpgme's configure.ac () is organized. (It may or may not be considered a regression in autoconf, or a bug in gpgme, hence I'm only writing here for now, not filing an issue. The relevant gpgme mailing list is on CC.) That configure.ac checks whether one specific GCC -Wno-missing-field-initializers flag is supported (l. 606), based on that one check optimistically goes ahead and adds a whole bunch of -Wno-... flags to CFLAGS, and only then (l. 661) happens to call _AC_UNDECLARED_WARNING (via gnupg_REPLACE_TTYNAME_R -> AC_CHECK_DECLS_ONCE -> _AC_CHECK_DECL_BODY) for the first time. If that configure is invoked with CC=clang supporting -Wno-missing-field-initializers but not supporting e.g. -Wno-format-truncation (which is among the bunch of flags optimistically added to CFLAGS), that was not much of an issue in the past; invocations of clang kept emitting noisy but harmless > warning: unknown warning option '-Wno-format-truncation' [-Wunknown-warning-option] lines. But now, _AC_CHECK_DECL_BODY fails hard with > configure:21628: checking how clang reports undeclared, standard C functions > configure:21645: clang -c -g -O2 -Wall -Wcast-align -Wshadow -Wstrict-prototypes -Wno-format-y2k -Wno-missing-field-initializers -Wno-sign-compare -Wno-format-zero-length -Wno-format-truncation -Wno-sizeof-pointer-div conftest.c >&5 > warning: unknown warning option '-Wno-format-truncation' [-Wunknown-warning-option] > conftest.c:51:8: warning: implicitly declaring library function 'strchr' with type 'char *(const char *, int)' [-Wimplicit-function-declaration] > (void) strchr; > ^ > conftest.c:51:8: note: include the header or explicitly provide a declaration for 'strchr' > 2 warnings generated. > configure:21645: $? = 0 > configure:21675: clang -c -g -O2 -Wall -Wcast-align -Wshadow -Wstrict-prototypes -Wno-format-y2k -Wno-missing-field-initializers -Wno-sign-compare -Wno-format-zero-length -Wno-format-truncation -Wno-sizeof-pointer-div conftest.c >&5 > warning: unknown warning option '-Wno-format-truncation' [-Wunknown-warning-option] > 1 warning generated. > configure:21675: $? = 0 > configure:21679: error: in `/home/sbergman/git.gnupg.org/gpgme': > configure:21681: error: cannot detect from compiler exit status or warnings One workaround is to move the gnupg_REPLACE_TTYNAME_R before the -Wno-missing-field-initializers etc. block in configure.ac. And maybe there would be a dedicated macro that can be called early to set up _AC_UNDECLARED_WARNING prior to modifying CFLAGS? From robbat2 at gentoo.org Mon Nov 9 00:31:48 2020 From: robbat2 at gentoo.org (Robin H. Johnson) Date: Sun, 8 Nov 2020 23:31:48 +0000 Subject: [PATCH] g10: --quiet should suppress notice about rejected third-party key signatures In-Reply-To: <20200520074413.GI150619@zeromail.org> References: <20200520052643.23627-1-robbat2@gentoo.org> <20200520074413.GI150619@zeromail.org> Message-ID: On Wed, May 20, 2020 at 09:44:13AM +0200, ilf wrote: > Thank you! > > There is an issue for this, but it's closed as "wontfix": > https://dev.gnupg.org/T4893 > > Robin H. Johnson via Gnupg-devel: > > Let --quiet hide the output about third-party key signatures: > > gpg: Note: third-party key signatures using the SHA1 algorithm are rejected > > This does not change actual behavior, it just omits that note instead. Can we please reopen this discussion about how to hide that message for automation cases? I'm specifically after hiding this message: "gpg: Note: third-party key signatures using the SHA1 algorithm are rejected" I have an automation use case where that message spams, and is already using --quiet. The alternative would be explicitly deleting some/many signatures before that point, which strikes me as suboptimal. I know there are OLD SHA1 signatures on some of the keys, they don't matter to the workflow. If you won't accept the patch to make --quiet ignore them, will you at least consider a patch that suppressed specific messages? e.g. --suppress-message=sha1-sig-3rd-party,md5-sig > > -- > ilf > > If you upload your address book to "the cloud", I don't want to be in it. > > _______________________________________________ > Gnupg-devel mailing list > Gnupg-devel at gnupg.org > http://lists.gnupg.org/mailman/listinfo/gnupg-devel > -- Robin Hugh Johnson Gentoo Linux: Dev, Infra Lead, Foundation Treasurer E-Mail : robbat2 at gentoo.org GnuPG FP : 11ACBA4F 4778E3F6 E4EDF38E B27B944E 34884E85 GnuPG FP : 7D0B3CEB E9B85B1F 825BCECF EE05E6F6 A48F6136 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 1113 bytes Desc: not available URL: From wk at gnupg.org Mon Nov 9 08:39:19 2020 From: wk at gnupg.org (Werner Koch) Date: Mon, 09 Nov 2020 08:39:19 +0100 Subject: [PATCH] g10: --quiet should suppress notice about rejected third-party key signatures In-Reply-To: (Robin H. Johnson via Gnupg-devel's message of "Sun, 8 Nov 2020 23:31:48 +0000") References: <20200520052643.23627-1-robbat2@gentoo.org> <20200520074413.GI150619@zeromail.org> Message-ID: <87zh3rrnbs.fsf@wheatstone.g10code.de> > I'm specifically after hiding this message: > "gpg: Note: third-party key signatures using the SHA1 algorithm are rejected" > > I have an automation use case where that message spams, and is already > using --quiet. Okay, I just pushed a change to act on --quiet for log_info (_("Note: third-party key signatures using" " the %s algorithm are rejected\n"), and log_info (_("Note: signatures using the %s algorithm are rejected\n"), gcry_md_algo_name(algo)); Thanks for insisting on this. Shalom-Salam, Werner -- Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 227 bytes Desc: not available URL: From wk at gnupg.org Tue Nov 17 11:17:11 2020 From: wk at gnupg.org (Werner Koch) Date: Tue, 17 Nov 2020 11:17:11 +0100 Subject: [Announce] GnuPG 2.2.24 released Message-ID: <87mtzgnv88.fsf@wheatstone.g10code.de> Hello! We are pleased to announce the availability of a new GnuPG release: version 2.2.24. This is maintenace release fixing some long standing bugs. See below for details. What is GnuPG ============= The GNU Privacy Guard (GnuPG, GPG) is a complete and free implementation of the OpenPGP and S/MIME standards. GnuPG allows to encrypt and sign data and communication, features a versatile key management system as well as access modules for public key directories. GnuPG itself is a command line tool with features for easy integration with other applications. The separate library GPGME provides a uniform API to use the GnuPG engine by software written in common programming languages. A wealth of frontend applications and libraries making use of GnuPG are available. As an universal crypto engine GnuPG provides support for S/MIME and Secure Shell in addition to OpenPGP. GnuPG is Free Software (meaning that it respects your freedom). It can be freely used, modified and distributed under the terms of the GNU General Public License. Noteworthy changes in version 2.2.24 ==================================== * Allow Unicode file names on Windows almost everywhere. Note that it is still not possible to use Unicode strings on the command line. This change also fixes a regression in 2.2.22 related to non-ascii file names. [#5098] * Fix localized time printing on Windows. [#5073] * gpg: New command --quick-revoke-sig. [#5093] * gpg: Do not use weak digest algos if selected by recipient preference during sign+encrypt. [4c181d51a6] * gpg: Switch to AES256 for symmetric encryption in de-vs mode. [166e779634] * gpg: Silence weak digest warnings with --quiet. [#4893] * gpg: Print new status line CANCELED_BY_USER for a cancel during symmetric encryption. [f05d1772c4] * gpg: Fix the encrypt+sign hash algo preference selection for ECDSA. This is in particular needed for keys created from existing smartcard based keys. [aeed0b93ff] * agent: Fix secret key import of GnuPG 2.3 generated Ed25519 keys. [#5114] * agent: Keep some permissions of private-keys-v1.d. [#2312] * dirmngr: Align sks-keyservers.netCA.pem use between ntbtls and gnutls builds. [e4f3b74c91] * dirmngr: Fix the pool keyserver case for a single host in the pool. [72e04b03b1a7] * scd: Fix the use case of verify_chv2 by CHECKPIN. [61aea64b3c] * scd: Various improvements to the ccid-driver. [#4616,#5065] * scd: Minor fixes for Yubikey [25bec16d0b] * gpgconf: New option --show-versions. * w32: Install gpg-check-pattern and example profiles. Install Windows subsystem variant of gpgconf (gpgconf-w32). * i18n: Complete overhaul and completion of the Italian translation. Thanks to Denis Renzi. * Require Libgcrypt 1.8 because 1.7 has long reached end-of-life. Release-info: https://dev.gnupg.org/T5052 Getting the Software ==================== Please follow the instructions found at or read on: GnuPG 2.2.24 may be downloaded from one of the GnuPG mirror sites or direct from its primary FTP server. The list of mirrors can be found at . Note that GnuPG is not available at ftp.gnu.org. The GnuPG source code compressed using BZIP2 and its OpenPGP signature are available here: https://gnupg.org/ftp/gcrypt/gnupg/gnupg-2.2.24.tar.bz2 (7027k) https://gnupg.org/ftp/gcrypt/gnupg/gnupg-2.2.24.tar.bz2.sig An installer for Windows without any graphical frontend except for a very minimal Pinentry tool is available here: https://gnupg.org/ftp/gcrypt/binary/gnupg-w32-2.2.24_20201117.exe (4322k) https://gnupg.org/ftp/gcrypt/binary/gnupg-w32-2.2.24_20201117.exe.sig The source used to build the Windows installer can be found in the same directory with a ".tar.xz" suffix. New versions of the GnuPG VS-Desktop(tm) as well as Gpg4win for Windows featuring this version of GnuPG will be released shortly. Checking the Integrity ====================== In order to check that the version of GnuPG which you are going to install is an original and unmodified one, you can do it in one of the following ways: * If you already have a version of GnuPG installed, you can simply verify the supplied signature. For example to verify the signature of the file gnupg-2.2.24.tar.bz2 you would use this command: gpg --verify gnupg-2.2.24.tar.bz2.sig gnupg-2.2.24.tar.bz2 This checks whether the signature file matches the source file. You should see a message indicating that the signature is good and made by one or more of the release signing keys. Make sure that this is a valid key, either by matching the shown fingerprint against a trustworthy list of valid release signing keys or by checking that the key has been signed by trustworthy other keys. See the end of this mail for information on the signing keys. * If you are not able to use an existing version of GnuPG, you have to verify the SHA-1 checksum. On Unix systems the command to do this is either "sha1sum" or "shasum". Assuming you downloaded the file gnupg-2.2.24.tar.bz2, you run the command like this: sha1sum gnupg-2.2.24.tar.bz2 and check that the output matches the next line: 2e8e29fdc06710d1e7f6f4b87098b96e058797fe gnupg-2.2.24.tar.bz2 eeefbaaecc4d69a3b66e1ce333c4c5081501310a gnupg-w32-2.2.24_20201117.tar.xz ab895bd9bc4319b88b1314ede3a816cd0a1cc677 gnupg-w32-2.2.24_20201117.exe Internationalization ==================== This version of GnuPG has support for 26 languages with Chinese (traditional and simplified), Czech, French, German, Italian, Japanese, Norwegian, Polish, Russian, and Ukrainian being almost completely translated. Documentation and Support ========================= If you used GnuPG in the past you should read the description of changes and new features at doc/whats-new-in-2.1.txt or online at https://gnupg.org/faq/whats-new-in-2.1.html The file gnupg.info has the complete reference manual of the system. Separate man pages are included as well but they miss some of the details available only in thee manual. The manual is also available online at https://gnupg.org/documentation/manuals/gnupg/ or can be downloaded as PDF at https://gnupg.org/documentation/manuals/gnupg.pdf . You may also want to search the GnuPG mailing list archives or ask on the gnupg-users mailing list for advise on how to solve problems. Most of the new features are around for several years and thus enough public experience is available. https://wiki.gnupg.org has user contributed information around GnuPG and relate software. In case of build problems specific to this release please first check https://dev.gnupg.org/T5052 for updated information. Please consult the archive of the gnupg-users mailing list before reporting a bug: . We suggest to send bug reports for a new release to this list in favor of filing a bug at . If you need commercial support go to or . If you are a developer and you need a certain feature for your project, please do not hesitate to bring it to the gnupg-devel mailing list for discussion. Thanks ====== Since 2001 maintenance and development of GnuPG is done by g10 Code GmbH and currently mostly financed by donations. Two full-time employed developers as well as two contractor exclusively work on GnuPG and closely related software like Libgcrypt, GPGME and Gpg4win. We like to thank all the nice people who are helping the GnuPG project, be it testing, coding, translating, suggesting, auditing, administering the servers, spreading the word, or answering questions on the mailing lists. Many thanks to our numerous financial supporters, both corporate and individuals. Without you it would not be possible to keep GnuPG in a good and secure shape and to address all the small and larger requests made by our users. Thanks. Happy hacking, Your GnuPG hackers p.s. This is an announcement only mailing list. Please send replies only to the gnupg-users'at'gnupg.org mailing list. p.p.s List of Release Signing Keys: To guarantee that a downloaded GnuPG version has not been tampered by malicious entities we provide signature files for all tarballs and binary versions. The keys are also signed by the long term keys of their respective owners. Current releases are signed by one or more of these four keys: rsa2048 2011-01-12 [expires: 2021-12-31] Key fingerprint = D869 2123 C406 5DEA 5E0F 3AB5 249B 39D2 4F25 E3B6 Werner Koch (dist sig) rsa2048 2014-10-29 [expires: 2020-10-30] Key fingerprint = 031E C253 6E58 0D8E A286 A9F2 2071 B08A 33BD 3F06 NIIBE Yutaka (GnuPG Release Key) rsa3072 2017-03-17 [expires: 2027-03-15] Key fingerprint = 5B80 C575 4298 F0CB 55D8 ED6A BCEF 7E29 4B09 2E28 Andre Heinecke (Release Signing Key) ed25519 2020-08-24 [expires: 2030-06-30] Key fingerprint = 6DAA 6E64 A76D 2840 571B 4902 5288 97B8 2640 3ADA Werner Koch (dist signing 2020) The keys are available at and in any recently released GnuPG tarball in the file g10/distsigkey.gpg . Note that this mail has been signed by a different key. -- Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 227 bytes Desc: not available URL: -------------- next part -------------- _______________________________________________ Gnupg-announce mailing list Gnupg-announce at gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-announce From wk at gnupg.org Mon Nov 23 19:00:22 2020 From: wk at gnupg.org (Werner Koch) Date: Mon, 23 Nov 2020 19:00:22 +0100 Subject: [Announce] GnuPG 2.2.25 released Message-ID: <87tutgj6mh.fsf@wheatstone.g10code.de> Hello! We are pleased to announce the availability of a new GnuPG release: version 2.2.25. This maintenance release fixes a minor regression introduced last week with 2.2.24. What is GnuPG ============= The GNU Privacy Guard (GnuPG, GPG) is a complete and free implementation of the OpenPGP and S/MIME standards. GnuPG allows to encrypt and sign data and communication, features a versatile key management system as well as access modules for public key directories. GnuPG itself is a command line tool with features for easy integration with other applications. The separate library GPGME provides a uniform API to use the GnuPG engine by software written in common programming languages. A wealth of frontend applications and libraries making use of GnuPG are available. As an universal crypto engine GnuPG provides support for S/MIME and Secure Shell in addition to OpenPGP. GnuPG is Free Software (meaning that it respects your freedom). It can be freely used, modified and distributed under the terms of the GNU General Public License. Noteworthy changes in version 2.2.25 ==================================== * scd: Fix regression in 2.2.24 requiring gpg --card-status before signing or decrypting. [#5065] * gpgsm: Using Libksba 1.5.0 signatures with a rarely used combination of attributes can now be verified. [#5146] Release-info: https://dev.gnupg.org/T5140 Getting the Software ==================== Please follow the instructions found at or read on: GnuPG 2.2.25 may be downloaded from one of the GnuPG mirror sites or direct from its primary FTP server. The list of mirrors can be found at . Note that GnuPG is not available at ftp.gnu.org. The GnuPG source code compressed using BZIP2 and its OpenPGP signature are available here: https://gnupg.org/ftp/gcrypt/gnupg/gnupg-2.2.25.tar.bz2 (7027k) https://gnupg.org/ftp/gcrypt/gnupg/gnupg-2.2.25.tar.bz2.sig An installer for Windows without any graphical frontend except for a very minimal Pinentry tool is available here: https://gnupg.org/ftp/gcrypt/binary/gnupg-w32-2.2.25_20201123.exe (4321k) https://gnupg.org/ftp/gcrypt/binary/gnupg-w32-2.2.25_20201123.exe.sig The source used to build the Windows installer can be found in the same directory with a ".tar.xz" suffix. New versions of the GnuPG VS-Desktop(tm) and Gpg4win featuring this version of GnuPG will be released shortly. Checking the Integrity ====================== In order to check that the version of GnuPG which you are going to install is an original and unmodified one, you can do it in one of the following ways: * If you already have a version of GnuPG installed, you can simply verify the supplied signature. For example to verify the signature of the file gnupg-2.2.25.tar.bz2 you would use this command: gpg --verify gnupg-2.2.25.tar.bz2.sig gnupg-2.2.25.tar.bz2 This checks whether the signature file matches the source file. You should see a message indicating that the signature is good and made by one or more of the release signing keys. Make sure that this is a valid key, either by matching the shown fingerprint against a trustworthy list of valid release signing keys or by checking that the key has been signed by trustworthy other keys. See the end of this mail for information on the signing keys. * If you are not able to use an existing version of GnuPG, you have to verify the SHA-1 checksum. On Unix systems the command to do this is either "sha1sum" or "shasum". Assuming you downloaded the file gnupg-2.2.25.tar.bz2, you run the command like this: sha1sum gnupg-2.2.25.tar.bz2 and check that the output matches the next line: 074b21dd07419575fa31c0c5d3116596d5544cbd gnupg-2.2.25.tar.bz2 9a36c4b487563aab82d1436d8bf4518718dcc267 gnupg-w32-2.2.25_20201123.tar.xz d4bc499a192e607f6db5e50bbc885a649ae670fc gnupg-w32-2.2.25_20201123.exe Internationalization ==================== This version of GnuPG has support for 26 languages with Chinese (traditional and simplified), Czech, French, German, Italian, Japanese, Norwegian, Polish, Russian, and Ukrainian being almost completely translated. Documentation and Support ========================= If you used GnuPG in the past you should read the description of changes and new features at doc/whats-new-in-2.1.txt or online at https://gnupg.org/faq/whats-new-in-2.1.html The file gnupg.info has the complete reference manual of the system. Separate man pages are included as well but they miss some of the details available only in thee manual. The manual is also available online at https://gnupg.org/documentation/manuals/gnupg/ or can be downloaded as PDF at https://gnupg.org/documentation/manuals/gnupg.pdf . You may also want to search the GnuPG mailing list archives or ask on the gnupg-users mailing list for advise on how to solve problems. Most of the new features are around for several years and thus enough public experience is available. https://wiki.gnupg.org has user contributed information around GnuPG and relate software. In case of build problems specific to this release please first check https://dev.gnupg.org/T5140 for updated information. Please consult the archive of the gnupg-users mailing list before reporting a bug: https://gnupg.org/documentation/mailing-lists.html. We suggest to send bug reports for a new release to this list in favor of filing a bug at https://bugs.gnupg.org. If you need commercial support go to https://gnupg.com or https://gnupg.org/service.html. If you are a developer and you need a certain feature for your project, please do not hesitate to bring it to the gnupg-devel mailing list for discussion. Thanks ====== Since 2001 maintenance and development of GnuPG is done by g10 Code GmbH and still mostly financed by donations. Two full-time employed developers as well as two contractors exclusively work on GnuPG and closely related software like Libgcrypt, GPGME and Gpg4win. We like to thank all the nice people who are helping the GnuPG project, be it testing, coding, translating, suggesting, auditing, administering the servers, spreading the word, or answering questions on the mailing lists. Many thanks to our numerous financial supporters, both corporate and individuals. Without you it would not be possible to keep GnuPG in a good and secure shape and to address all the small and larger requests made by our users. Thanks. Happy hacking, Your GnuPG hackers p.s. This is an announcement only mailing list. Please send replies only to the gnupg-users'at'gnupg.org mailing list. p.p.s List of Release Signing Keys: To guarantee that a downloaded GnuPG version has not been tampered by malicious entities we provide signature files for all tarballs and binary versions. The keys are also signed by the long term keys of their respective owners. Current releases are signed by one or more of these four keys: rsa2048 2011-01-12 [expires: 2021-12-31] Key fingerprint = D869 2123 C406 5DEA 5E0F 3AB5 249B 39D2 4F25 E3B6 Werner Koch (dist sig) rsa2048 2014-10-29 [expires: 2020-10-30] Key fingerprint = 031E C253 6E58 0D8E A286 A9F2 2071 B08A 33BD 3F06 NIIBE Yutaka (GnuPG Release Key) rsa3072 2017-03-17 [expires: 2027-03-15] Key fingerprint = 5B80 C575 4298 F0CB 55D8 ED6A BCEF 7E29 4B09 2E28 Andre Heinecke (Release Signing Key) ed25519 2020-08-24 [expires: 2030-06-30] Key fingerprint = 6DAA 6E64 A76D 2840 571B 4902 5288 97B8 2640 3ADA Werner Koch (dist signing 2020) The keys are available at https://gnupg.org/signature_key.html and in any recently released GnuPG tarball in the file g10/distsigkey.gpg . Note that this mail has been signed by a different key. -- "If privacy is outlawed, only outlaws will have privacy." - PRZ 1991 ... some still don't get it. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 227 bytes Desc: not available URL: -------------- next part -------------- _______________________________________________ Gnupg-announce mailing list Gnupg-announce at gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-announce From sanczes at gmail.com Thu Nov 26 15:10:08 2020 From: sanczes at gmail.com (=?UTF-8?B?SmnFmcOtIEsu?=) Date: Thu, 26 Nov 2020 15:10:08 +0100 Subject: [PATCH gpgme] Add license file for cJSON Message-ID: >From 25655d9473770a355d61c47e9770a0d1806714ea Mon Sep 17 00:00:00 2001 From: Jiri Kucera Add a COPYING.MIT file, containing the license of cJSON, to the root directory. Signed-off-by: Jiri Kucera --- COPYING.MIT | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) create mode 100644 COPYING.MIT diff --git a/COPYING.MIT b/COPYING.MIT new file mode 100644 index 00000000..151dc51f --- /dev/null +++ b/COPYING.MIT @@ -0,0 +1,19 @@ +Copyright (c) 2009 Dave Gamble + +Permission is hereby granted, free of charge, to any person obtaining a copy +of this software and associated documentation files (the "Software"), to deal +in the Software without restriction, including without limitation the rights +to use, copy, modify, merge, publish, distribute, sublicense, and/or sell +copies of the Software, and to permit persons to whom the Software is +furnished to do so, subject to the following conditions: + +The above copyright notice and this permission notice shall be included in +all copies or substantial portions of the Software. + +THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR +IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, +FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE +AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER +LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, +OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN +THE SOFTWARE. -- 2.17.2 -------------- next part -------------- An HTML attachment was scrubbed... URL: From meissner at b1-systems.de Sun Nov 22 14:42:34 2020 From: meissner at b1-systems.de (=?UTF-8?Q?Jens_Mei=c3=9fner?=) Date: Sun, 22 Nov 2020 14:42:34 +0100 Subject: [PATCH GnuPG] doc: Add parameters for batch generation of ECC keys. Message-ID: <71f73cd1-8cf1-891b-d116-edff2e9fbd5e@b1-systems.de> * doc/gpg.texi: Add parameters for batch generation of ECC keys. -- There are parameters required for batch generation of ECC keys which weren't mentioned in the documentation. Signed-off-by: Jens Mei?ner --- doc/gpg.texi | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/doc/gpg.texi b/doc/gpg.texi index f611813fb..805af3f22 100644 --- a/doc/gpg.texi +++ b/doc/gpg.texi @@ -4207,6 +4207,11 @@ for @samp{Subkey-Type}. @item Key-Length: @var{nbits} The requested length of the generated key in bits. The default is returned by running the command @samp{@gpgname --gpgconf-list}. +For ECC keys this parameter is ignored. + + at item Key-Curve: @var{curve} +The requested elliptic curve of the generated key. This is a required +parameter for ECC keys. It is ignored for non-ECC keys. @item Key-Grip: @var{hexstring} This is optional and used to generate a CSR or certificate for an @@ -4231,6 +4236,9 @@ can be handled. See also @samp{Key-Type} above. Length of the secondary key (subkey) in bits. The default is returned by running the command @samp{@gpgname --gpgconf-list}. + at item Subkey-Curve: @var{curve} +Key curve for a subkey; similar to @samp{Key-Curve}. + @item Subkey-Usage: @var{usage-list} Key usage lists for a subkey; similar to @samp{Key-Usage}. -- 2.20.1 -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-doc-Add-parameters-for-batch-generation-of-ECC-keys.patch Type: text/x-patch Size: 1670 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 263 bytes Desc: OpenPGP digital signature URL: From meissner at b1-systems.de Sun Nov 22 14:42:18 2020 From: meissner at b1-systems.de (=?UTF-8?Q?Jens_Mei=c3=9fner?=) Date: Sun, 22 Nov 2020 14:42:18 +0100 Subject: =?UTF-8?Q?DCO_for_Jens_Mei=c3=9fner?= Message-ID: <79e7702c-01f4-d543-2794-a28a63fc4e25@b1-systems.de> GnuPG Developer's Certificate of Origin. Version 1.0 ===================================================== By making a contribution to the GnuPG project, I certify that: (a) The contribution was created in whole or in part by me and I have the right to submit it under the free software license indicated in the file; or (b) The contribution is based upon previous work that, to the best of my knowledge, is covered under an appropriate free software license and I have the right under that license to submit that work with modifications, whether created in whole or in part by me, under the same free software license (unless I am permitted to submit under a different license), as indicated in the file; or (c) The contribution was provided directly to me by some other person who certified (a), (b) or (c) and I have not modified it. (d) I understand and agree that this project and the contribution are public and that a record of the contribution (including all personal information I submit with it, including my sign-off) is maintained indefinitely and may be redistributed consistent with this project or the free software license(s) involved. Signed-off-by: Jens Mei?ner -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 263 bytes Desc: OpenPGP digital signature URL: