sslc - routines useful for SSL clients
These routines are intended for use by SSL based clients. Routines which are shared between clients and servers are documented in sslfd(3).
setMyId() should be called before anything else, as it sets the prompt that SSLeay will use to prompt for passwords. The aim is that the client will tell the user what its name and process id are so that the user knows to ignore any important message that does not include that tag - such as a prompt for their certificate password.
A typical client then calls:
sslc_init(cert_file, key_file, cipher_list, verify_flag, init_flags);
ssl_init(cert_file, key_file, cipher_list, verify_flag, verify_cb, log_lev, init_flags):
and provides appropriate callback and log_lev arguments. The client can then call one of:
sslc_start_cb(sock, active, flags, verify_cb,
ssl_start_cb(sock, log_lev, active, verify_cb,
The only feature that the sslc_start() routines have over ssl_start_cb() is that if bit one of flags is set, they issue a status message indicating that SSL is established and which cipher is being used.
ssld(3), ssl_rcmd(3), ssl(3), netio(3).
The current version of SSLeay can be obtained from: ftp://ftp.psy.uq.oz.au/pub/Crypto/SSL/SSLeay-x.xx.tar.gz
The SSLeay FAQ by Tim Hudson <email@example.com> can be found at http://www.psy.uq.oz.au/~ftp/Crypto
Simon J. Gerraty <firstname.lastname@example.org>
Table of Contents