Re: [CryptoAPI-devel] license clarification

[Herbert V. R. <hv...@hv...>]

On Mon, 2002-03-04 at 21:45, Kyle McMartin wrote:
> alright. i considered reverting all my changes with cvs, but i felt this
> to be unnecessary.
well, as long as you don't forget to revert the kbuild patch ;-)
cause that's a bigger technical show-stopper...
=20
> what i do need, however, is clarification on how cryptoapi is licensed.
> from what i can see, it is a mishmash of differently licensed code,
> which is bad, imho.
please grab the last patch-int-2.4.3 which was created by alex, as this
contains a readme.license or something like this... it may help...
but you'll have to look closely at the comment header of each source
file, and try to find out what kind of license it is...
=20
> is it possible for you to tell me which directories are covered by what?
> i'll assume the cryptoapi.c is GPL as per the original license, however
> the new cryptoapi2 module does not contain any license at all. this
> leads to abit of confusion.
well it's just because I wanted to postpone the license question....
but well, we can handle it now as well... it's just a nasty issue which
needs to be done sooner or later... :-/
=20
> i'll back out the MODULE_LICENSE changes on ciphers and digests in the
> meantime and fix the kbuild, since these seem to be priority.
... but you felt it to be unnecessary... ;)

regards,
--=20
Herbert Valerio Riedel       /    Phone: (EUROPE) +43-1-58801-18840
Email: hv...@hv...       /    Finger hv...@gn... for GnuPG Public Key
GnuPG Key Fingerprint: 7BB9 2D6C D485 CE64 4748  5F65 4981 E064 883F
4142