classpath
[Top][All Lists]
Advanced

[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: Thu, 29 Dec 2005 06:24:08 +1100
User-agent: KMail/1.9.1

hello Anthony,

On Monday 12 December 2005 20:52, Anthony Green wrote:
> On Mon, 2005-12-12 at 20:48 +1100, Raif S. Naffah wrote:
> > 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?
>
> Yes, that would be nice.

looking at the current Classpath package structure and classes, i see 
that an implementation of a Cipher using RSA is already included.  
those are normally part of the javax.crypto strain.  do you strip those 
out when you package your export-controlled applications?


cheers;
rsn

Attachment: pgpO5lUH0Iv70.pgp
Description: PGP signature


reply via email to

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