Simon Josefsson <[email protected]> writes: > Daiki Ueno <[email protected]> writes: > >> On a slightly related note, we might also want to plan a new major >> release (3.9 or 4.0) with backward incompatible changes, such as default >> cipher selections. > > What kind of backward incompatible API/ABI change are you thinking of?
I meant more about backward incompatible "behavior" changes, such as: https://gitlab.com/gnutls/gnutls/-/issues/1761 https://gitlab.com/gnutls/gnutls/-/issues/1772 > I think doing backwards incompatible changes that affect running code > out there is often just a bad idea, so IMHO it would be nice to > enumerate the API/ABI changes for consideration, and then run reverse > builds of Debian/Fedora packages using GnuTLS to see what breaks. I agree. Even if we disable some already deprecated functionality, such as SRP, we will likely keep the API/ABI (but may turn it no-op). Regards, -- Daiki Ueno _______________________________________________ Gnutls-help mailing list [email protected] http://lists.gnupg.org/mailman/listinfo/gnutls-help
