We've recently enabled quic by default in Gentoo "testing" ebuilds. As we provide a mechanism for users to enable MultiSSL there are a number who choose to enable alternative TLS backends in order to meet thier requirements.
While I can provide package-manager flags to prevent this configuration from being enabled, it's also worth raising an issue to discuss.
I did this
./configure --prefix=/usr --build=i686-pc-linux-gnu --host=i686-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --datarootdir=/usr/share --disable-dependency-tracking --disable-silent-rules --disable-static --docdir=/usr/share/doc/curl-8.9.0 --htmldir=/usr/share/doc/curl-8.9.0/html --with-sysroot=/ --libdir=/usr/lib --without-ca-fallback --with-ca-bundle=/etc/ssl/certs/ca-certificates.crt --without-gnutls --without-mbedtls --without-rustls --with-gnutls --with-ssl --with-ca-path=/etc/ssl/certs --with-default-ssl-backend=openssl --enable-alt-svc --enable-basic-auth --enable-bearer-auth --enable-digest-auth --enable-kerberos-auth --enable-negotiate-auth --enable-aws --enable-dict --disable-ech --enable-file --enable-ftp --disable-gopher --enable-hsts --enable-http --enable-imap --disable-ldap --disable-ldaps --enable-ntlm --enable-pop3 --enable-rt --enable-rtsp --enable-smb --with-libssh2 --enable-smtp --disable-telnet --enable-tftp --enable-tls-srp --enable-ares --enable-cookies --enable-dateparse --enable-dnsshuffle --enable-doh --enable-symbol-hiding --enable-http-auth --enable-ipv6 --enable-largefile --enable-manual --enable-mime --enable-netrc --enable-progress-meter --enable-proxy --enable-socketpair --disable-sspi --disable-static --enable-pthreads --enable-threaded-resolver --disable-versioned-symbols --without-amissl --without-bearssl --without-brotli --with-fish-functions-dir=/usr/share/fish/vendor_completions.d --with-nghttp2 --without-hyper --with-libidn2 --with-gssapi=/usr --without-libgsasl --with-libpsl --without-msh3 --with-nghttp3 --without-ngtcp2 --with-openssl-quic --without-quiche --with-librtmp --without-schannel --without-secure-transport --without-test-caddy --without-test-httpd --without-test-nghttpx --enable-websockets --without-winidn --without-wolfssl --with-zlib --with-zstd --with-zsh-functions-dir=/usr/share/zsh/site-functions
. . .
configure: error: MultiSSL cannot be enabled with HTTP/3 and vice versa
I expected the following
Uncertain; worth discussing:
- Is this explicitly unsupported?
- Is there a reason to support MultiSSL + HTTP3/QUIC?
- What might that look like if so?
curl/libcurl version
curl 8.9.0
operating system
Gentoo Linux
We've recently enabled quic by default in Gentoo "testing" ebuilds. As we provide a mechanism for users to enable MultiSSL there are a number who choose to enable alternative TLS backends in order to meet thier requirements.
While I can provide package-manager flags to prevent this configuration from being enabled, it's also worth raising an issue to discuss.
I did this
I expected the following
Uncertain; worth discussing:
curl/libcurl version
curl 8.9.0
operating system
Gentoo Linux