Appended two corrections, one extension and one new manpage.
        Lutz
-- 
Lutz Jaenicke                             [EMAIL PROTECTED]
BTU Cottbus               http://www.aet.TU-Cottbus.DE/personen/jaenicke/
Lehrstuhl Allgemeine Elektrotechnik                  Tel. +49 355 69-4129
Universitaetsplatz 3-4, D-03044 Cottbus              Fax. +49 355 69-4153
diff -r -u --new-file 
openssl-SNAP-20000919-vanilla/doc/ssl/SSL_CTX_set_cipher_list.pod 
openssl-SNAP-20000919/doc/ssl/SSL_CTX_set_cipher_list.pod
--- openssl-SNAP-20000919-vanilla/doc/ssl/SSL_CTX_set_cipher_list.pod   Tue Sep 19 
01:00:39 2000
+++ openssl-SNAP-20000919/doc/ssl/SSL_CTX_set_cipher_list.pod   Tue Sep 19 22:28:19 
+2000
@@ -30,6 +30,15 @@
 are simply ignored. Failure is only flagged if no ciphers could be collected
 at all.
 
+It should be noted, that inclusion of a cipher to be used into the list is
+a necessary condition. On the client side, the inclusion into the list is
+also sufficient. On the server side, additional restrictions apply. All ciphers
+have additional requirements. ADH ciphers don't need a certificate, but
+DH-parameters must have been set. All other ciphers need a corresponding
+certificate and key. A RSA cipher can only be chosen, when a RSA certificate is
+available, the respective is valid for DSA ciphers. Ciphers using EDH need
+a certificate and key and DH-parameters.
+
 =head1 RETURN VALUES
 
 SSL_CTX_set_cipher_list() and SSL_set_cipher_list() return 1 if any cipher
diff -r -u --new-file openssl-SNAP-20000919-vanilla/doc/ssl/SSL_clear.pod 
openssl-SNAP-20000919/doc/ssl/SSL_clear.pod
--- openssl-SNAP-20000919-vanilla/doc/ssl/SSL_clear.pod Sat Sep 16 18:01:02 2000
+++ openssl-SNAP-20000919/doc/ssl/SSL_clear.pod Tue Sep 19 22:21:54 2000
@@ -8,7 +8,7 @@
 
  #include <openssl/ssl.h>
 
- int *SSL_clear(SSL *ssl);
+ int SSL_clear(SSL *ssl);
 
 =head1 DESCRIPTION
 
diff -r -u --new-file openssl-SNAP-20000919-vanilla/doc/ssl/SSL_library_init.pod 
openssl-SNAP-20000919/doc/ssl/SSL_library_init.pod
--- openssl-SNAP-20000919-vanilla/doc/ssl/SSL_library_init.pod  Thu Jan  1 01:00:00 
1970
+++ openssl-SNAP-20000919/doc/ssl/SSL_library_init.pod  Tue Sep 19 19:29:37 2000
@@ -0,0 +1,52 @@
+=pod
+
+=head1 NAME
+
+SSL_library_init, OpenSSL_add_ssl_algorithms, SSLeay_add_ssl_algorithms
+- initialize SSL library by registering algorithms
+
+=head1 SYNOPSIS
+
+ #include <openssl/ssl.h>
+
+ int SSL_library_init(void);
+ #define OpenSSL_add_ssl_algorithms()    SSL_library_init()
+ #define SSLeay_add_ssl_algorithms()     SSL_library_init()
+
+=head1 DESCRIPTION
+
+SSL_library_init() registers the available ciphers and digests.
+
+OpenSSL_add_ssl_algorithms() and SSLeay_add_ssl_algorithms() are synonyms
+for SSL_library_init().
+
+=head1 NOTES
+
+SSL_library_init() must be called before any other action takes place.
+
+=head1 IMPORTANT
+
+SSL_library_init() only registers ciphers. Another important initialization
+is the seeding of the PRNG (Pseude Random Number Generator), which has to
+be performed seperately.
+
+=head1 EXAMPLES
+
+A typical TLS/SSL application will start with the library initialization,
+will provide readable error messages and will seed the PRNG.
+
+ SSL_load_error_strings();                /* readable error messages */
+ SSL_library_init();                      /* initialize library */
+ actions_to_seed_PRNG(); 
+
+=head1 RETURN VALUES
+
+SSL_library_init() always returns "1", so it is safe to discard the return
+value.
+
+=head1 SEE ALSO
+
+L<ssl(3)|ssl(3)>, L<SSL_load_error_strings(3)|SSL_load_error_strings(3)>,
+L<RAND_add(3)|RAND_add(3)>
+
+=cut
diff -r -u --new-file openssl-SNAP-20000919-vanilla/doc/ssl/SSL_set_session.pod 
openssl-SNAP-20000919/doc/ssl/SSL_set_session.pod
--- openssl-SNAP-20000919-vanilla/doc/ssl/SSL_set_session.pod   Sat Sep 16 18:01:02 
2000
+++ openssl-SNAP-20000919/doc/ssl/SSL_set_session.pod   Tue Sep 19 22:22:00 2000
@@ -8,7 +8,7 @@
 
  #include <openssl/ssl.h>
 
- int *SSL_set_session(SSL *ssl, SSL_SESSION *session);
+ int SSL_set_session(SSL *ssl, SSL_SESSION *session);
 
 =head1 DESCRIPTION
 

Reply via email to