I don't have the specific code, but it's not that much. I take it that
you're issuing your own certs with the acceptable client ip in the
"subjectAltName" - you might want to allow a range.
I have similar code but not for this purpose, so let's see if I can put
them together. My code looks at th
I don't know if you're writing a client or a server, but I'll just
describe what I did:
- hack up your code with some conditional memory debugging stuff such
that it accepts (or connects) a fixed number of times and then
calls CRYPTO_mem_leaks_fp() and exits.
- run the program for one connect
You need to do the following in your code -
at start:
CRYPTO_malloc_debug_init();
CRYPTO_dbg_set_options(V_CRYPTO_MDEBUG_ALL);
CRYPTO_mem_ctrl(CRYPTO_MEM_CHECK_ON);
at end:
CRYPTO_mem_leaks_fp(stderr);
This produces tons of memory references that you'll have to s
See http://www.modssl.org/docs/2.6/ssl_faq.html#remove-passphrase
steve
On Tue, 14 Nov 2000, Carl Ma wrote:
> Hello all,
>
>
> I am using Apache 1.3.14 with openssl-0.9.5a on Redhat 6.2(kernel 2.2.14-5.0).
> Everything works fine and I create my key file with CA.pl after inputting the
> pri
I use this:
SSL *ss;
int rc, connected;
while ( !connected ) {
rc = SSL_connect(ss); /* returns '1' on success */
connected = ((rc == 1) && SSL_is_init_finished(ss));
if (rc <= 0) {
