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

Robert M. Münch robert.muench at robertmuench.de
Tue Apr 22 18:11:50 CEST 2008

On Tue, 22 Apr 2008 12:45:58 +0200, Benoit Amiaux <b.amiaux at ateme.com>  

> That's not possible in many cases as Vortex is LGPL and some projects
> may need to comply to section 6.b of this license.

Hi, I don't understand what you referr to. As Vortex is LGPL I don't see a  
problem. LGPL states:

"The main difference between the GPL and the LGPL is that the latter can  
be linked to (in the case of a library, 'used by') a non-(L)GPLed program,  
which may be free software or proprietary software."

> Putting licenses aside, compiling everything statically have many
> disadvantages. Taking zlib as an example, whenever a security exploit
> arise, I prefer updating the single zlib DLL, than having to do 'make
> world' and recompile my whole system. (and it's not even possible in
> case you have proprietary software)

Well, I see it differently. Sending out an update for a single DLL or the  
whole program doesn't make a big logistic difference. And, in the case of  
a DLL, you can't be sure someone else overwrites it again with an unsafe  
version. I prefer to have as much control about such issues as I can.

But anyway, your milage may vary here. Robert

More information about the Vortex mailing list