On Wed, 8 Apr 1998, Tim Bass wrote:
> Concur. Does anyone have a suggestion on the top 10 lib functions
> to do man(3) pages on?
>
> I would like to make sure that my initial efforts reap the maximum
> benefit for the ssleay team.
For clients, they all need minimally
SSLeay_add_ssl_algorithms
SSL_CTX_new
SSLv23_client_method (and v2 and v3)
SSL_CTX_set_options
SSL_CTX_set_default_verify_paths
SSL_set_fd
SSL_new
SSL_connect
SSL_read
SSL_write
SSL_free
Servers and cert supporting clients would add minimally
SSL_accept
SSL_use_RSAPrivateKey_file
SSL_use_certificate_file
SSL_CTX_set_verify
And for printing out interesting things and doing status:
X509_STORE_CTX_get_* (most of these)
X509_NAME_oneline
BIO_printf
ASN1_UTCTIME_print
X509_get_notBefore
X509_get_notAfter
PEM_write_X509
SSL_load_error_strings
ERR_load_crypto_strings
SSL_get_cipher
ERR_error_string
ERR_get_error
Noting there are often SSL_CTX_set and SSL_set which do similar things,
but one on a context and one on a connection, but most would be a single
page (but 2 links).
And explaining the critical innards of the structures would also be
useful.
I think the above are all I use for my SSL-via-proxy programs, which do
both server and client, but I just read the source and didn't do a nm on
the object.
--- reply to tzeruch - at - ceddec - dot - com ---
+-------------------------------------------------------------------------+
| Administrative requests should be sent to [EMAIL PROTECTED] |
| List service provided by Open Software Associates, http://www.osa.com/ |
+-------------------------------------------------------------------------+
