From gnutls-devel at lists.gnutls.org Mon Feb 2 12:55:00 2026 From: gnutls-devel at lists.gnutls.org (Read-only notification of GnuTLS library development activities) Date: Mon, 02 Feb 2026 11:55:00 +0000 Subject: [gnutls-devel] GnuTLS | bootstrap fails when using gettext (autopoint) v. 1.0 (#1792) In-Reply-To: References: Message-ID: Daiki Ueno commented: https://gitlab.com/gnutls/gnutls/-/issues/1792#note_3051405009 I admit I have been away from the gettext development for a long time, but that reminds me of https://lists.gnu.org/archive/html/bug-gettext/2013-07/msg00002.html and I suspect it might be fixed if autopoint used `func_trace_autoconf` instead of `func_trace_sed` for that. @bhaible What do you think? Given gettext 0.19 is already over a decade old, I guess we could simply drop the `m4_ifdef` anyway. -- Reply to this email directly or view it on GitLab: https://gitlab.com/gnutls/gnutls/-/issues/1792#note_3051405009 You're receiving this email because of your account on gitlab.com. -------------- next part -------------- An HTML attachment was scrubbed... URL: From gnutls-devel at lists.gnutls.org Mon Feb 2 13:57:12 2026 From: gnutls-devel at lists.gnutls.org (Read-only notification of GnuTLS library development activities) Date: Mon, 02 Feb 2026 12:57:12 +0000 Subject: [gnutls-devel] GnuTLS | bootstrap fails when using gettext (autopoint) v. 1.0 (#1792) In-Reply-To: References: Message-ID: Bruno Haible commented: https://gitlab.com/gnutls/gnutls/-/issues/1792#note_3051633223 I would suggest to - either change that `0.19` to `0.19.6` and eliminate the m4_ifdef test, - or hide the m4_ifdef test from `autopoint`, similar to what is done in https://sources.debian.org/src/wget2/2.2.0+ds-3/debian/patches/configure-ac.patch -- Reply to this email directly or view it on GitLab: https://gitlab.com/gnutls/gnutls/-/issues/1792#note_3051633223 You're receiving this email because of your account on gitlab.com. -------------- next part -------------- An HTML attachment was scrubbed... URL: From gnutls-devel at lists.gnutls.org Tue Feb 3 05:34:03 2026 From: gnutls-devel at lists.gnutls.org (Read-only notification of GnuTLS library development activities) Date: Tue, 03 Feb 2026 04:34:03 +0000 Subject: [gnutls-devel] GnuTLS | configure.ac: hide m4_ifdef from autopoint (!2061) References: Message-ID: Daiki Ueno created a merge request: https://gitlab.com/gnutls/gnutls/-/merge_requests/2061 Project:Branches: dueno/gnutls:wip/dueno/gettext-1.0 to gnutls/gnutls:master Author: Daiki Ueno * configure.ac: hide m4_ifdef from autopoint The recent version of autopoint warns about multiple invocation of AM_GNU_GETTEXT_REQUIRE_VERSION, without evaluating m4_ifdef. This obfuscates the first occurrence with a quote to work around that. Suggested by Bruno Haible. Fixes: #1792 ## Checklist * [x] Commits have `Signed-off-by:` with name/author being identical to the commit author * [ ] Code modified for feature * [ ] Test suite updated with functionality tests * [ ] Test suite updated with negative tests * [ ] Documentation updated / NEWS entry present (for non-trivial changes) ## Reviewer's checklist: * [ ] Any issues marked for closing are addressed * [ ] There is a test suite reasonably covering new functionality or modifications * [ ] Function naming, parameters, return values, types, etc., are consistent and according to `CONTRIBUTION.md` * [ ] This feature/change has adequate documentation added * [ ] No obvious mistakes in the code -- Reply to this email directly or view it on GitLab: https://gitlab.com/gnutls/gnutls/-/merge_requests/2061 You're receiving this email because of your account on gitlab.com. -------------- next part -------------- An HTML attachment was scrubbed... URL: From gnutls-devel at lists.gnutls.org Tue Feb 3 17:10:07 2026 From: gnutls-devel at lists.gnutls.org (Read-only notification of GnuTLS library development activities) Date: Tue, 03 Feb 2026 16:10:07 +0000 Subject: [gnutls-devel] GnuTLS | GOST crypto according to RFC9558 support (#1793) References: Message-ID: Igor created an issue: https://gitlab.com/gnutls/gnutls/-/issues/1793 Hello, dear colleagues! Are there any plans for support GOST2012 with elliptic curve id-tc26-gost-3410-2012-256-paramSet as discribed in RFC9558? There is the comment in lib/x509/key_encode.c: ```c /* For compatibility per R 1323565.1.023?2018 provide digest OID only * for GOST-2001 keys or GOST-2012 keys with CryptoPro curves. Do not * set this optional parameter for TC26 curves */ ``` But the document has been greatly updated and for now elliptic curves from TC26 are used, for example, in openssl. Or maybe this is a question of nettle software patching? Thank you in advence for your answer! -- Reply to this email directly or view it on GitLab: https://gitlab.com/gnutls/gnutls/-/issues/1793 You're receiving this email because of your account on gitlab.com. -------------- next part -------------- An HTML attachment was scrubbed... URL: From gnutls-devel at lists.gnutls.org Tue Feb 3 18:29:17 2026 From: gnutls-devel at lists.gnutls.org (Read-only notification of GnuTLS library development activities) Date: Tue, 03 Feb 2026 17:29:17 +0000 Subject: [gnutls-devel] GnuTLS | GOST crypto according to RFC9558 support (#1793) In-Reply-To: References: Message-ID: Simon Josefsson commented: https://gitlab.com/gnutls/gnutls/-/issues/1793#note_3055511267 If we don't have support for it, I don't think it is useful to add now. X25519 is a good ECC curve, and working on adding old pre-PQ crypto now seems odd. -- Reply to this email directly or view it on GitLab: https://gitlab.com/gnutls/gnutls/-/issues/1793#note_3055511267 You're receiving this email because of your account on gitlab.com. -------------- next part -------------- An HTML attachment was scrubbed... URL: