> > This is a big field which needs even bigger investigation. The free
> > runtimes can load them but signed jars are still not supported (or was
> > this fixed lately...). Your best action would be to just test it with
> > kaffe or gcj or whatever and report any bugs you find.
>
> In the meantim
> > In order to be trusted, the security provider must be signed with a
> > key that was certified by the JCE Code Signing Certification
> > Authority (see Step 5 of the document above).
>
> So why can't we ship trusted root certificates for a Debian Code
> Signing Certification Authority, or trus
> > Can someone please comment on how we should proceed to obtain a JCE Code
> > Signing Certificate for Debian?
>
> Why can't we just install a trusted certificate in our own packages?
>
> It's not clear to me who should own the private key corresponding to
> the certificate, either. Perhaps yo
tests fail as the resulting jars need to be signed.
Can someone please comment on how we should proceed to obtain a JCE Code
Signing Certificate for Debian?
thanks,
Charles
-Original Message-
> From: Charles Fry <[EMAIL PROTECTED]>
> Subject: JCE Code Signing Certificate
> Da
Now that BouncyCastle[1] has been packaged for Debian[2], it is time for
us to move forward with Arnaud's suggestion[3] that we obtain a JCE Code
Signing Certificate[4] for Debian, in order to vouch for this and other
JCE Security Providers that Debian may provide.
The process is fairly straight-f
5 matches
Mail list logo
