SSL accelerator support is built in the engine code but you need to actually
use the appropriate library calls in your code to utilize the hardware. The
following code should get you started.
ENGINE *e;
ERR_load_ENGINE_strings; // load engine error strings
e = ENGINE_by_id("cswift"); // u
On Friday 27 July 2001 10:04 am, you wrote:
> Hi all.
>
> I followed instructions in
> http://marc.theaimsgroup.com/?l=openssl-users&m=99494629705968&w=2
> to find memory leaks in my application.
>
> The output generated by CRYPTO_mem_leaks_fp (as show below) tells me
> that 899 bytes were leaked
hich you think are leaks. I found that I could reformat
> the data with awk and do a diff between a number of sessions to see
where
> the memory was growing.
>
> Steve
>
> On Wed, 11 Jul 2001, C. Gould wrote:
> > I've been tuning up my code and am now trying to locate s
I've been tuning up my code and am now trying to locate sources of what
appears to be some leaking memory. I've searched the archives and saw
a bit of discussion about compiling with -DCRYPTO_MDEBUG set. When I did
so there was no indication that any sort of leaks were even trying to be
detected
Ah, big difference. It is running much, much faster, and now runs pretty
much even with the apache/mod_ssl server. Thanks Geoff.
Chris
On Monday 09 July 2001 11:17 am, you wrote:
> On Mon, 9 Jul 2001, C. Gould wrote:
> > I've created some server code based on openssl 0.9.6 th
