apr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Justin Erenkrantz" <jus...@erenkrantz.com>
Subject Re: Proposed Crypto Notification process
Date Sun, 02 Jul 2006 00:05:11 GMT
On 7/1/06, Roy T. Fielding <fielding@gbiv.com> wrote:
> If we remove the patent-encumbered code from OpenSSL, then it isn't
> OpenSSL and we cannot distribute it or anything built from it under
> the TSU exception without distributing the source code exactly as built.
> That means we have to distribute the modified OpenSSL library as
> something
> else *not* called OpenSSL (because otherwise we are violating the
> OpenSSL
> license).  In any case, none of our users want a modified OpenSSL --
> they
> can download the real thing on their own.  What we should be
> redistributing
> is a post-install DLL relinking tool so that they can link our windows
> binary with whatever they install for SSL, but I have no idea how.

Well, removing the patent encumbered bits is just a configure flag to OpenSSL.


So, it doesn't require any code changes to the OpenSSL library itself
- just how we'd build it.  So, I don't see how that'd violate
OpenSSL's license...  -- justin

View raw message