Re: Force Reuse, Porting Old Code

null@example.com (todd) — Mon, 06 May 2013 21:31:19 +0000

The proper way to do this is to extend the timeout value that is compared with the bornOn time. This can be done with:

wolfSSL_set_timeout()

It defaults to 500 seconds, but wolfSSL_set_timeout() can increase that value to whatever you like.

-Todd

Force Reuse, Porting Old Code

null@example.com (yuvalperlov) — Sat, 04 May 2013 16:10:36 +0000

I am porting some code from wolfSSL 1.5 to 2.6.

Most APIs seem very stable but I came upon this which uses an internal api (used to be in wolfssl_int.h):

static void saveforreuse(iao_connection *c)
{
if (doreuse(c))
{
agentsslsession = SSL_get_session(c->ssl);
agentsslsession->bornOn = LowResTimer();
}
}

I am guessing from the function names that the programmer was aiming to force the system to keep using the same ssl session across hits (the use case is a 5 minute https keep alive).

Does this make any sense? Would it have the intended effect?
What is the correct way of doing this in the 2.6 release?

Yuval

wolfSSL - Embedded SSL Library — Force Reuse, Porting Old Code

Re: Force Reuse, Porting Old Code

Force Reuse, Porting Old Code