Hi all,
I am only using SSL for handling TLS/SSL handshakes in libcurl. I am
encountering the memory leaks described in this defect:
http://rt.openssl.org/Ticket/Display.html?id=2561&user=guest&pass=guest
which seem to be caused by not cleaning up the compression methods
stuff.
Does anyone know
Hi,
I am currently using openssl on multilingual platforms and I've come
across an interesting issue. I am using the function
x509_load_crl_file which takes in a path and I've noticed that this
call essentially becomes a call to fopen. For unicode paths (utf8 or
utf16), the function call fails.
Thanks :) That was the problem! Very interesting. I didn't think
order mattered :)
I reordered it and it worked.
J
On Tue, Feb 28, 2012 at 5:30 PM, Wim Lewis wrote:
>
> On 28 Feb 2012, at 5:15 PM, JonathonS wrote:
>> Thanks guys. Sorry for the confusion. I thought "U&q
-lssl --L/home/user/build/libcurl/debug/lib -lcurl -ldl
-lstdc++ -lpthread -lrt -lz -lstdc++
When I built libcurl, I specified the --with-ssl=/.../ flag to point
to my openssl build.
Thanks,
J
On Tue, Feb 28, 2012 at 12:48 PM, Jeremy Farrell
wrote:
>> From: JonathonS [mailto:thejunk...@gm
These are the undefined symbols I believe.
Thanks again for all the help.
J
On Tue, Feb 28, 2012 at 10:39 AM, Wim Lewis wrote:
>
> On 28 Feb 2012, at 9:57 AM, JonathonS wrote:
>> Here is the command I used to build openssl:
>>
>> ./Configure --prefix=/home/user/openssl_
Hi all,
I am building openssl as a static library, and when I link to it, I am
getting a bunch of missing symbols that *should* be defined by
openssl.
Here is the command I used to build openssl:
./Configure --prefix=/home/user/openssl_release
--openssldir=/home/user/openssl_release no-asm threa
