[Vortex] [ISSUE] API mismatch using custom SSL contexts

Jens Alfke jens at mooseyard.com
Tue Apr 22 19:03:36 CEST 2008

On 22 Apr '08, at 8:49 AM, Benoit Amiaux wrote:

> If you statically link libvortex with openssl, TLS authentication is  
> not
> useable.

Wouldn't there be license conflicts with that anyway, as OpenSSL is  
BSD while Vortex is LGPL? (I'm not really clear on this, as normally I  
try to stay as far away from *GPL'd code as possible, Vortex being a  
rare exception.)

> The main application, which creates the SSL context may not be
> using the same SSL implementation than the libvortex DLL was compiled
> with (SSL symbols are not accessible anymore).

That sounds like a really good reason not to combine static and  
dynamic linking! Is there a reason against making OpenSSL a DLL that  
both Vortex and your app code link against?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 1875 bytes
Desc: not available
Url : http://lists.aspl.es/pipermail/vortex/attachments/20080422/c0bb142e/attachment.bin 

More information about the Vortex mailing list