The GnuTLS library typically maintains binary and source code compatibility across versions. The releases that have the major version increased break binary compatibility but source compatibility is provided. This section lists exceptional cases where changes to existing code are required due to library changes.
GnuTLS 2.12.x is binary compatible with previous versions but changes the
gnutls_transport_set_lowat, which might cause breakage
in applications that relied on its default value be 1. Two fixes
gnutls_transport_set_lowat (session, 1);after gnutls_init.
selectto check for gnutls pending data, the function gnutls_record_check_pending has to be used to achieve the same functionality as described in Asynchronous operation.
GnuTLS 3.0.x is source compatible with previous versions except for the functions listed below.
|To replace its functionality the function gnutls_record_check_pending has to be used, as described in Asynchronous operation|
|They are replaced by the safer function gnutls_session_get_random|
|Replaced by the keying material exporters discussed in Deriving keys for other applications/protocols|
|Replaced by using the system’s errno facility or gnutls_transport_set_errno.|
|Replaced by gnutls_pubkey_verify_data2.|
|Replaced by gnutls_certificate_verify_peers2.|
|Removed. The key derivation function was never standardized.|
|Removed. Extension registration API is now internal to allow easier changes in the API.|
|Removed to allow updating the internal structures. Replaced by gnutls_certificate_get_issuer.|
|Removed. The inner application extensions were completely removed (they failed to be standardized).|
GnuTLS 3.1.x is source and binary compatible with GnuTLS 3.0.x releases. Few functions have been deprecated and are listed below.
|The function gnutls_pubkey_verify_hash2 is provided and is functionally equivalent and safer to use.|
|The function gnutls_pubkey_verify_data2 is provided and is functionally equivalent and safer to use.|
GnuTLS 3.2.x is source and binary compatible with GnuTLS 3.1.x releases. Few functions have been deprecated and are listed below.
|The function gnutls_privkey_sign_hash is equivalent
when the flag |
GnuTLS 3.3.x is source and binary compatible with GnuTLS 3.2.x releases; however there few changes in semantics which are listed below.
|No longer required. The library is initialized using a constructor.|
|No longer required. The library is deinitialized using a destructor.|
GnuTLS 3.4.x is source compatible with GnuTLS 3.3.x releases; however, several deprecated functions were removed, and are listed below.
|Priority string "NORMAL" has been modified||The following string emulates the 3.3.x behavior "NORMAL:+VERS-SSL3.0:+ARCFOUR-128:+DHE-DSS:+SIGN-DSA-SHA512:+SIGN-DSA-SHA256:+SIGN-DSA-SHA1"|
|No replacement; the library does not support the RSA-EXPORT ciphersuites.|
|No replacement; a similar function is gnutls_x509_crt_get_signature_algorithm.|
|No replacement; a similar function is gnutls_pubkey_get_preferred_hash_algorithm.|
|gnutls_privkey_sign_hash with the flag GNUTLS_PRIVKEY_SIGN_FLAG_TLS1_RSA|
GnuTLS 3.6.x is source and binary compatible with GnuTLS 3.5.x releases; however, there are minor differences, listed below.
|The priority strings "+COMP" are a no-op||TLS compression is no longer available.|
|The SSL 3.0 protocol is a no-op||SSL 3.0 is no longer compiled in by default. It is a legacy protocol which is completely eliminated from public internet. As such it was removed to reduce the attack vector for applications using the library.|
|The hash function SHA2-224 is a no-op for TLS1.2||TLS 1.3 no longer uses SHA2-224, and it was never a widespread hash algorithm. As such it was removed for simplicity.|
|The SRP key exchange accepted parameters outside the [TLSSRP] spec||The SRP key exchange is restricted to [TLSSRP] spec parameters to protect clients from MitM attacks.|
|The compression-related functions are deprecated||No longer use |
|gnutls_x509_crt_sign, gnutls_x509_crl_sign, gnutls_x509_crq_sign||These signing functions will no longer sign using SHA1, but with a secure hash algorithm.|
|gnutls_certificate_set_ocsp_status_request_file||This function will return an error if the loaded response doesn’t match
any of the present certificates. To revert to previous semantics set the |
|The callback gnutls_privkey_import_ext3 is not flexible enough for new signature algorithms such as RSA-PSS||It is replaced with gnutls_privkey_import_ext4|
|Re-handshake functionality is not applicable under TLS 1.3.||It is replaced by separate key update and re-authentication functionality which can be accessed directly via gnutls_session_key_update and gnutls_reauth.|
|TLS session identifiers are not shared with the server under TLS 1.3.||The TLS session identifiers are persistent across resumption only on server side and can be obtained as before via gnutls_session_get_id2.|
|gnutls_pkcs11_privkey_generate3, gnutls_pkcs11_copy_secret_key, gnutls_pkcs11_copy_x509_privkey2||These functions no longer create an exportable key by default; they require the flag |
|gnutls_db_set_retrieve_function, gnutls_db_set_store_function, gnutls_db_set_remove_function||These functions are no longer relevant under TLS 1.3; resumption under TLS 1.3 is done via session tickets, c.f. gnutls_session_ticket_enable_server.|
|gnutls_session_get_data2, gnutls_session_get_data||These functions may introduce a slight delay under TLS 1.3 for few milliseconds. Check output of gnutls_session_get_flags for GNUTLS_SFLAGS_SESSION_TICKET before calling this function to avoid delays.|
|SRP and RSA-PSK key exchanges are not supported under TLS 1.3||SRP and RSA-PSK key exchanges are not supported in TLS 1.3, so when these key exchanges are present in a priority string, TLS 1.3 is disabled.|
|Anonymous key exchange is not supported under TLS 1.3||There is no anonymous key exchange supported under TLS 1.3, so if an anonymous key exchange method is set in a priority string, and no certificate credentials are set in the client or server, TLS 1.3 will not be negotiated.|
|ECDHE-PSK and DHE-PSK keywords have the same meaning under TLS 1.3||In the priority strings, both |
|Authentication-only ciphersuites are not supported under TLS 1.3||Ciphersuites with the |
|Supplemental data is not supported under TLS 1.3||The TLS supplemental data handshake message (RFC 4680) is not supported under TLS 1.3, so if the application calls gnutls_supplemental_register or gnutls_session_supplemental_register, TLS 1.3 is disabled.|