> -----Original Message-----
> From: Daniel M. Pomerantz [SMTP:[EMAIL PROTECTED]]
> Sent: Monday, April 24, 2000 9:21 PM
> To: [EMAIL PROTECTED]
> Subject: streams and memory
>
> There is a particular way I would like to send and receive SSL data. It
> looks like it's possible, but I just can't nail down exactly how to do it.
> I'd like to create a
> stream or a socket which looks like any other socket, allows me to read
> directly from and write directly to it, but in stead of going to/from a
> file or to another host,
> I want it to pass through SSL_read()/SSL_write() or whatever. It looks
> like the BIO routines (like the ones in s_socket.c) dance around this, but
> I just can't find
> the exact way to do this. Sorry if this is a simple feature of OpenSSL
> which I am overlooking.
>
> Also, I have written a C++ client which runs on Win32. The client runs
> fine, but when the program terminates, VC++ reports "memory leaks"
> detected. I have
> traced it and found that if I call either SSL_load_error_strings() or
> SSLeay_add_ssl_algorithms() then the "leaks" are reported. It seems to me
> that this isn't so
> much a leak, as just failure to cleanup. I've tried calling both
> EVP_cleanup() and ERR_free_strings(), but neither one seems to alleviate
> the problems. Any one
> else know how to prevent these "leaks" from showing up in Win32 C++?
> Thanx.
>
> Daniel M. Pomerantz
>
>
> ______________________________________________________________________
> OpenSSL Project http://www.openssl.org
> User Support Mailing List [EMAIL PROTECTED]
> Automated List Manager [EMAIL PROTECTED]
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
