Raul Miller <[EMAIL PROTECTED]> writes:
> A tempting idea: start a project derived from ssleay, and reimplement
> openssl.
I believe openssl inherits most of its GPL-incompatible clauses from
ssleay. For example, I have an old copy of fcrypt.c, which is part of
Eric Young's libdes, which includes:
* 3. All advertising materials mentioning features or use of this software
* must display the following acknowledgement:
* "This product includes cryptographic software written by
* Eric Young ([EMAIL PROTECTED])"
* The word 'cryptographic' can be left out if the rouines from the library
* being used are not cryptographic related :-).
which is the BSD advertising clause that is incompatible with the GPL.
There's also:
* The licence and distribution terms for any publically available version or
* derivative of this code cannot be changed. i.e. this code cannot simply be
* copied and put under another distribution licence
* [including the GNU Public Licence.]
which I would read as being GPL-incompatible in the opposite
direction, because the GPL adds additional restrictions (must provide
source) and changes the distribution terms.
--
Carey Evans http://home.clear.net.nz/pages/c.evans/
"May not be representative of the experience of actual customers."
