Re: Running SSL on own socket code

Yes it was as straightforward as you mentioned. Thanks to those who responded. jeff On 11-06-02 05:47 AM, Neo Liu wrote: > > > On Wed, Jun 1, 2011 at 10:22 PM, Victor Duchovni > > wrote: > > On Tue, May 31, 2011 at 09:05:29AM -0400, Jeff Saremi wro

Re: Running SSL on own socket code

On Wed, Jun 1, 2011 at 10:22 PM, Victor Duchovni < victor.ducho...@morganstanley.com> wrote: > On Tue, May 31, 2011 at 09:05:29AM -0400, Jeff Saremi wrote: > > > I'd like to know the feasibility or complexity around using my own > > socket code with OpenSSL's ssl code. If I provide OpenSSL with a

Re: Running SSL on own socket code

Depends exactly what the person wants to do and also if he wants to use existing code and if he is familiar with the bio pairs. My point was not specific to his needs as there was not a lot of detail, only that making changes to the code is better and easier when you override functions -- such

Re: Running SSL on own socket code

On Wed, Jun 01, 2011 at 10:56:47AM -0700, Eric S. Eberhard wrote: > The way I do things like this is to slightly modify OpenSSL (and keep track > of the mods!) Completely unnecessary, OpenSSL supports custom I/O layers via BIO pairs. -- Viktor. _

Re: Running SSL on own socket code

The way I do things like this is to slightly modify OpenSSL (and keep track of the mods!) 1) Hunt down the socket code 2) Set a new variable, a pointer to a function (for each function you replace) (fptr in my example) 3) rename the routine to "release_function" 4) make a new function() which

Re: Running SSL on own socket code

On Tue, May 31, 2011 at 09:05:29AM -0400, Jeff Saremi wrote: > I'd like to know the feasibility or complexity around using my own > socket code with OpenSSL's ssl code. If I provide OpenSSL with a pair of > BIOs to read and write would that be sufficient? How tightly integrated > the code is with