Have you looked at http://www.matrixssl.org/ ?
On 07/03/13 08:37, Peter Sand wrote:
Hello,
My current solution is a cut down version of OpenSSL adapted for an
embedded solution.
So there is no filesystem etc.
A lot of underlying functions are stubbed.
I currently can save the SSL_SESSION in RAM and reuse it as SSL
Session ID when reconnecting.
The idea is to save it in Flash and reuse after power on again.
I've looked at saving the Session like it is done in
s_client -sess_out arg / -sess_in arg
but a lot of functions to serialize SSL_SESSION
ssl.h : PEM_read_bio_SSL_SESSION()
ssl.h : PEM_write_bio_SSL_SESSION()
are unfortuneately stubbed way below.
And I have no filesystem...
I have started looking at options.
Questions
1. Am I correct to observe that I have to save the whole SSL_SESSION
to be able to use the SSL Session ID?
2. Is my assumption correct: Would it be enough to save the TLS Ticket
IDs length & data?
3. I tried to just save the TLS Ticket ID but I cannot get it to work.
a. SSL_CTX_get_tlsext_ticket_keys() -> FLASH
b. REBOOT
c. Init stuff
d. FLASH -> SSL_CTX_set_tlsext_ticket_keys()
e. Connect (does not work)
Can somebody please verify that this should work or not?
4. Any way to avoid saving the whole SSL_SESSION?
5. Any other way to do it? :)
Thanks in advance!
Peter
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List [email protected]
Automated List Manager [email protected]
