diff options
author | Nikos Mavrogiannopoulos <nmav@redhat.com> | 2017-06-26 10:18:33 +0200 |
---|---|---|
committer | Nikos Mavrogiannopoulos <nmav@gnutls.org> | 2017-07-10 07:40:18 +0000 |
commit | b4aed16ee30f76211c13b075149bb87c012f9bf6 (patch) | |
tree | 30f74421f9502515d2778e2ade140003cb45a3af /doc | |
parent | fd9cc393ba5fba46c2d98c2cb8470863039e75e2 (diff) | |
download | gnutls-b4aed16ee30f76211c13b075149bb87c012f9bf6.tar.gz |
Documented use gnutls_priority_set2().
Signed-off-by: Nikos Mavrogiannopoulos <nmav@redhat.com>
Diffstat (limited to 'doc')
-rw-r--r-- | doc/cha-gtls-app.texi | 2 | ||||
-rw-r--r-- | doc/cha-intro-tls.texi | 2 | ||||
-rw-r--r-- | doc/cha-upgrade.texi | 4 | ||||
-rw-r--r-- | doc/examples/ex-serv-dtls.c | 2 | ||||
-rw-r--r-- | doc/examples/ex-serv-psk.c | 2 | ||||
-rw-r--r-- | doc/examples/ex-serv-x509.c | 2 |
6 files changed, 9 insertions, 5 deletions
diff --git a/doc/cha-gtls-app.texi b/doc/cha-gtls-app.texi index 37df31a5db..bc06c5e2b0 100644 --- a/doc/cha-gtls-app.texi +++ b/doc/cha-gtls-app.texi @@ -1075,7 +1075,7 @@ specific algorithm details, as the priority strings are not constant between gnutls versions (they are periodically updated to account for cryptographic advances while providing compatibility with old clients and servers). -@showfuncB{gnutls_priority_set_direct,gnutls_priority_set} +@showfuncB{gnutls_priority_set_direct,gnutls_priority_set2} @float Table,tab:prio-keywords @multitable @columnfractions .20 .70 diff --git a/doc/cha-intro-tls.texi b/doc/cha-intro-tls.texi index 3f1ea66126..a8dc95c8af 100644 --- a/doc/cha-intro-tls.texi +++ b/doc/cha-intro-tls.texi @@ -273,7 +273,7 @@ solves the problem by using minimal padding. If you implement an application that has a configuration file, we recommend that you make it possible for users or administrators to specify a GnuTLS protocol priority string, which is used by your -application via @funcref{gnutls_priority_set}. To allow the best +application via @funcref{gnutls_priority_set2}. To allow the best flexibility, make it possible to have a different priority string for different incoming IP addresses. diff --git a/doc/cha-upgrade.texi b/doc/cha-upgrade.texi index 0401719ec9..f32acfadc7 100644 --- a/doc/cha-upgrade.texi +++ b/doc/cha-upgrade.texi @@ -199,4 +199,8 @@ however, there are minor differences, listed below. @funcintref{gnutls_compression_get_name}, @funcintref{gnutls_compression_list}, and @funcintref{gnutls_compression_get_id}. +@item The @funcref{gnutls_priority_set} has been superseded by @funcref{gnutls_priority_set2}. +@tab The function @funcref{gnutls_priority_set2} allows for sharing priority +caches across multiple sessions reducing allocated memory per session. + @end multitable diff --git a/doc/examples/ex-serv-dtls.c b/doc/examples/ex-serv-dtls.c index 887b4b83df..0166493b3d 100644 --- a/doc/examples/ex-serv-dtls.c +++ b/doc/examples/ex-serv-dtls.c @@ -174,7 +174,7 @@ int main(void) continue; gnutls_init(&session, GNUTLS_SERVER | GNUTLS_DATAGRAM); - gnutls_priority_set(session, priority_cache); + gnutls_priority_set2(session, priority_cache, 0); gnutls_credentials_set(session, GNUTLS_CRD_CERTIFICATE, x509_cred); diff --git a/doc/examples/ex-serv-psk.c b/doc/examples/ex-serv-psk.c index 26aad02f47..6463fddca8 100644 --- a/doc/examples/ex-serv-psk.c +++ b/doc/examples/ex-serv-psk.c @@ -109,7 +109,7 @@ int main(void) client_len = sizeof(sa_cli); for (;;) { gnutls_init(&session, GNUTLS_SERVER); - gnutls_priority_set(session, priority_cache); + gnutls_priority_set2(session, priority_cache, 0); gnutls_credentials_set(session, GNUTLS_CRD_CERTIFICATE, x509_cred); gnutls_credentials_set(session, GNUTLS_CRD_PSK, psk_cred); diff --git a/doc/examples/ex-serv-x509.c b/doc/examples/ex-serv-x509.c index 4bf1940b89..65f94a3b94 100644 --- a/doc/examples/ex-serv-x509.c +++ b/doc/examples/ex-serv-x509.c @@ -107,7 +107,7 @@ int main(void) client_len = sizeof(sa_cli); for (;;) { CHECK(gnutls_init(&session, GNUTLS_SERVER)); - CHECK(gnutls_priority_set(session, priority_cache)); + CHECK(gnutls_priority_set2(session, priority_cache, 0)); CHECK(gnutls_credentials_set(session, GNUTLS_CRD_CERTIFICATE, x509_cred)); |