Greetings All, I've gone through various levels of documentation to see if there is a method available to implement SSL as I have envisioned, but I haven't been able to find what I'm looking for. Perhaps someone here could point me in a good direction...
I'm developing a nonblocking application (backed by several edge-trigger methods, such as epoll/kqueue/etc). I'd like to integrate SSL into the flow, but I'm not fond of pushing the buffering and socket interaction routines into the SSL library. What I would prefer to do is to perform callouts to the ssl library, while maintaining the buffering and socket handling within my application. Ideally, I'd like to perform the recv() calls, buffer the data myself, and pass it to a function that would be capable of decrypting the data (if a complete encryption block is received) - and provide me appropriate returns to let me know if additional steps are required (such as a renegotiation). I'd also prefer to be able to encrypt the data through a function call, and be able to buffer and deliver that data at my leisure. In short, I don't really want SSL doing my writing or buffering. I just want the library to do my negotiation and encryption - but by providing me the data I need rather than by writing to the socket. Does the ability to do this exist? I'm not too fond of fully reverse-engineering SSL itself and using the pure encryption calls, so I'm hoping there exists API's that will let me take this route. If anyone knows of an implementation out there like this, I'd love to see it. Thanks! -Aaron ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager majord...@openssl.org
