Nils,
The basic succession of calls are as follows. I think the program waits for an ssl_read or ssl_write to implicitly trigger the handshake process.
meth = TLSv1_client_method()
SSL_load_error_strings();
SSLeay_add_ssl_algorithms();
SSL_CTX_new(meth);
ssl = SSL_new( ctx );
sbio = BIO_new_socket( sock, BIO_NOCLOSE );
SSL_set_bio( ssl, sbio, sbio );
SSL_set_connect_state( ssl );
iSslInitStatus = SSL_in_init( ssl );
After that, the only API calls are ssl_read(), ssl_write() and an occasional SSL_pending( ssl ).
| Nils Larsch <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED] 08/29/2006 02:58 PM
|
|
[EMAIL PROTECTED] wrote:
>
> Nils,
>
> Yes. I read the entire e-mail. I can't find ANYWHERE where it's being
> fed to the application, (including the source code). As far as I can
> see, it's definitely not being used in an ssl_ library call nor is he
which ssl api calls are used to initialize the ssl context ?
Cheers,
Nils
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List openssl-users@openssl.org
Automated List Manager [EMAIL PROTECTED]
