[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [GNU Crypto] Re: [Jessie-discuss] Re: RFC: merging GNU Crypto and Je

From: Raif S. Naffah
Subject: Re: [GNU Crypto] Re: [Jessie-discuss] Re: RFC: merging GNU Crypto and Jessie
Date: Mon, 12 Dec 2005 20:48:44 +1100
User-agent: KMail/1.9.1

On Monday 12 December 2005 01:45, Anthony Green wrote:
> On Sun, 2005-12-11 at 15:19 +0100, Mark Wielaard wrote:
> > If there are situations where you are not able to (re)distribute
> > the GNU Classpath source code and/or follow the the BIS/ENC
> > notification procedures as done by the various GNU/Linux distros to
> > distribute binary derivatives of GNU Classpath as Free Software
> > works then please let us know.
> I don't think my situation is relevant to public Linux distros.
> I'm told the rules are different when you want to make a private
> distribution of FOSS crypto code (ie. not easily found on a public
> web/ftp site).  In my specific case, it's easier just to remove the
> problematic code completely.

would adding a second Provider --that supplies the strong stuff; i.e. 
ciphers, modes, padding, etc..-- living in its own package 
sub-directory/hierarchy and eventually (when the segmentation of 
Classpath into multiple jars occur) be packaged in its own jar help 
solve your problem?


Attachment: pgp2FqA64K4D1.pgp
Description: PGP signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]