← Back to branch summary

~ubuntu-branches/ubuntu/quantal/gnutls26/quantal

« back to all changes in this revision

Viewing changes to doc/manpages/gnutls_rehandshake.3

  • Committer: Bazaar Package Importer
  • Author(s): Steve Langasek
  • Date: 2011-05-20 13:07:18 UTC
  • mfrom: (12.1.11 sid)
  • Revision ID: james.westby@ubuntu.com-20110520130718-db41dybbanzfvlji
Tags: 2.10.5-1ubuntu1
* Merge from Debian unstable, remaining changes:
  - Fix build failure with --no-add-needed.
  - Build for multiarch.

Show diffs side-by-side

added added

removed removed

Lines of Context:
doc/manpages/gnutls_rehandshake.3
1
1
.\" DO NOT MODIFY THIS FILE!  It was generated by gdoc.
2
 
.TH "gnutls_rehandshake" 3 "2.8.6" "gnutls" "gnutls"
 
2
.TH "gnutls_rehandshake" 3 "2.10.5" "gnutls" "gnutls"
3
3
.SH NAME
4
 
gnutls_rehandshake \- renegotiate security parameters
 
4
gnutls_rehandshake \- API function
5
5
.SH SYNOPSIS
6
6
.B #include <gnutls/gnutls.h>
7
7
.sp
20
20
\fBgnutls_handshake()\fP function in order to negotiate the new
21
21
parameters.
22
22
 
 
23
Since TLS is full duplex some application data might have been
 
24
sent during peer's processing of this message. In that case
 
25
one should call \fBgnutls_record_recv()\fP until GNUTLS_E_REHANDSHAKE
 
26
is returned to clear any pending data. Care must be taken if
 
27
rehandshake is mandatory to terminate if it does not start after
 
28
some threshold.
 
29
 
23
30
If the client does not wish to renegotiate parameters he will
24
31
should with an alert message, thus the return code will be
25
32
\fBGNUTLS_E_WARNING_ALERT_RECEIVED\fP and the alert will be