Hi All. We wish to exhange data over sockets in embedded-environments, and unfortunately can't afford to use the de-facto openssl implementation, which I believe uses dynamic memory allocations/deallocations in its code (we intend to deploy our solution using bare-metal C, in environments where even no RTOS are available). I googled a lot, but somehow managed to fail in finding the native SSL-signalling steps. We are wishing to gain some information on native SSL-signalling, much like what GET/POST/PUT/DELETE are for HTTP. Since OpenSSL is the de-facto/expert in this field, may I please put forward my earnest request for directing us to some literature in this regard, wherein we can set up a SSL-context using absolute native SS7-signalling. Our plan is pretty straighforward :: 1) Connect to a nginix-erver on its HTTPS port. 2) <Set up SSL-context using native SS7-signalling, on the same socket of step 1> 3) Just before what would have been a normal socket "send", we encrypt the data using the server-public-key obtained from step 2, and then send the encrypted data (over the socket of step 1). 4) Just after what would have been a normal socket "recv", we decrypt the data (obtained from the socket of step 1) using the client-private-key obtained from step 2, and then have it available to the client's software. Looking forward to some pointers... Thanks and Regards, Ajay -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mta.openssl.org/pipermail/openssl-users/attachments/20150816/ab65f34e/attachment.html>
