[gnutls-devel] GnuTLS | Soft-disabling configuration capabilities should match the hard-disabling ones (#1172)

[Read-only notification of GnuTLS library development activities]

David Woodhouse commented:


We are finding this particularly problematic in OpenConnect because when we attempt to use our carefully crafted prio strings to select a particular version of DTLS, the system policy makes it fail.

It's OK to disable things by default, but to force them off even when the application knows what it's doing and explicitly tries to use them is going to be counter-productive.

https://gitlab.com/openconnect/openconnect/-/issues/243

-- 
Reply to this email directly or view it on GitLab: https://gitlab.com/gnutls/gnutls/-/issues/1172#note_575984608
You're receiving this email because of your account on gitlab.com.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.gnupg.org/pipermail/gnutls-devel/attachments/20210514/eff2d07f/attachment-0001.html>