> > The only options I can think of are to make multiple packages, some
> > with signed jars and some with unsigned jars, or to provide both
> > jars in the same package. Note that this is not just a matter of
> > bein signed by the Legion of the Bouncy Castle; the certificate they
> > use was obta
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Charles Fry <[EMAIL PROTECTED]> writes:
> The only options I can think of are to make multiple packages, some
> with signed jars and some with unsigned jars, or to provide both jars
> in the same package. Note that this is not just a matter of bein
>
> > Basically, the source of the Bouncy Castle Crypto libraries is
> > freely available, however the library jar file is signed by Bouncy
> > Castle, which is necessary for its use as a Java security provider.
>
> Bad.
>
> > As far as I can tell, in creating a Java library package, I want to
> >
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Charles Fry <[EMAIL PROTECTED]> writes:
> Basically, the source of the Bouncy Castle Crypto libraries is freely
> available, however the library jar file is signed by Bouncy Castle,
> which is necessary for its use as a Java security provider.
Bad.
On Mon, 5 Apr 2004, Charles Fry wrote:
> Hi,
>
> I sent this to debian-mentors with no response yet, and started thinking
> maybe I should send it to debian-java instead. In any case:
>
> I have started work on packaging the Bouncy Castle Crypto libraries
> for Java (bug #234048). I think I have m
5 matches
Mail list logo