Re: [CryptoAPI-devel] Coding style, or something.

[Justin C. <ju...@po...>]

Hi Kyle,

Kyle McMartin wrote:
> 
> I'm going to, after consensus, begin modifying the code to conform to
> the standards that are the result of this thread.
> 
<snip>

Not fussed about this one way or another.  It will make it easier for
future people to understand the code, which is probably a good idea.
 
> Now the more pressing matter, there are a number of patented and
> GPL licensed modules in cryptoapi. If we wish to release and have people
> integrate our code into their kernels (distributions, for example) we
> must have the entire main cryptoapi package under the GPL or
> dual-licensed. For example, Mandrake currently uses loop-AES, but would
> be unable to include cryptoapi in their kernel, since we have patented and
> non-free ciphers right there.
> 
> To remedy this, I propose a directory hierarchy extension to the
> ciphers/ directory. For example, all free, mainline ciphers could stay
> in their current place, and we could have cryptoapi-patented and
> cryptoapi-nonfree extension tarballs which fill up ciphers/patented/ and
> ciphers/non-free/

This seems to be a very decent first step to solve this problem.  Almost
making the non-GPL ciphers plug-in modules.  In the future we might have
a crypto-API which is pure GPL, and people can further install their
chosen cipher if it's not in the GPL'd list.

This would simplify some issues.

:-)

Regards and best wishes,

Justin Clift


> Comments, questions, flames?
> 
>   - k
> 
> --
> copyleft (c) 2002, Kyle McMartin
> 
>   ------------------------------------------------------------------------
>    Part 1.2Type: application/pgp-signature

-- 
"My grandfather once told me that there are two kinds of people: those
who work and those who take the credit. He told me to try to be in the
first group; there was less competition there."
   - Indira Gandhi