Package: curl
Version: 8.12.1-1
Severity: important

Dear Maintainer,

curl, as currently packaged in debian unstable, has switched to building
against gnutls instead of openssl, which is a change from debian stable
(bookworm).

My understanding, based on the NEWS entry, is that the only reason for this
switch is to enable HTTP/3 support in curl.

OpenSSL, as currently packaged in debian unstable, does have HTTP/3 support as
well, which makes the stated rationale for using gnutls over openssl no longer
valid.

I would therefore like to ask you to consider switching back to building
against openssl instead of gnutls, just like it is currently done in debian
stable (bookworm).

The main reason for this is that switching to gnutls introduces compatibility
issues with current uses of curl in debian stable, sometimes subtle (different
ordering of TLS parameters leading to different behavior on the server, in some
cases leading to breakage) sometimes not so subtle (getting an error when using
the --ciphers option for curl, "Warning: ignoring --ciphers, not supported by
libcurl with GnuTLS/3.8").

In the interest of preserving compatibility with the uses of curl on debian
stable (bookworm) and next debian stable (trixie), curl should again be built
against openssl instead of gnutls, or alternatively another good reason should
be provided for building against gnutls (because the http/3 point is now moot).

Thanks.


-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.12.13-amd64 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages curl depends on:
ii  libc6               2.40-6
ii  libcurl3t64-gnutls  8.12.1-1
ii  zlib1g              1:1.3.dfsg+really1.3.1-1+b1

curl recommends no packages.

curl suggests no packages.

-- no debconf information

Reply via email to