From 5dadf34209c288b8fffba1016e6a3c9446381153 Mon Sep 17 00:00:00 2001 From: Rob Austein Date: Thu, 7 Jun 2007 02:37:32 +0000 Subject: Replace hacked OpenSSL code with OpenSSL 0.9.8e distribution. svn path=/openssl/Makefile; revision=659 --- openssl/trunk/doc/ssl/SSL_state_string.pod | 45 ------------------------------ 1 file changed, 45 deletions(-) delete mode 100644 openssl/trunk/doc/ssl/SSL_state_string.pod (limited to 'openssl/trunk/doc/ssl/SSL_state_string.pod') diff --git a/openssl/trunk/doc/ssl/SSL_state_string.pod b/openssl/trunk/doc/ssl/SSL_state_string.pod deleted file mode 100644 index fe25d47c..00000000 --- a/openssl/trunk/doc/ssl/SSL_state_string.pod +++ /dev/null @@ -1,45 +0,0 @@ -=pod - -=head1 NAME - -SSL_state_string, SSL_state_string_long - get textual description of state of an SSL object - -=head1 SYNOPSIS - - #include - - const char *SSL_state_string(const SSL *ssl); - const char *SSL_state_string_long(const SSL *ssl); - -=head1 DESCRIPTION - -SSL_state_string() returns a 6 letter string indicating the current state -of the SSL object B. - -SSL_state_string_long() returns a string indicating the current state of -the SSL object B. - -=head1 NOTES - -During its use, an SSL objects passes several states. The state is internally -maintained. Querying the state information is not very informative before -or when a connection has been established. It however can be of significant -interest during the handshake. - -When using non-blocking sockets, the function call performing the handshake -may return with SSL_ERROR_WANT_READ or SSL_ERROR_WANT_WRITE condition, -so that SSL_state_string[_long]() may be called. - -For both blocking or non-blocking sockets, the details state information -can be used within the info_callback function set with the -SSL_set_info_callback() call. - -=head1 RETURN VALUES - -Detailed description of possible states to be included later. - -=head1 SEE ALSO - -L, L - -=cut -- cgit v1.2.3