From gnutls-devel at lists.gnutls.org Mon Mar 2 06:24:01 2026 From: gnutls-devel at lists.gnutls.org (Read-only notification of GnuTLS library development activities) Date: Mon, 02 Mar 2026 05:24:01 +0000 Subject: [gnutls-devel] GnuTLS | Draft: fix mingw (!2076) In-Reply-To: References: Message-ID: Daiki Ueno started a new discussion on tests/name-constraints-ip.c: https://gitlab.com/gnutls/gnutls/-/merge_requests/2076#note_3123287687 > _gnutls_x509_name_constraints_merge(gnutls_x509_name_constraints_t nc, > gnutls_x509_name_constraints_t nc2); > > -static void check_for_error(int ret) > -{ > - if (ret != GNUTLS_E_SUCCESS) > - fail_msg("error in %d: %s\n", __LINE__, gnutls_strerror(ret)); > -} > +#define check_for_error(ret) \ Why? I generally prefer a regular function rather than a macro; maybe we could make `static inline` though. -- Reply to this email directly or view it on GitLab: https://gitlab.com/gnutls/gnutls/-/merge_requests/2076#note_3123287687 You're receiving this email because of your account on gitlab.com. Unsubscribe from this thread: https://gitlab.com/-/sent_notifications/3-77hsezrsqnbni2at3qiv94gid/unsubscribe | Manage all notifications: https://gitlab.com/-/profile/notifications | Help: https://gitlab.com/help -------------- next part -------------- An HTML attachment was scrubbed... URL: From gnutls-devel at lists.gnutls.org Mon Mar 2 06:29:27 2026 From: gnutls-devel at lists.gnutls.org (Read-only notification of GnuTLS library development activities) Date: Mon, 02 Mar 2026 05:29:27 +0000 Subject: [gnutls-devel] GnuTLS | Draft: fix mingw (!2076) In-Reply-To: References: Message-ID: Daiki Ueno commented on a discussion on tests/name-constraints-ip.c: https://gitlab.com/gnutls/gnutls/-/merge_requests/2076#note_3123293024 > _gnutls_x509_name_constraints_merge(gnutls_x509_name_constraints_t nc, > gnutls_x509_name_constraints_t nc2); > > -static void check_for_error(int ret) > -{ > - if (ret != GNUTLS_E_SUCCESS) > - fail_msg("error in %d: %s\n", __LINE__, gnutls_strerror(ret)); > -} > +#define check_for_error(ret) \ Ah, I see it's for `__LINE__`. IMO it's worth a comment (or a commit message) about the reason behind the change. -- Reply to this email directly or view it on GitLab: https://gitlab.com/gnutls/gnutls/-/merge_requests/2076#note_3123293024 You're receiving this email because of your account on gitlab.com. Unsubscribe from this thread: https://gitlab.com/-/sent_notifications/3-3sii4vb2ue3rvq4vf8mk1lemk/unsubscribe | Manage all notifications: https://gitlab.com/-/profile/notifications | Help: https://gitlab.com/help -------------- next part -------------- An HTML attachment was scrubbed... URL: From gnutls-devel at lists.gnutls.org Mon Mar 2 12:59:00 2026 From: gnutls-devel at lists.gnutls.org (Read-only notification of GnuTLS library development activities) Date: Mon, 02 Mar 2026 11:59:00 +0000 Subject: [gnutls-devel] GnuTLS | Draft: fix mingw (!2076) In-Reply-To: References: Message-ID: Alexander Sosedkin commented: https://gitlab.com/gnutls/gnutls/-/merge_requests/2076#note_3124318661 The images I've created lacked wine-common and only had wine-core. Wine still ran stuff fine, but each process first waited 5 minutes for something in the prefix initialization to time out. FML. Will re-do the entire MR. -- Reply to this email directly or view it on GitLab: https://gitlab.com/gnutls/gnutls/-/merge_requests/2076#note_3124318661 You're receiving this email because of your account on gitlab.com. Unsubscribe from this thread: https://gitlab.com/-/sent_notifications/3-c7hhm299jmnqgw36agiqpeik8/unsubscribe | Manage all notifications: https://gitlab.com/-/profile/notifications | Help: https://gitlab.com/help -------------- next part -------------- An HTML attachment was scrubbed... URL: From gnutls-devel at lists.gnutls.org Mon Mar 2 13:10:04 2026 From: gnutls-devel at lists.gnutls.org (Read-only notification of GnuTLS library development activities) Date: Mon, 02 Mar 2026 12:10:04 +0000 Subject: [gnutls-devel] GnuTLS | Draft: fix mingw (!2076) In-Reply-To: References: Message-ID: Alexander Sosedkin commented: https://gitlab.com/gnutls/gnutls/-/merge_requests/2076#note_3124348962 Do we want to keep the separation of ctests into windows and non-windows? Should save a bit of building time, but at the cost of maintaining two lists. -- Reply to this email directly or view it on GitLab: https://gitlab.com/gnutls/gnutls/-/merge_requests/2076#note_3124348962 You're receiving this email because of your account on gitlab.com. Unsubscribe from this thread: https://gitlab.com/-/sent_notifications/3-9fj2vhysm01mu3vzcuotn87ev/unsubscribe | Manage all notifications: https://gitlab.com/-/profile/notifications | Help: https://gitlab.com/help -------------- next part -------------- An HTML attachment was scrubbed... URL: From gnutls-devel at lists.gnutls.org Mon Mar 2 13:56:55 2026 From: gnutls-devel at lists.gnutls.org (Read-only notification of GnuTLS library development activities) Date: Mon, 02 Mar 2026 12:56:55 +0000 Subject: [gnutls-devel] GnuTLS | devel/ci-local.sh: add a gitlab-ci-local wrapper (!2077) References: Message-ID: Alexander Sosedkin created a merge request: https://gitlab.com/gnutls/gnutls/-/merge_requests/2077 Branches: devel-ci-local to master Author: Alexander Sosedkin This is an opinionated script I've started to use to run CI jobs locally, and I wonder whether it could be of use to others. gitlab-ci-local doesn't play nicely with gnutls out of the box. This adds a wrapper that smoothes several wrinkles out: 1. if you're using worktrees, bootstrapping submodules fails 2. there's no way to pass arbitrary arguments like `--remote` to podman 3. `artifacts: untracked: true` doesn't work without `paths` specified 4. commit-check job is skipped by default ## 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/2077 You're receiving this email because of your account on gitlab.com. Unsubscribe from this thread: https://gitlab.com/-/sent_notifications/3-esji75jf3kmmzf9v74k2o5hn8/unsubscribe | Manage all notifications: https://gitlab.com/-/profile/notifications | Help: https://gitlab.com/help -------------- next part -------------- An HTML attachment was scrubbed... URL: From gnutls-devel at lists.gnutls.org Mon Mar 2 13:59:36 2026 From: gnutls-devel at lists.gnutls.org (Read-only notification of GnuTLS library development activities) Date: Mon, 02 Mar 2026 12:59:36 +0000 Subject: [gnutls-devel] GnuTLS | fix mingw (!2076) In-Reply-To: References: Message-ID: Alexander Sosedkin marked merge request !2076 as ready -- Reply to this email directly or view it on GitLab: https://gitlab.com/gnutls/gnutls/-/merge_requests/2076 You're receiving this email because of your account on gitlab.com. Unsubscribe from this thread: https://gitlab.com/-/sent_notifications/3-21k9ge2mu5ikbt9xh6gf540p5/unsubscribe | Manage all notifications: https://gitlab.com/-/profile/notifications | Help: https://gitlab.com/help -------------- next part -------------- An HTML attachment was scrubbed... URL: From gnutls-devel at lists.gnutls.org Mon Mar 2 14:12:39 2026 From: gnutls-devel at lists.gnutls.org (Read-only notification of GnuTLS library development activities) Date: Mon, 02 Mar 2026 13:12:39 +0000 Subject: [gnutls-devel] GnuTLS | fix mingw (!2076) In-Reply-To: References: Message-ID: Daiki Ueno commented on a discussion: https://gitlab.com/gnutls/gnutls/-/merge_requests/2076#note_3124535761 We probably should minimize the latter list by not using `fork` in the tests; given they are skipped anyway, I don't oppose to merge those lists. -- Reply to this email directly or view it on GitLab: https://gitlab.com/gnutls/gnutls/-/merge_requests/2076#note_3124535761 You're receiving this email because of your account on gitlab.com. Unsubscribe from this thread: https://gitlab.com/-/sent_notifications/3-3qsmw4h4ftnhz3iam3scob8jn/unsubscribe | Manage all notifications: https://gitlab.com/-/profile/notifications | Help: https://gitlab.com/help -------------- next part -------------- An HTML attachment was scrubbed... URL: From gnutls-devel at lists.gnutls.org Mon Mar 2 14:13:05 2026 From: gnutls-devel at lists.gnutls.org (Read-only notification of GnuTLS library development activities) Date: Mon, 02 Mar 2026 13:13:05 +0000 Subject: [gnutls-devel] GnuTLS | fix mingw (!2076) In-Reply-To: References: Message-ID: Daiki Ueno commented: https://gitlab.com/gnutls/gnutls/-/merge_requests/2076#note_3124537268 LGTM! -- Reply to this email directly or view it on GitLab: https://gitlab.com/gnutls/gnutls/-/merge_requests/2076#note_3124537268 You're receiving this email because of your account on gitlab.com. Unsubscribe from this thread: https://gitlab.com/-/sent_notifications/3-80dj0a5jridtbxl9obl8ed3ar/unsubscribe | Manage all notifications: https://gitlab.com/-/profile/notifications | Help: https://gitlab.com/help -------------- next part -------------- An HTML attachment was scrubbed... URL: From gnutls-devel at lists.gnutls.org Mon Mar 2 14:13:23 2026 From: gnutls-devel at lists.gnutls.org (Read-only notification of GnuTLS library development activities) Date: Mon, 02 Mar 2026 13:13:23 +0000 Subject: [gnutls-devel] GnuTLS | fix mingw (!2076) In-Reply-To: References: Message-ID: Merge request !2076 was approved by Daiki Ueno Merge request URL: https://gitlab.com/gnutls/gnutls/-/merge_requests/2076 Project:Branches: asosedkin/gnutls:fix-mingw to gnutls/gnutls:master Author: Alexander Sosedkin Assignees: Reviewers: -- 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 Mar 2 15:05:50 2026 From: gnutls-devel at lists.gnutls.org (Read-only notification of GnuTLS library development activities) Date: Mon, 02 Mar 2026 14:05:50 +0000 Subject: [gnutls-devel] GnuTLS | Draft: [RFC]Add new API to fetch privkey type (!2074) In-Reply-To: References: Message-ID: Daiki Ueno commented: https://gitlab.com/gnutls/gnutls/-/merge_requests/2074#note_3124718055 Hello Ghadi, thank you for the patch. The feature sounds reasonable, though I wonder if the original problem could be solved by extending `gnutls_pkcs11_privkey_get_pk_algorithm` to return a curve embedded in the `bits` parameter. As `gnutls_pkcs11_privkey_t` holds an object handle, it should be possible to retrieve any attributes on the private key object (currently the `bits` field of `gnutls_pkcs11_privkey_t` is set only when the key type is RSA, which could be modified to handle other key types as well). What do you think? If you end up with adding a new API, follow the guidance at https://gitlab.com/gnutls/gnutls/-/blob/master/CONTRIBUTING.md?ref_type=heads#introducing-new-functions--api. -- Reply to this email directly or view it on GitLab: https://gitlab.com/gnutls/gnutls/-/merge_requests/2074#note_3124718055 You're receiving this email because of your account on gitlab.com. Unsubscribe from this thread: https://gitlab.com/-/sent_notifications/3-cxweeoiu6a3gycq7vho7av3zv/unsubscribe | Manage all notifications: https://gitlab.com/-/profile/notifications | Help: https://gitlab.com/help -------------- next part -------------- An HTML attachment was scrubbed... URL: From gnutls-devel at lists.gnutls.org Mon Mar 2 15:22:55 2026 From: gnutls-devel at lists.gnutls.org (Read-only notification of GnuTLS library development activities) Date: Mon, 02 Mar 2026 14:22:55 +0000 Subject: [gnutls-devel] GnuTLS | Support building with Nettle 4 (!2075) In-Reply-To: References: Message-ID: Niels M?ller commented: https://gitlab.com/gnutls/gnutls/-/merge_requests/2075#note_3124780916 Late review (I was off on vacation last week). Looks reasonable to me, thanks! I hope the workaround for changed return value of base16_decode_update/base64_decode_update is not needed (fixed in nettle commit 4d1bd74a2ad316a485124c44c241124b4760dc69). -- Reply to this email directly or view it on GitLab: https://gitlab.com/gnutls/gnutls/-/merge_requests/2075#note_3124780916 You're receiving this email because of your account on gitlab.com. Unsubscribe from this thread: https://gitlab.com/-/sent_notifications/3-59pxtuvkp41oqd2jtxcduxk6z/unsubscribe | Manage all notifications: https://gitlab.com/-/profile/notifications | Help: https://gitlab.com/help -------------- next part -------------- An HTML attachment was scrubbed... URL: From gnutls-devel at lists.gnutls.org Mon Mar 2 15:24:32 2026 From: gnutls-devel at lists.gnutls.org (Read-only notification of GnuTLS library development activities) Date: Mon, 02 Mar 2026 14:24:32 +0000 Subject: [gnutls-devel] GnuTLS | Support building with Nettle 4 (!2075) In-Reply-To: References: Message-ID: Merge request https://gitlab.com/gnutls/gnutls/-/merge_requests/2075 was reviewed by Niels M?ller -- Niels M?ller started a new discussion on lib/x509_b64.c: https://gitlab.com/gnutls/gnutls/-/merge_requests/2075#note_3124780851 > + /* Nettle 4 returns -1 on error, while Nettle 3 returns 0; > + * catch both > + */ I think that's a bug that was luckily reported and fixed *prior* to the release. -- Reply to this email directly or view it on GitLab: https://gitlab.com/gnutls/gnutls/-/merge_requests/2075 You're receiving this email because of your account on gitlab.com. Unsubscribe from this thread: https://gitlab.com/-/sent_notifications/3-0e5zuc3cmrjigsvtxnhg9odqw/unsubscribe | Manage all notifications: https://gitlab.com/-/profile/notifications | Help: https://gitlab.com/help -------------- next part -------------- An HTML attachment was scrubbed... URL: From gnutls-devel at lists.gnutls.org Mon Mar 2 18:54:09 2026 From: gnutls-devel at lists.gnutls.org (Read-only notification of GnuTLS library development activities) Date: Mon, 02 Mar 2026 17:54:09 +0000 Subject: [gnutls-devel] GnuTLS | fix mingw (!2076) In-Reply-To: References: Message-ID: Alexander Sosedkin commented on a discussion: https://gitlab.com/gnutls/gnutls/-/merge_requests/2076#note_3125452958 when it failed, it failed pretty right away on some benign operation. hope I fixed that one with an explicit init that windows-capable tests should call -- Reply to this email directly or view it on GitLab: https://gitlab.com/gnutls/gnutls/-/merge_requests/2076#note_3125452958 You're receiving this email because of your account on gitlab.com. Unsubscribe from this thread: https://gitlab.com/-/sent_notifications/3-2gpcpdn85pp2q5r0d4e2pn05u/unsubscribe | Manage all notifications: https://gitlab.com/-/profile/notifications | Help: https://gitlab.com/help -------------- next part -------------- An HTML attachment was scrubbed... URL: From gnutls-devel at lists.gnutls.org Tue Mar 3 01:21:56 2026 From: gnutls-devel at lists.gnutls.org (Read-only notification of GnuTLS library development activities) Date: Tue, 03 Mar 2026 00:21:56 +0000 Subject: [gnutls-devel] GnuTLS | PKCS#11 Auto-Initialization Not Working (#1798) In-Reply-To: References: Message-ID: Claudio Ferreira commented: https://gitlab.com/gnutls/gnutls/-/issues/1798#note_3126116596 @dueno, any other thing that I can do? -- Reply to this email directly or view it on GitLab: https://gitlab.com/gnutls/gnutls/-/issues/1798#note_3126116596 You're receiving this email because of your account on gitlab.com. Unsubscribe from this thread: https://gitlab.com/-/sent_notifications/3-acyjrj9a28mzf13fztc8e7bti/unsubscribe | Manage all notifications: https://gitlab.com/-/profile/notifications | Help: https://gitlab.com/help -------------- next part -------------- An HTML attachment was scrubbed... URL: From gnutls-devel at lists.gnutls.org Tue Mar 3 09:06:21 2026 From: gnutls-devel at lists.gnutls.org (Read-only notification of GnuTLS library development activities) Date: Tue, 03 Mar 2026 08:06:21 +0000 Subject: [gnutls-devel] GnuTLS | Undefined reference to _gnutls_hmac_sha_aarch64 when building with nettle v4 patch (#1804) References: Message-ID: bbhtt created an issue: https://gitlab.com/gnutls/gnutls/-/issues/1804 The patch was applied on top of the 3.8.12 tag. The issue seems to affect aarch64 build only. ``` libtool: link: ar cr .libs/libcmd-ocsp.a .libs/ocsptool-options.o mv -f .deps/p11tool-p11tool.Tpo .deps/p11tool-p11tool.Po libtool: link: ranlib .libs/libcmd-ocsp.a libtool: link: ( cd ".libs" && rm -f "libcmd-ocsp.la" && ln -s "../libcmd-ocsp.la" "libcmd-ocsp.la" ) libtool: link: aarch64-unknown-linux-gnu-gcc -DTEST=1 -O2 -pipe -g -Wp,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -fexceptions -fstack-protector-strong -grecord-gcc-switches -fasynchronous-unwind-tables -fstack-clash-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -mbranch-protection=bti+pac-ret -Wl,-z -Wl,relro -Wl,-z -Wl,now -Wl,--as-needed -o dumpcfg dumpcfg-cfg.o ../gl/.libs/libgnu.a gl/.libs/libgnu_gpl.a libtool: link: ar cr .libs/libcmd-serv.a .libs/gnutls-serv-options.o libtool: link: ranlib .libs/libcmd-serv.a libtool: link: ( cd ".libs" && rm -f "libcmd-serv.la" && ln -s "../libcmd-serv.la" "libcmd-serv.la" ) libtool: link: ar cr .libs/libcmd-cli.a .libs/gnutls-cli-options.o libtool: link: ranlib .libs/libcmd-cli.a libtool: link: aarch64-unknown-linux-gnu-gcc -fanalyzer -fstrict-flex-arrays -Wall -Wbad-function-cast -Wcast-align=strict -Wdate-time -Wdisabled-optimization -Wdouble-promotion -Wduplicated-branches -Wduplicated-cond -Wextra -Wflex-array-member-not-at-end -Winit-self -Winvalid-pch -Wlogical-op -Wmissing-declarations -Wmissing-include-dirs -Wmissing-prototypes -Wnested-externs -Wnull-dereference -Wold-style-definition -Wopenmp-simd -Wpacked -Wpointer-arith -Wshadow -Wstrict-flex-arrays -Wstrict-prototypes -Wsuggest-attribute=cold -Wsuggest-attribute=format -Wsuggest-attribute=malloc -Wsuggest-final-methods -Wsuggest-final-types -Wsync-nand -Wtrampolines -Wuninitialized -Wunknown-pragmas -Wunused-macros -Wvariadic-macros -Wvector-operation-performance -Wwrite-strings -Warray-bounds=2 -Wattribute-alias=2 -Wbidi-chars=any,ucn -Wformat-overflow=2 -Wformat=2 -Wformat-truncation=2 -Wimplicit-fallthrough=5 -Wshift-overflow=2 -Wuse-after-free=3 -Wunused-const-variable=2 -Wvla-larger-than=4031 -Wno-analyzer-malloc-leak -Wno-missing-field-initializers -Wno-unused-parameter -Wno-format-truncation -Wimplicit-fallthrough=2 -Wabi=11 -fdiagnostics-show-option -fno-builtin-strcmp -O2 -pipe -g -Wp,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -fexceptions -fstack-protector-strong -grecord-gcc-switches -fasynchronous-unwind-tables -fstack-clash-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -mbranch-protection=bti+pac-ret -Wl,-z -Wl,relro -Wl,-z -Wl,now -Wl,--as-needed -o .libs/psktool psk.o ../lib/.libs/libgnutls.so -lp11-kit -lidn2 -lunistring -ldl -ltasn1 -lhogweed -lnettle -lgmp ./.libs/libcmd-psk.a ../gl/.libs/libgnu.a gl/.libs/libgnu_gpl.a libtool: link: ( cd ".libs" && rm -f "libcmd-cli.la" && ln -s "../libcmd-cli.la" "libcmd-cli.la" ) /usr/aarch64-unknown-linux-gnu/bin/ld.bfd: ../lib/.libs/libgnutls.so: undefined reference to `_gnutls_hmac_sha_aarch64' collect2: error: ld returned 1 exit status make[3]: *** [Makefile:3275: psktool] Error 1 make[3]: *** Waiting for unfinished jobs.... mv -f .deps/p11tool-common.Tpo .deps/p11tool-common.Po mv -f .deps/p11tool-pkcs11.Tpo .deps/p11tool-pkcs11.Po mv -f .deps/p11tool-certtool-common.Tpo .deps/p11tool-certtool-common.Po make[3]: Leaving directory '/buildstream-build/bst_build_dir/src' make[2]: *** [Makefile:3114: all] Error 2 make[2]: Leaving directory '/buildstream-build/bst_build_dir/src' make[1]: *** [Makefile:2934: all-recursive] Error 1 make[1]: Leaving directory '/buildstream-build/bst_build_dir' make: *** [Makefile:2859: all] Error 2 Command 'if [ -n "bst_build_dir" ]; then cd bst_build_dir fi make ' failed with exitcode 2 ``` -- Reply to this email directly or view it on GitLab: https://gitlab.com/gnutls/gnutls/-/issues/1804 You're receiving this email because of your account on gitlab.com. Unsubscribe from this thread: https://gitlab.com/-/sent_notifications/3-a7jh2z04rt88rkliyk93xulyt/unsubscribe | Manage all notifications: https://gitlab.com/-/profile/notifications | Help: https://gitlab.com/help -------------- next part -------------- An HTML attachment was scrubbed... URL: From gnutls-devel at lists.gnutls.org Tue Mar 3 09:29:31 2026 From: gnutls-devel at lists.gnutls.org (Read-only notification of GnuTLS library development activities) Date: Tue, 03 Mar 2026 08:29:31 +0000 Subject: [gnutls-devel] GnuTLS | gnulib: update to 2026-03-02 f1d55e9f84 (!2069) In-Reply-To: References: Message-ID: Alexander Sosedkin commented: https://gitlab.com/gnutls/gnutls/-/merge_requests/2069#note_3126730314 Sigh, I think I'm triggering a fresh bug in gnulib, sent an email to [bug-gnulib](https://lists.gnu.org/archive/html/bug-gnulib/2026-03/index.html) and rolling it back one day with: `gnulib: update to 2026-03-01 1cc0125a28` -- Reply to this email directly or view it on GitLab: https://gitlab.com/gnutls/gnutls/-/merge_requests/2069#note_3126730314 You're receiving this email because of your account on gitlab.com. Unsubscribe from this thread: https://gitlab.com/-/sent_notifications/3-84ektiybb6v9zb93bi9mzp4am/unsubscribe | Manage all notifications: https://gitlab.com/-/profile/notifications | Help: https://gitlab.com/help -------------- next part -------------- An HTML attachment was scrubbed... URL: From gnutls-devel at lists.gnutls.org Tue Mar 3 10:11:23 2026 From: gnutls-devel at lists.gnutls.org (Read-only notification of GnuTLS library development activities) Date: Tue, 03 Mar 2026 09:11:23 +0000 Subject: [gnutls-devel] GnuTLS | Remove no longer used files copied from Nettle (!2078) References: Message-ID: Daiki Ueno created a merge request: https://gitlab.com/gnutls/gnutls/-/merge_requests/2078 Project:Branches: dueno/gnutls:wip/dueno/remove-nettle-bundle to gnutls/gnutls:master Author: Daiki Ueno In 3.8.11, we bumped the minimum required version of Nettle from 3.6 to 3.10, which made most of the "vendored" files unused as they are part of Nettle 3.10. This removes those now that we haven't heard any complaints on the version bump in the past couple of release cycles. ## 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/2078 You're receiving this email because of your account on gitlab.com. Unsubscribe from this thread: https://gitlab.com/-/sent_notifications/3-946s1nu8pkp15mcinmgmogeu8/unsubscribe | Manage all notifications: https://gitlab.com/-/profile/notifications | Help: https://gitlab.com/help -------------- next part -------------- An HTML attachment was scrubbed... URL: From gnutls-devel at lists.gnutls.org Tue Mar 3 10:12:15 2026 From: gnutls-devel at lists.gnutls.org (Read-only notification of GnuTLS library development activities) Date: Tue, 03 Mar 2026 09:12:15 +0000 Subject: [gnutls-devel] GnuTLS | Support building with Nettle 4 (!2075) In-Reply-To: References: Message-ID: Daiki Ueno commented on a discussion on lib/x509_b64.c: https://gitlab.com/gnutls/gnutls/-/merge_requests/2075#note_3126861993 > > ret = base64_decode_update(&ctx, &size, result->data, pdata.size, > (void *)pdata.data); > - if (ret == 0 || size == 0) { > + /* Nettle 4 returns -1 on error, while Nettle 3 returns 0; > + * catch both > + */ Thank you for spotting this; I was apparently using a pre-released version for testing. I'm picking it up in https://gitlab.com/gnutls/gnutls/-/merge_requests/2078 -- Reply to this email directly or view it on GitLab: https://gitlab.com/gnutls/gnutls/-/merge_requests/2075#note_3126861993 You're receiving this email because of your account on gitlab.com. Unsubscribe from this thread: https://gitlab.com/-/sent_notifications/3-3j8gaaolifhet4hfl7h074fy4/unsubscribe | Manage all notifications: https://gitlab.com/-/profile/notifications | Help: https://gitlab.com/help -------------- next part -------------- An HTML attachment was scrubbed... URL: From gnutls-devel at lists.gnutls.org Tue Mar 3 10:31:14 2026 From: gnutls-devel at lists.gnutls.org (Read-only notification of GnuTLS library development activities) Date: Tue, 03 Mar 2026 09:31:14 +0000 Subject: [gnutls-devel] GnuTLS | Draft: [RFC]Add new API to fetch privkey type (!2074) In-Reply-To: References: Message-ID: Daiki Ueno commented on a discussion: https://gitlab.com/gnutls/gnutls/-/merge_requests/2074#note_3126922938 After looking at the code more closely, it feels to me that `gnutls_pkcs11_privkey_t` is not the right place to add this kind of API, as it's backed by PKCS#11 URI; so I like your initial approach more. Only one suggestion is that, currently the function looks like: ```c int gnutls_pkcs11_get_privkey_type(gnutls_pkcs11_obj_t obj, gnutls_pk_algorithm_t *pk, gnutls_ecc_curve_t *curve, unsigned int *bits); ``` which could be: ```c gnutls_pk_algorithm_t gnutls_pkcs11_obj_get_pk_algorithm(gnutls_pkcs11_obj_t obj, unsigned int *bits); ``` so that the API is in line with other _get_pk_algorithm functions. -- Reply to this email directly or view it on GitLab: https://gitlab.com/gnutls/gnutls/-/merge_requests/2074#note_3126922938 You're receiving this email because of your account on gitlab.com. Unsubscribe from this thread: https://gitlab.com/-/sent_notifications/3-0rk0p9vfwyg781kfj3ep5myw1/unsubscribe | Manage all notifications: https://gitlab.com/-/profile/notifications | Help: https://gitlab.com/help -------------- next part -------------- An HTML attachment was scrubbed... URL: From gnutls-devel at lists.gnutls.org Tue Mar 3 10:37:48 2026 From: gnutls-devel at lists.gnutls.org (Read-only notification of GnuTLS library development activities) Date: Tue, 03 Mar 2026 09:37:48 +0000 Subject: [gnutls-devel] GnuTLS | gnulib: update to 2026-03-01 1cc0125a28 (!2069) In-Reply-To: References: Message-ID: Alexander Sosedkin commented on a discussion: https://gitlab.com/gnutls/gnutls/-/merge_requests/2069#note_3126942943 And I finally have the answer: this change does *not* break mingw. Tested together with https://gitlab.com/gnutls/gnutls/-/merge_requests/2076: https://gitlab.com/asosedkin/gnutls/-/jobs/13330103075 https://gitlab.com/asosedkin/gnutls/-/jobs/13330103070 -- Reply to this email directly or view it on GitLab: https://gitlab.com/gnutls/gnutls/-/merge_requests/2069#note_3126942943 You're receiving this email because of your account on gitlab.com. Unsubscribe from this thread: https://gitlab.com/-/sent_notifications/3-8qbo34a4ke5bls34o6f49t7lf/unsubscribe | Manage all notifications: https://gitlab.com/-/profile/notifications | Help: https://gitlab.com/help -------------- next part -------------- An HTML attachment was scrubbed... URL: From gnutls-devel at lists.gnutls.org Tue Mar 3 10:37:49 2026 From: gnutls-devel at lists.gnutls.org (Read-only notification of GnuTLS library development activities) Date: Tue, 03 Mar 2026 09:37:49 +0000 Subject: [gnutls-devel] GnuTLS | gnulib: update to 2026-03-01 1cc0125a28 (!2069) In-Reply-To: References: Message-ID: All discussions on merge request !2069 were resolved by Alexander Sosedkin https://gitlab.com/gnutls/gnutls/-/merge_requests/2069 -- Reply to this email directly or view it on GitLab: https://gitlab.com/gnutls/gnutls/-/merge_requests/2069 You're receiving this email because of your account on gitlab.com. Unsubscribe from this thread: https://gitlab.com/-/sent_notifications/3-38vii2r4l8rgdw68j5aghpufl/unsubscribe | Manage all notifications: https://gitlab.com/-/profile/notifications | Help: https://gitlab.com/help -------------- next part -------------- An HTML attachment was scrubbed... URL: From gnutls-devel at lists.gnutls.org Tue Mar 3 11:16:16 2026 From: gnutls-devel at lists.gnutls.org (Read-only notification of GnuTLS library development activities) Date: Tue, 03 Mar 2026 10:16:16 +0000 Subject: [gnutls-devel] GnuTLS | Draft: [RFC]Add new API to fetch privkey type (!2074) In-Reply-To: References: Message-ID: Ghadi Rahme commented on a discussion: https://gitlab.com/gnutls/gnutls/-/merge_requests/2074#note_3127066875 Thank you for reviewing this Daiki! That is correct the privkey struct cannot be used since it is populated based on the URI instead of an iterator. I will update the function definition, embed the curve in the bits field as well and check the guidance documentation. -- Reply to this email directly or view it on GitLab: https://gitlab.com/gnutls/gnutls/-/merge_requests/2074#note_3127066875 You're receiving this email because of your account on gitlab.com. Unsubscribe from this thread: https://gitlab.com/-/sent_notifications/3-8mxtm3qelffmzhcsmq9s2gl70/unsubscribe | Manage all notifications: https://gitlab.com/-/profile/notifications | Help: https://gitlab.com/help -------------- next part -------------- An HTML attachment was scrubbed... URL: From gnutls-devel at lists.gnutls.org Tue Mar 3 17:04:31 2026 From: gnutls-devel at lists.gnutls.org (Read-only notification of GnuTLS library development activities) Date: Tue, 03 Mar 2026 16:04:31 +0000 Subject: [gnutls-devel] GnuTLS | fix mingw (!2076) In-Reply-To: References: Message-ID: Alexander Sosedkin commented on a discussion: https://gitlab.com/gnutls/gnutls/-/merge_requests/2076#note_3128247476 Without hard opinions on either keeping on removing it, the strongest argument for either side was having an established place for marking tests as skip-on-Windows --- the test source code --- so keeping it as is won. -- Reply to this email directly or view it on GitLab: https://gitlab.com/gnutls/gnutls/-/merge_requests/2076#note_3128247476 You're receiving this email because of your account on gitlab.com. Unsubscribe from this thread: https://gitlab.com/-/sent_notifications/3-75s68zmk6zom3pn1j9v120hzc/unsubscribe | Manage all notifications: https://gitlab.com/-/profile/notifications | Help: https://gitlab.com/help -------------- next part -------------- An HTML attachment was scrubbed... URL: From gnutls-devel at lists.gnutls.org Tue Mar 3 17:04:36 2026 From: gnutls-devel at lists.gnutls.org (Read-only notification of GnuTLS library development activities) Date: Tue, 03 Mar 2026 16:04:36 +0000 Subject: [gnutls-devel] GnuTLS | fix mingw (!2076) In-Reply-To: References: Message-ID: Alexander Sosedkin commented: https://gitlab.com/gnutls/gnutls/-/merge_requests/2076#note_3128247878 Rebased + trimmed the three commits separating ctests into Windows and non-Windows. -- Reply to this email directly or view it on GitLab: https://gitlab.com/gnutls/gnutls/-/merge_requests/2076#note_3128247878 You're receiving this email because of your account on gitlab.com. Unsubscribe from this thread: https://gitlab.com/-/sent_notifications/3-elfnrtrcwiolus2j5dezjb7nn/unsubscribe | Manage all notifications: https://gitlab.com/-/profile/notifications | Help: https://gitlab.com/help -------------- next part -------------- An HTML attachment was scrubbed... URL: From gnutls-devel at lists.gnutls.org Tue Mar 3 17:04:46 2026 From: gnutls-devel at lists.gnutls.org (Read-only notification of GnuTLS library development activities) Date: Tue, 03 Mar 2026 16:04:46 +0000 Subject: [gnutls-devel] GnuTLS | fix mingw (!2076) In-Reply-To: References: Message-ID: All discussions on merge request !2076 were resolved by Alexander Sosedkin https://gitlab.com/gnutls/gnutls/-/merge_requests/2076 -- Reply to this email directly or view it on GitLab: https://gitlab.com/gnutls/gnutls/-/merge_requests/2076 You're receiving this email because of your account on gitlab.com. Unsubscribe from this thread: https://gitlab.com/-/sent_notifications/3-d9trq0rkkcub9gbyh7b4llq7k/unsubscribe | Manage all notifications: https://gitlab.com/-/profile/notifications | Help: https://gitlab.com/help -------------- next part -------------- An HTML attachment was scrubbed... URL: From gnutls-devel at lists.gnutls.org Tue Mar 3 19:55:16 2026 From: gnutls-devel at lists.gnutls.org (Read-only notification of GnuTLS library development activities) Date: Tue, 03 Mar 2026 18:55:16 +0000 Subject: [gnutls-devel] GnuTLS | fix mingw (!2076) In-Reply-To: References: Message-ID: Merge request !2076 was merged Merge request URL: https://gitlab.com/gnutls/gnutls/-/merge_requests/2076 Project:Branches: asosedkin/gnutls:fix-mingw to gnutls/gnutls:master Author: Alexander Sosedkin -- Reply to this email directly or view it on GitLab: https://gitlab.com/gnutls/gnutls/-/merge_requests/2076 You're receiving this email because of your account on gitlab.com. Unsubscribe from this thread: https://gitlab.com/-/sent_notifications/3-aouw8707slpy8pjj60nxw82zd/unsubscribe | Manage all notifications: https://gitlab.com/-/profile/notifications | Help: https://gitlab.com/help -------------- next part -------------- An HTML attachment was scrubbed... URL: From gnutls-devel at lists.gnutls.org Tue Mar 3 19:57:26 2026 From: gnutls-devel at lists.gnutls.org (Read-only notification of GnuTLS library development activities) Date: Tue, 03 Mar 2026 18:57:26 +0000 Subject: [gnutls-devel] GnuTLS | gnulib: update to 2026-03-01 1cc0125a28 (!2069) In-Reply-To: References: Message-ID: Alexander Sosedkin commented: https://gitlab.com/gnutls/gnutls/-/merge_requests/2069#note_3128821178 rebasing past mingw fixes just to be sure... -- Reply to this email directly or view it on GitLab: https://gitlab.com/gnutls/gnutls/-/merge_requests/2069#note_3128821178 You're receiving this email because of your account on gitlab.com. Unsubscribe from this thread: https://gitlab.com/-/sent_notifications/3-7raofrhqp36t6kthkwtfdsy1j/unsubscribe | Manage all notifications: https://gitlab.com/-/profile/notifications | Help: https://gitlab.com/help -------------- next part -------------- An HTML attachment was scrubbed... URL: From gnutls-devel at lists.gnutls.org Tue Mar 3 20:12:59 2026 From: gnutls-devel at lists.gnutls.org (Read-only notification of GnuTLS library development activities) Date: Tue, 03 Mar 2026 19:12:59 +0000 Subject: [gnutls-devel] =?utf-8?q?GnuTLS_=7C_ktls=3A_fix_ChaCha20-Poly130?= =?utf-8?q?5_IV_passing_for_TLS=C2=A01=2E2_=28!2079=29?= In-Reply-To: References: Message-ID: Franti?ek Kren?elok was added as a reviewer. -- Reply to this email directly or view it on GitLab: https://gitlab.com/gnutls/gnutls/-/merge_requests/2079 You're receiving this email because of your account on gitlab.com. Unsubscribe from this thread: https://gitlab.com/-/sent_notifications/3-1kxcuadzw87cajtehr9s81sn5/unsubscribe | Manage all notifications: https://gitlab.com/-/profile/notifications | Help: https://gitlab.com/help -------------- next part -------------- An HTML attachment was scrubbed... URL: From gnutls-devel at lists.gnutls.org Tue Mar 3 20:13:02 2026 From: gnutls-devel at lists.gnutls.org (Read-only notification of GnuTLS library development activities) Date: Tue, 03 Mar 2026 19:13:02 +0000 Subject: [gnutls-devel] =?utf-8?q?GnuTLS_=7C_ktls=3A_fix_ChaCha20-Poly130?= =?utf-8?q?5_IV_passing_for_TLS=C2=A01=2E2_=28!2079=29?= References: Message-ID: Alexander Sosedkin created a merge request: https://gitlab.com/gnutls/gnutls/-/merge_requests/2079 Project:Branches: asosedkin/gnutls:ktls-chacha-iv-fix to gnutls/gnutls:master Author: Alexander Sosedkin Reviewer: Franti?ek Kren?elok For TLS 1.2 + Chacha20 + KTLS, IV was effectively sequence number + a bit of stack garbage. The test forks client and server, so the likelihood of said garbage matching was high, masking the issue. * ktls: fix ChaCha20-Poly1305 IV passing for TLS?1.2 - the fix * ktls: simplify ChaCha20?Poly1305 IV passing for TLS 1.2 - should be a no-op ## 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/2079 You're receiving this email because of your account on gitlab.com. Unsubscribe from this thread: https://gitlab.com/-/sent_notifications/3-4fgryfs0s287eou2lax6xp7u0/unsubscribe | Manage all notifications: https://gitlab.com/-/profile/notifications | Help: https://gitlab.com/help -------------- next part -------------- An HTML attachment was scrubbed... URL: From gnutls-devel at lists.gnutls.org Tue Mar 3 20:30:30 2026 From: gnutls-devel at lists.gnutls.org (Read-only notification of GnuTLS library development activities) Date: Tue, 03 Mar 2026 19:30:30 +0000 Subject: [gnutls-devel] =?utf-8?q?GnuTLS_=7C_ktls=3A_fix_ChaCha20-Poly130?= =?utf-8?q?5_IV_passing_for_TLS=C2=A01=2E2_=28!2079=29?= In-Reply-To: References: Message-ID: Franti?ek Kren?elok commented: https://gitlab.com/gnutls/gnutls/-/merge_requests/2079#note_3128898306 LGTM, how the hack did i come up with that, I have no clue.... Thanks Alex for catching this! -- Reply to this email directly or view it on GitLab: https://gitlab.com/gnutls/gnutls/-/merge_requests/2079#note_3128898306 You're receiving this email because of your account on gitlab.com. Unsubscribe from this thread: https://gitlab.com/-/sent_notifications/3-5ihkubn97kd6r8c8c7m5ofuth/unsubscribe | Manage all notifications: https://gitlab.com/-/profile/notifications | Help: https://gitlab.com/help -------------- next part -------------- An HTML attachment was scrubbed... URL: From gnutls-devel at lists.gnutls.org Tue Mar 3 20:30:51 2026 From: gnutls-devel at lists.gnutls.org (Read-only notification of GnuTLS library development activities) Date: Tue, 03 Mar 2026 19:30:51 +0000 Subject: [gnutls-devel] =?utf-8?q?GnuTLS_=7C_ktls=3A_fix_ChaCha20-Poly130?= =?utf-8?q?5_IV_passing_for_TLS=C2=A01=2E2_=28!2079=29?= In-Reply-To: References: Message-ID: Merge request !2079 was approved by Franti?ek Kren?elok Merge request URL: https://gitlab.com/gnutls/gnutls/-/merge_requests/2079 Project:Branches: asosedkin/gnutls:ktls-chacha-iv-fix to gnutls/gnutls:master Author: Alexander Sosedkin Assignees: Reviewer: Franti?ek Kren?elok -- 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 Wed Mar 4 02:11:08 2026 From: gnutls-devel at lists.gnutls.org (Read-only notification of GnuTLS library development activities) Date: Wed, 04 Mar 2026 01:11:08 +0000 Subject: [gnutls-devel] GnuTLS | accelerated: don't register custom HMAC for AArch64 if Nettle 4 (!2080) References: Message-ID: Daiki Ueno created a merge request: https://gitlab.com/gnutls/gnutls/-/merge_requests/2080 Project:Branches: dueno/gnutls:wip/dueno/nettle-4-followup to gnutls/gnutls:master Author: Daiki Ueno * nettle: revert workaround for base64_decode_update return values This reverts commit d6014115969655005968491be1da8892ddedc134, as it turned out that the change of error return value was only available in an unreleased version of Nettle. * accelerated: don't register custom HMAC for AArch64 if Nettle 4 As a follow-up of commit 4e3921c36529110a94c2a63e0d6601c502901589, add missing #ifdefs for AArch64, as Nettle 4 doesn't provide an easy way to implement a custom HMAC instance. Fixes: #1804 ## 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/2080 You're receiving this email because of your account on gitlab.com. Unsubscribe from this thread: https://gitlab.com/-/sent_notifications/3-68h1pajxefqadi90kzukj2xpr/unsubscribe | Manage all notifications: https://gitlab.com/-/profile/notifications | Help: https://gitlab.com/help -------------- next part -------------- An HTML attachment was scrubbed... URL: From gnutls-devel at lists.gnutls.org Wed Mar 4 02:11:47 2026 From: gnutls-devel at lists.gnutls.org (Read-only notification of GnuTLS library development activities) Date: Wed, 04 Mar 2026 01:11:47 +0000 Subject: [gnutls-devel] GnuTLS | Undefined reference to _gnutls_hmac_sha_aarch64 when building with nettle v4 patch (#1804) In-Reply-To: References: Message-ID: Daiki Ueno commented: https://gitlab.com/gnutls/gnutls/-/issues/1804#note_3129543466 Thanks for the report, !2080 should fix the issue. -- Reply to this email directly or view it on GitLab: https://gitlab.com/gnutls/gnutls/-/issues/1804#note_3129543466 You're receiving this email because of your account on gitlab.com. Unsubscribe from this thread: https://gitlab.com/-/sent_notifications/3-bi35dnejhx1oevaif8e31d5mn/unsubscribe | Manage all notifications: https://gitlab.com/-/profile/notifications | Help: https://gitlab.com/help -------------- next part -------------- An HTML attachment was scrubbed... URL: From gnutls-devel at lists.gnutls.org Wed Mar 4 02:11:58 2026 From: gnutls-devel at lists.gnutls.org (Read-only notification of GnuTLS library development activities) Date: Wed, 04 Mar 2026 01:11:58 +0000 Subject: [gnutls-devel] GnuTLS | Undefined reference to _gnutls_hmac_sha_aarch64 when building with nettle v4 patch (#1804) In-Reply-To: References: Message-ID: Milestone changed to Release of GnuTLS 3.8.13 ( https://gitlab.com/gnutls/gnutls/-/milestones/51 ) -- Reply to this email directly or view it on GitLab: https://gitlab.com/gnutls/gnutls/-/issues/1804 You're receiving this email because of your account on gitlab.com. Unsubscribe from this thread: https://gitlab.com/-/sent_notifications/3-9o7yu6tnt1odpvz2ftfqjowzn/unsubscribe | Manage all notifications: https://gitlab.com/-/profile/notifications | Help: https://gitlab.com/help -------------- next part -------------- An HTML attachment was scrubbed... URL: From gnutls-devel at lists.gnutls.org Wed Mar 4 06:24:34 2026 From: gnutls-devel at lists.gnutls.org (Read-only notification of GnuTLS library development activities) Date: Wed, 04 Mar 2026 05:24:34 +0000 Subject: [gnutls-devel] GnuTLS | accelerated: don't register custom HMAC for AArch64 if Nettle 4 (!2080) In-Reply-To: References: Message-ID: Alexander Sosedkin was added as a reviewer. -- Reply to this email directly or view it on GitLab: https://gitlab.com/gnutls/gnutls/-/merge_requests/2080 You're receiving this email because of your account on gitlab.com. Unsubscribe from this thread: https://gitlab.com/-/sent_notifications/3-cctcwv70epjf94hspbjtm03df/unsubscribe | Manage all notifications: https://gitlab.com/-/profile/notifications | Help: https://gitlab.com/help -------------- next part -------------- An HTML attachment was scrubbed... URL: From gnutls-devel at lists.gnutls.org Wed Mar 4 10:13:30 2026 From: gnutls-devel at lists.gnutls.org (Read-only notification of GnuTLS library development activities) Date: Wed, 04 Mar 2026 09:13:30 +0000 Subject: [gnutls-devel] libtasn1 | add RELATIVE-OID support (!124) References: Message-ID: gjeanneau6wind created a merge request: https://gitlab.com/gnutls/libtasn1/-/merge_requests/124 Project:Branches: 6WIND/libtasn1:add_relative_oid_support to gnutls/libtasn1:master Author: gjeanneau6wind RELATIVE-OID is a standard type defined in ASN.1, as specified in ITU-T X.680. ## Checklist * [ ] Code modified for feature * [ ] Test suite updated with functionality tests * [ ] Test suite updated with negative tests * [ ] Documentation updated ## Reviewer's checklist: * [ ] There is a test suite reasonably covering new functionality or modifications * [ ] Function naming, parameters, return values, types, etc., are consistent with other code * [ ] 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/libtasn1/-/merge_requests/124 You're receiving this email because of your account on gitlab.com. Unsubscribe from this thread: https://gitlab.com/-/sent_notifications/3-4sb144igr8s3wuu1q40gp3n7r/unsubscribe | Manage all notifications: https://gitlab.com/-/profile/notifications | Help: https://gitlab.com/help -------------- next part -------------- An HTML attachment was scrubbed... URL: From gnutls-devel at lists.gnutls.org Wed Mar 4 11:24:07 2026 From: gnutls-devel at lists.gnutls.org (Read-only notification of GnuTLS library development activities) Date: Wed, 04 Mar 2026 10:24:07 +0000 Subject: [gnutls-devel] GnuTLS | accelerated: don't register custom HMAC for AArch64 if Nettle 4 (!2080) In-Reply-To: References: Message-ID: Merge request !2080 was approved by Alexander Sosedkin Merge request URL: https://gitlab.com/gnutls/gnutls/-/merge_requests/2080 Project:Branches: dueno/gnutls:wip/dueno/nettle-4-followup to gnutls/gnutls:master Author: Daiki Ueno Assignees: Reviewer: Alexander Sosedkin -- 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 Wed Mar 4 11:35:27 2026 From: gnutls-devel at lists.gnutls.org (Read-only notification of GnuTLS library development activities) Date: Wed, 04 Mar 2026 10:35:27 +0000 Subject: [gnutls-devel] GnuTLS | gnulib: update to 2026-03-01 1cc0125a28 (!2069) In-Reply-To: References: Message-ID: Merge request !2069 was merged Merge request URL: https://gitlab.com/gnutls/gnutls/-/merge_requests/2069 Project:Branches: asosedkin/gnutls:update-gnulib to gnutls/gnutls:master Author: Alexander Sosedkin Reviewer: Zolt?n Fridrich -- Reply to this email directly or view it on GitLab: https://gitlab.com/gnutls/gnutls/-/merge_requests/2069 You're receiving this email because of your account on gitlab.com. Unsubscribe from this thread: https://gitlab.com/-/sent_notifications/3-4awew68bfenzg9txnrwmluaxe/unsubscribe | Manage all notifications: https://gitlab.com/-/profile/notifications | Help: https://gitlab.com/help -------------- next part -------------- An HTML attachment was scrubbed... URL: From gnutls-devel at lists.gnutls.org Wed Mar 4 12:42:38 2026 From: gnutls-devel at lists.gnutls.org (Read-only notification of GnuTLS library development activities) Date: Wed, 04 Mar 2026 11:42:38 +0000 Subject: [gnutls-devel] GnuTLS | Undefined reference to _gnutls_hmac_sha_aarch64 when building with nettle v4 patch (#1804) In-Reply-To: References: Message-ID: Issue was closed by Alexander Sosedkin with merge request !2080 (https://gitlab.com/gnutls/gnutls/-/merge_requests/2080) Issue #1804: https://gitlab.com/gnutls/gnutls/-/issues/1804 -- Reply to this email directly or view it on GitLab: https://gitlab.com/gnutls/gnutls/-/issues/1804 You're receiving this email because of your account on gitlab.com. Unsubscribe from this thread: https://gitlab.com/-/sent_notifications/3-auos8dmf8aeqz74vyrzrns4lx/unsubscribe | Manage all notifications: https://gitlab.com/-/profile/notifications | Help: https://gitlab.com/help -------------- next part -------------- An HTML attachment was scrubbed... URL: From gnutls-devel at lists.gnutls.org Wed Mar 4 12:42:37 2026 From: gnutls-devel at lists.gnutls.org (Read-only notification of GnuTLS library development activities) Date: Wed, 04 Mar 2026 11:42:37 +0000 Subject: [gnutls-devel] GnuTLS | accelerated: don't register custom HMAC for AArch64 if Nettle 4 (!2080) In-Reply-To: References: Message-ID: Merge request !2080 was merged Merge request URL: https://gitlab.com/gnutls/gnutls/-/merge_requests/2080 Project:Branches: dueno/gnutls:wip/dueno/nettle-4-followup to gnutls/gnutls:master Author: Daiki Ueno Reviewer: Alexander Sosedkin -- Reply to this email directly or view it on GitLab: https://gitlab.com/gnutls/gnutls/-/merge_requests/2080 You're receiving this email because of your account on gitlab.com. Unsubscribe from this thread: https://gitlab.com/-/sent_notifications/3-1auvbhk7b7f9yyhe608i5lv4f/unsubscribe | Manage all notifications: https://gitlab.com/-/profile/notifications | Help: https://gitlab.com/help -------------- next part -------------- An HTML attachment was scrubbed... URL: From gnutls-devel at lists.gnutls.org Wed Mar 4 12:50:44 2026 From: gnutls-devel at lists.gnutls.org (Read-only notification of GnuTLS library development activities) Date: Wed, 04 Mar 2026 11:50:44 +0000 Subject: [gnutls-devel] GnuTLS | Remove no longer used files copied from Nettle (!2078) In-Reply-To: References: Message-ID: Alexander Sosedkin was added as a reviewer. -- Reply to this email directly or view it on GitLab: https://gitlab.com/gnutls/gnutls/-/merge_requests/2078 You're receiving this email because of your account on gitlab.com. Unsubscribe from this thread: https://gitlab.com/-/sent_notifications/3-cm501f1sdoeju3w9fe05cyv5q/unsubscribe | Manage all notifications: https://gitlab.com/-/profile/notifications | Help: https://gitlab.com/help -------------- next part -------------- An HTML attachment was scrubbed... URL: From gnutls-devel at lists.gnutls.org Wed Mar 4 13:13:38 2026 From: gnutls-devel at lists.gnutls.org (Read-only notification of GnuTLS library development activities) Date: Wed, 04 Mar 2026 12:13:38 +0000 Subject: [gnutls-devel] libtasn1 | Fix discard const qualifier (!123) In-Reply-To: References: Message-ID: Rudi Heitbaum commented: https://gitlab.com/gnutls/libtasn1/-/merge_requests/123#note_3130904118 @dueno @jas - any changes required or can this be merged? -- Reply to this email directly or view it on GitLab: https://gitlab.com/gnutls/libtasn1/-/merge_requests/123#note_3130904118 You're receiving this email because of your account on gitlab.com. Unsubscribe from this thread: https://gitlab.com/-/sent_notifications/3-avq4wfste1q91h1uyessaubrm/unsubscribe | Manage all notifications: https://gitlab.com/-/profile/notifications | Help: https://gitlab.com/help -------------- next part -------------- An HTML attachment was scrubbed... URL: From gnutls-devel at lists.gnutls.org Wed Mar 4 13:57:01 2026 From: gnutls-devel at lists.gnutls.org (Read-only notification of GnuTLS library development activities) Date: Wed, 04 Mar 2026 12:57:01 +0000 Subject: [gnutls-devel] GnuTLS | Remove no longer used files copied from Nettle (!2078) In-Reply-To: References: Message-ID: Merge request !2078 was approved by Alexander Sosedkin Merge request URL: https://gitlab.com/gnutls/gnutls/-/merge_requests/2078 Project:Branches: dueno/gnutls:wip/dueno/remove-nettle-bundle to gnutls/gnutls:master Author: Daiki Ueno Assignees: Reviewer: Alexander Sosedkin -- 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 Wed Mar 4 13:57:11 2026 From: gnutls-devel at lists.gnutls.org (Read-only notification of GnuTLS library development activities) Date: Wed, 04 Mar 2026 12:57:11 +0000 Subject: [gnutls-devel] GnuTLS | Remove no longer used files copied from Nettle (!2078) In-Reply-To: References: Message-ID: Alexander Sosedkin commented: https://gitlab.com/gnutls/gnutls/-/merge_requests/2078#note_3131034917 Don't see anything wrong with it. -- Reply to this email directly or view it on GitLab: https://gitlab.com/gnutls/gnutls/-/merge_requests/2078#note_3131034917 You're receiving this email because of your account on gitlab.com. Unsubscribe from this thread: https://gitlab.com/-/sent_notifications/3-864ml0ox7occwdjp3y5ji3ak7/unsubscribe | Manage all notifications: https://gitlab.com/-/profile/notifications | Help: https://gitlab.com/help -------------- next part -------------- An HTML attachment was scrubbed... URL: From gnutls-devel at lists.gnutls.org Wed Mar 4 14:03:53 2026 From: gnutls-devel at lists.gnutls.org (Read-only notification of GnuTLS library development activities) Date: Wed, 04 Mar 2026 13:03:53 +0000 Subject: [gnutls-devel] GnuTLS | Remove no longer used files copied from Nettle (!2078) In-Reply-To: References: Message-ID: Merge request !2078 was merged Merge request URL: https://gitlab.com/gnutls/gnutls/-/merge_requests/2078 Project:Branches: dueno/gnutls:wip/dueno/remove-nettle-bundle to gnutls/gnutls:master Author: Daiki Ueno Reviewer: Alexander Sosedkin -- Reply to this email directly or view it on GitLab: https://gitlab.com/gnutls/gnutls/-/merge_requests/2078 You're receiving this email because of your account on gitlab.com. Unsubscribe from this thread: https://gitlab.com/-/sent_notifications/3-3p2yo1269ppwtwjolg9ejfqva/unsubscribe | Manage all notifications: https://gitlab.com/-/profile/notifications | Help: https://gitlab.com/help -------------- next part -------------- An HTML attachment was scrubbed... URL: From gnutls-devel at lists.gnutls.org Wed Mar 4 14:06:12 2026 From: gnutls-devel at lists.gnutls.org (Read-only notification of GnuTLS library development activities) Date: Wed, 04 Mar 2026 13:06:12 +0000 Subject: [gnutls-devel] =?utf-8?q?GnuTLS_=7C_ktls=3A_fix_ChaCha20-Poly130?= =?utf-8?q?5_IV_passing_for_TLS=C2=A01=2E2_=28!2079=29?= In-Reply-To: References: Message-ID: Alexander Sosedkin commented on a discussion: https://gitlab.com/gnutls/gnutls/-/merge_requests/2079#note_3131061599 probably just a copy-paste error. happens to the best of us! -- Reply to this email directly or view it on GitLab: https://gitlab.com/gnutls/gnutls/-/merge_requests/2079#note_3131061599 You're receiving this email because of your account on gitlab.com. Unsubscribe from this thread: https://gitlab.com/-/sent_notifications/3-7mxi6wozq6knwzzg823wgca4n/unsubscribe | Manage all notifications: https://gitlab.com/-/profile/notifications | Help: https://gitlab.com/help -------------- next part -------------- An HTML attachment was scrubbed... URL: From gnutls-devel at lists.gnutls.org Wed Mar 4 14:06:44 2026 From: gnutls-devel at lists.gnutls.org (Read-only notification of GnuTLS library development activities) Date: Wed, 04 Mar 2026 13:06:44 +0000 Subject: [gnutls-devel] =?utf-8?q?GnuTLS_=7C_ktls=3A_fix_ChaCha20-Poly130?= =?utf-8?q?5_IV_passing_for_TLS=C2=A01=2E2_=28!2079=29?= In-Reply-To: References: Message-ID: All discussions on merge request !2079 were resolved by Alexander Sosedkin https://gitlab.com/gnutls/gnutls/-/merge_requests/2079 -- Reply to this email directly or view it on GitLab: https://gitlab.com/gnutls/gnutls/-/merge_requests/2079 You're receiving this email because of your account on gitlab.com. Unsubscribe from this thread: https://gitlab.com/-/sent_notifications/3-bpm2xenfassy64qpic92oqlqp/unsubscribe | Manage all notifications: https://gitlab.com/-/profile/notifications | Help: https://gitlab.com/help -------------- next part -------------- An HTML attachment was scrubbed... URL: From gnutls-devel at lists.gnutls.org Wed Mar 4 17:31:55 2026 From: gnutls-devel at lists.gnutls.org (Read-only notification of GnuTLS library development activities) Date: Wed, 04 Mar 2026 16:31:55 +0000 Subject: [gnutls-devel] =?utf-8?q?GnuTLS_=7C_ktls=3A_fix_ChaCha20-Poly130?= =?utf-8?q?5_IV_passing_for_TLS=C2=A01=2E2_=28!2079=29?= In-Reply-To: References: Message-ID: Merge request !2079 was merged Merge request URL: https://gitlab.com/gnutls/gnutls/-/merge_requests/2079 Project:Branches: asosedkin/gnutls:ktls-chacha-iv-fix to gnutls/gnutls:master Author: Alexander Sosedkin Reviewer: Franti?ek Kren?elok -- Reply to this email directly or view it on GitLab: https://gitlab.com/gnutls/gnutls/-/merge_requests/2079 You're receiving this email because of your account on gitlab.com. Unsubscribe from this thread: https://gitlab.com/-/sent_notifications/3-4t6hnviedc9nmvnhmm98n4tqg/unsubscribe | Manage all notifications: https://gitlab.com/-/profile/notifications | Help: https://gitlab.com/help -------------- next part -------------- An HTML attachment was scrubbed... URL: From gnutls-devel at lists.gnutls.org Wed Mar 4 22:33:16 2026 From: gnutls-devel at lists.gnutls.org (Read-only notification of GnuTLS library development activities) Date: Wed, 04 Mar 2026 21:33:16 +0000 Subject: [gnutls-devel] GnuTLS | Fails to build properly with autoconf 2.72.90 (2.73 pre-release) (#1806) References: Message-ID: Ross Burton created an issue: https://gitlab.com/gnutls/gnutls/-/issues/1806 If I build gnutls with autoconf 2.72.90 (the 2.73 pre-release) then the compiler is mis-detected: ``` WARNING: Compiler does not support C99. It may not be able to compile the project. ``` This is GCC 15.2, it most certainly does support C99. However, the configure code in `gnutls/configure.ac.` responsible for this check is quite broken: ``` AS_CASE([$ac_prog_cc_stdc], [c11 | c99], [AC_DEFINE([C99_MACROS], 1, [C99 macros are supported])], [AC_MSG_WARN([[Compiler does not support C99. It may not be able to compile the project.]])] ) ``` This is because `ac_prog_cc_stdc` is now `c23`, due to this change in autoconf: ``` *** AC_PROG_CC now prefers C23 if available. ``` This is trivially fixed by adding `c23` to the list of available standards, but the test is very fragile. Does gnutls even need to cater for non-C99 compilers? That's a pretty niche market these days, surely. -- Reply to this email directly or view it on GitLab: https://gitlab.com/gnutls/gnutls/-/issues/1806 You're receiving this email because of your account on gitlab.com. Unsubscribe from this thread: https://gitlab.com/-/sent_notifications/3-9xm1yqidhcg1kvwkmmrcq7il2/unsubscribe | Manage all notifications: https://gitlab.com/-/profile/notifications | Help: https://gitlab.com/help -------------- next part -------------- An HTML attachment was scrubbed... URL: From gnutls-devel at lists.gnutls.org Thu Mar 5 03:01:45 2026 From: gnutls-devel at lists.gnutls.org (Read-only notification of GnuTLS library development activities) Date: Thu, 05 Mar 2026 02:01:45 +0000 Subject: [gnutls-devel] GnuTLS | devel/ci-local.sh: add a gitlab-ci-local wrapper (!2077) In-Reply-To: References: Message-ID: Daiki Ueno commented: https://gitlab.com/gnutls/gnutls/-/merge_requests/2077#note_3133092596 Haven't tried, but it sounds useful. -- Reply to this email directly or view it on GitLab: https://gitlab.com/gnutls/gnutls/-/merge_requests/2077#note_3133092596 You're receiving this email because of your account on gitlab.com. Unsubscribe from this thread: https://gitlab.com/-/sent_notifications/3-1cft32xx2d4lccorveuzr3z34/unsubscribe | Manage all notifications: https://gitlab.com/-/profile/notifications | Help: https://gitlab.com/help -------------- next part -------------- An HTML attachment was scrubbed... URL: From gnutls-devel at lists.gnutls.org Thu Mar 5 03:01:49 2026 From: gnutls-devel at lists.gnutls.org (Read-only notification of GnuTLS library development activities) Date: Thu, 05 Mar 2026 02:01:49 +0000 Subject: [gnutls-devel] GnuTLS | devel/ci-local.sh: add a gitlab-ci-local wrapper (!2077) In-Reply-To: References: Message-ID: Merge request !2077 was approved by Daiki Ueno Merge request URL: https://gitlab.com/gnutls/gnutls/-/merge_requests/2077 Branches: devel-ci-local to master Author: Alexander Sosedkin Assignees: Reviewers: -- 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 Thu Mar 5 03:14:36 2026 From: gnutls-devel at lists.gnutls.org (Read-only notification of GnuTLS library development activities) Date: Thu, 05 Mar 2026 02:14:36 +0000 Subject: [gnutls-devel] GnuTLS | Fails to build properly with autoconf 2.72.90 (2.73 pre-release) (#1806) In-Reply-To: References: Message-ID: Daiki Ueno commented: https://gitlab.com/gnutls/gnutls/-/issues/1806#note_3133111880 Thanks for the report. I agree that we should support only C99 or later (maybe it's a good topic for the [planning](https://gitlab.com/gnutls/gnutls/-/wikis/Planning-for-4.0)). For this particular case, this is only a warning, so I guess we are fine either to add c23 to the match expression or to switch to using the [c99](https://www.gnu.org/software/gnulib/MODULES.html#module=c99) module. -- Reply to this email directly or view it on GitLab: https://gitlab.com/gnutls/gnutls/-/issues/1806#note_3133111880 You're receiving this email because of your account on gitlab.com. Unsubscribe from this thread: https://gitlab.com/-/sent_notifications/3-7u51x8agwayllr7ehremvyrl0/unsubscribe | Manage all notifications: https://gitlab.com/-/profile/notifications | Help: https://gitlab.com/help -------------- next part -------------- An HTML attachment was scrubbed... URL: From gnutls-devel at lists.gnutls.org Thu Mar 5 12:38:16 2026 From: gnutls-devel at lists.gnutls.org (Read-only notification of GnuTLS library development activities) Date: Thu, 05 Mar 2026 11:38:16 +0000 Subject: [gnutls-devel] GnuTLS | configure: make the C99 detection more resiliant (!2081) References: Message-ID: Ross Burton created a merge request: https://gitlab.com/gnutls/gnutls/-/merge_requests/2081 Project:Branches: rossburton/gnutls:c99 to gnutls/gnutls:master Author: Ross Burton * configure: make the C99 detection more resiliant autoconf 2.73 will default to C23 by default, which means that the >C99 detection logic in configure.ac will fail because it only handles c11 and c99. Instead of adding c23 to the list and then breaking again in the future, flip the logic around (as suggested by Zack Weinberg) and check explicitly for just c89. Closes #1806. Signed-off-by: Ross Burton ## 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/2081 You're receiving this email because of your account on gitlab.com. Unsubscribe from this thread: https://gitlab.com/-/sent_notifications/3-3wv3s6vc23o45x319e7zxeuvy/unsubscribe | Manage all notifications: https://gitlab.com/-/profile/notifications | Help: https://gitlab.com/help -------------- next part -------------- An HTML attachment was scrubbed... URL: From gnutls-devel at lists.gnutls.org Thu Mar 5 12:39:01 2026 From: gnutls-devel at lists.gnutls.org (Read-only notification of GnuTLS library development activities) Date: Thu, 05 Mar 2026 11:39:01 +0000 Subject: [gnutls-devel] GnuTLS | Fails to build properly with autoconf 2.72.90 (2.73 pre-release) (#1806) In-Reply-To: References: Message-ID: Ross Burton commented: https://gitlab.com/gnutls/gnutls/-/issues/1806#note_3134362932 Note that this isn't just an annoying failure: the gnutls.so grows by half a meg when built without C99, and the tests fail to link. -- Reply to this email directly or view it on GitLab: https://gitlab.com/gnutls/gnutls/-/issues/1806#note_3134362932 You're receiving this email because of your account on gitlab.com. Unsubscribe from this thread: https://gitlab.com/-/sent_notifications/3-arv5bbpb61s4fcg4jm5aewz7o/unsubscribe | Manage all notifications: https://gitlab.com/-/profile/notifications | Help: https://gitlab.com/help -------------- next part -------------- An HTML attachment was scrubbed... URL: From gnutls-devel at lists.gnutls.org Thu Mar 5 20:18:04 2026 From: gnutls-devel at lists.gnutls.org (Read-only notification of GnuTLS library development activities) Date: Thu, 05 Mar 2026 19:18:04 +0000 Subject: [gnutls-devel] GnuTLS | Draft: key_share: allow key share reuse with hybrids (!2067) In-Reply-To: References: Message-ID: Alexander Sosedkin commented on a discussion on lib/ext/key_share.c: https://gitlab.com/gnutls/gnutls/-/merge_requests/2067#note_3135862814 > > case GNUTLS_PK_ECDH_X25519: > case GNUTLS_PK_ECDH_X448: > - gnutls_pk_params_release(&session->key.kshare.ecdhx_params); > - gnutls_pk_params_init(&session->key.kshare.ecdhx_params); > + /* try reusing existing values */ > + if (session->key.kshare.ecdhx_params.curve == group->curve && > + session->key.kshare.ecdhx_params.algo == group->pk && > + session->key.kshare.ecdhx_params.raw_pub.data != NULL) { okay, so... here's an entire menu of versions to pick from: * ... * bdda1c936e key_share: reuse existing key shares (guards edition) - that's the continuation of what I was doing * f7af8dbbea key_share: reuse key shares (4-loop edition) - this is the version with a lot of passes, mind the limitations like slot reuse guards * 6636e9b641 key_share: reuse key shares (3-loop edition) - what I see as a natural simplification * b4c1bfc502 key_share: reuse key shares (2-loop edition) - what I see as a natural simplification * ec5163e807 key_share: reuse key shares (1-loop edition) - what I see as a natural simplification * 48cced8375 key_share: guards enable slot reuse - and now we've come full circle You've probably meant neither of these, but at least now you have an assortment of starting points at your disposal to continue explaining how multiple passes are better =) what's the closest to what you wanted and what is it lacking? -- Reply to this email directly or view it on GitLab: https://gitlab.com/gnutls/gnutls/-/merge_requests/2067#note_3135862814 You're receiving this email because of your account on gitlab.com. Unsubscribe from this thread: https://gitlab.com/-/sent_notifications/3-a6rrps16ei4sw3kcvcmrfmz9d/unsubscribe | Manage all notifications: https://gitlab.com/-/profile/notifications | Help: https://gitlab.com/help -------------- next part -------------- An HTML attachment was scrubbed... URL: From gnutls-devel at lists.gnutls.org Fri Mar 6 01:51:54 2026 From: gnutls-devel at lists.gnutls.org (Read-only notification of GnuTLS library development activities) Date: Fri, 06 Mar 2026 00:51:54 +0000 Subject: [gnutls-devel] GnuTLS | configure: make the C99 detection more resiliant (!2081) In-Reply-To: References: Message-ID: Merge request !2081 was approved by Daiki Ueno Merge request URL: https://gitlab.com/gnutls/gnutls/-/merge_requests/2081 Project:Branches: rossburton/gnutls:c99 to gnutls/gnutls:master Author: Ross Burton Assignees: Reviewers: -- 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 Fri Mar 6 01:52:00 2026 From: gnutls-devel at lists.gnutls.org (Read-only notification of GnuTLS library development activities) Date: Fri, 06 Mar 2026 00:52:00 +0000 Subject: [gnutls-devel] GnuTLS | configure: make the C99 detection more resiliant (!2081) In-Reply-To: References: Message-ID: Merge request !2081 was merged Merge request URL: https://gitlab.com/gnutls/gnutls/-/merge_requests/2081 Project:Branches: rossburton/gnutls:c99 to gnutls/gnutls:master Author: Ross Burton -- Reply to this email directly or view it on GitLab: https://gitlab.com/gnutls/gnutls/-/merge_requests/2081 You're receiving this email because of your account on gitlab.com. Unsubscribe from this thread: https://gitlab.com/-/sent_notifications/3-ds32aspp96n17iw90wno8r1xc/unsubscribe | Manage all notifications: https://gitlab.com/-/profile/notifications | Help: https://gitlab.com/help -------------- next part -------------- An HTML attachment was scrubbed... URL: From gnutls-devel at lists.gnutls.org Fri Mar 6 01:52:01 2026 From: gnutls-devel at lists.gnutls.org (Read-only notification of GnuTLS library development activities) Date: Fri, 06 Mar 2026 00:52:01 +0000 Subject: [gnutls-devel] GnuTLS | Fails to build properly with autoconf 2.72.90 (2.73 pre-release) (#1806) In-Reply-To: References: Message-ID: Issue was closed by Daiki Ueno with merge request !2081 (https://gitlab.com/gnutls/gnutls/-/merge_requests/2081) Issue #1806: https://gitlab.com/gnutls/gnutls/-/issues/1806 -- Reply to this email directly or view it on GitLab: https://gitlab.com/gnutls/gnutls/-/issues/1806 You're receiving this email because of your account on gitlab.com. Unsubscribe from this thread: https://gitlab.com/-/sent_notifications/3-1fggxwgr4a06cw81tr5t9l95u/unsubscribe | Manage all notifications: https://gitlab.com/-/profile/notifications | Help: https://gitlab.com/help -------------- next part -------------- An HTML attachment was scrubbed... URL: From gnutls-devel at lists.gnutls.org Fri Mar 6 01:52:02 2026 From: gnutls-devel at lists.gnutls.org (Read-only notification of GnuTLS library development activities) Date: Fri, 06 Mar 2026 00:52:02 +0000 Subject: [gnutls-devel] GnuTLS | Fails to build properly with autoconf 2.72.90 (2.73 pre-release) (#1806) In-Reply-To: References: Message-ID: Issue was closed by Daiki Ueno with commit 203d8f2187bb7f483290e0f8b7b48b152b1d027f Issue #1806: https://gitlab.com/gnutls/gnutls/-/issues/1806 -- Reply to this email directly or view it on GitLab: https://gitlab.com/gnutls/gnutls/-/issues/1806 You're receiving this email because of your account on gitlab.com. Unsubscribe from this thread: https://gitlab.com/-/sent_notifications/3-2dashnvhdryfl9vzbpdm0s7un/unsubscribe | Manage all notifications: https://gitlab.com/-/profile/notifications | Help: https://gitlab.com/help -------------- next part -------------- An HTML attachment was scrubbed... URL: From gnutls-devel at lists.gnutls.org Fri Mar 6 01:52:08 2026 From: gnutls-devel at lists.gnutls.org (Read-only notification of GnuTLS library development activities) Date: Fri, 06 Mar 2026 00:52:08 +0000 Subject: [gnutls-devel] GnuTLS | configure: make the C99 detection more resiliant (!2081) In-Reply-To: References: Message-ID: Daiki Ueno commented: https://gitlab.com/gnutls/gnutls/-/merge_requests/2081#note_3136543477 Thank you! -- Reply to this email directly or view it on GitLab: https://gitlab.com/gnutls/gnutls/-/merge_requests/2081#note_3136543477 You're receiving this email because of your account on gitlab.com. Unsubscribe from this thread: https://gitlab.com/-/sent_notifications/3-379xhs0c44k4vfyaboda4abea/unsubscribe | Manage all notifications: https://gitlab.com/-/profile/notifications | Help: https://gitlab.com/help -------------- next part -------------- An HTML attachment was scrubbed... URL: From gnutls-devel at lists.gnutls.org Fri Mar 6 01:52:25 2026 From: gnutls-devel at lists.gnutls.org (Read-only notification of GnuTLS library development activities) Date: Fri, 06 Mar 2026 00:52:25 +0000 Subject: [gnutls-devel] GnuTLS | Fails to build properly with autoconf 2.72.90 (2.73 pre-release) (#1806) In-Reply-To: References: Message-ID: Milestone changed to Release of GnuTLS 3.8.13 ( https://gitlab.com/gnutls/gnutls/-/milestones/51 ) -- Reply to this email directly or view it on GitLab: https://gitlab.com/gnutls/gnutls/-/issues/1806 You're receiving this email because of your account on gitlab.com. Unsubscribe from this thread: https://gitlab.com/-/sent_notifications/3-b14mit6zbyfhaaj9rdw7ap6ch/unsubscribe | Manage all notifications: https://gitlab.com/-/profile/notifications | Help: https://gitlab.com/help -------------- next part -------------- An HTML attachment was scrubbed... URL: From gnutls-devel at lists.gnutls.org Fri Mar 6 15:06:39 2026 From: gnutls-devel at lists.gnutls.org (Read-only notification of GnuTLS library development activities) Date: Fri, 06 Mar 2026 14:06:39 +0000 Subject: [gnutls-devel] GnuTLS | devel/ci-local.sh: add a gitlab-ci-local wrapper (!2077) In-Reply-To: References: Message-ID: Alexander Sosedkin commented: https://gitlab.com/gnutls/gnutls/-/merge_requests/2077#note_3138267210 (29c1d61c is a rebase of 5d10db50 with no changes otherwise) -- Reply to this email directly or view it on GitLab: https://gitlab.com/gnutls/gnutls/-/merge_requests/2077#note_3138267210 You're receiving this email because of your account on gitlab.com. Unsubscribe from this thread: https://gitlab.com/-/sent_notifications/3-davvg7m6xzkfw86gd13ezswjy/unsubscribe | Manage all notifications: https://gitlab.com/-/profile/notifications | Help: https://gitlab.com/help -------------- next part -------------- An HTML attachment was scrubbed... URL: From gnutls-devel at lists.gnutls.org Fri Mar 6 15:57:59 2026 From: gnutls-devel at lists.gnutls.org (Read-only notification of GnuTLS library development activities) Date: Fri, 06 Mar 2026 14:57:59 +0000 Subject: [gnutls-devel] GnuTLS | devel/release-steps.md: extend (!2065) In-Reply-To: References: Message-ID: Alexander Sosedkin commented on a discussion on devel/release-steps.md: https://gitlab.com/gnutls/gnutls/-/merge_requests/2065#note_3138452358 > Create a detached GPG signature. > Upload zip and signature files to ftp.gnupg.org. > Do the same analogically for `mingw64/archive`. > +1. Reveal and close the security issues addressed in the release. > +1. Close the security fixes merge requests addressed in the release. > 1. Create and send announcement email based on previously sent email mentioned by addresses and linked to the archives -- Reply to this email directly or view it on GitLab: https://gitlab.com/gnutls/gnutls/-/merge_requests/2065#note_3138452358 You're receiving this email because of your account on gitlab.com. Unsubscribe from this thread: https://gitlab.com/-/sent_notifications/3-b558661apms7plis4ptp4fify/unsubscribe | Manage all notifications: https://gitlab.com/-/profile/notifications | Help: https://gitlab.com/help -------------- next part -------------- An HTML attachment was scrubbed... URL: From gnutls-devel at lists.gnutls.org Fri Mar 6 19:22:31 2026 From: gnutls-devel at lists.gnutls.org (Read-only notification of GnuTLS library development activities) Date: Fri, 06 Mar 2026 18:22:31 +0000 Subject: [gnutls-devel] GnuTLS | Add new API to fetch privkey type (!2074) In-Reply-To: References: Message-ID: Ghadi Rahme marked merge request !2074 as ready -- Reply to this email directly or view it on GitLab: https://gitlab.com/gnutls/gnutls/-/merge_requests/2074 You're receiving this email because of your account on gitlab.com. Unsubscribe from this thread: https://gitlab.com/-/sent_notifications/3-c7yo2co4joa08zfuy9tw4xapx/unsubscribe | Manage all notifications: https://gitlab.com/-/profile/notifications | Help: https://gitlab.com/help -------------- next part -------------- An HTML attachment was scrubbed... URL: