At 22.29 22/02/2004, you wrote:
I am out of development for a few weeks but I have some ideas about using OpenSSL in ReactOS but we have one minor show stoppper. The OpenSSL license is not compatible with the GPL so any code that links to OpenSSL is going to need to be either LGPL or GPL with a exception for OpenSSL.
I see a lot of confusion about what exactly uses OpenSSL and what doesn't (not that I have a clear idea of that, either). This looks like the perfect time for planning before diving head-first. Anyone can help us track dependencies of Windows components from cryptography and certificate management functions? I'll start with an easy one: wininet should use whatever SSL/TLS implementation it finds, querying for it with CryptAcquireContext, so it won't depend on OpenSSL
PS: I fail to understand how an "exception" in licensing could help. Advertising OpenSSL would still be required to comply with its license. Not that complying with such a requirement looks such a dramatic burden as to make anything "non-free" - e.g. did you know that the Opera web browser uses OpenSSL? Be quick to think of a counter-counter-example, because I already have a counter-example ready