* Charles Fry:
> Well, I may not entirely understand your question, but here is my
> understanding of the situation, as supported by the document How to
> Implement a Provider for the JavaTM Cryptography Extension[1].
Unfortunately, this document doesn't explain why the certificate is
needed.
>
> > 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
* Charles Fry:
> I should also point out that this JCE Code Signing Certificate is
> necessary not only to allow libbcprov-java to be used as a trusted
> security provider, but also for me to package bcmail, bctsp, and bcpg
> which are also part of Bouncy Castle. I can currently build all of them,
I should also point out that this JCE Code Signing Certificate is
necessary not only to allow libbcprov-java to be used as a trusted
security provider, but also for me to package bcmail, bctsp, and bcpg
which are also part of Bouncy Castle. I can currently build all of them,
but the regression test
Do not know there to post, so I post here.
Eclipse 3.1 packages (from http://www.backports.org/~mkoch/) contain a bug -
the plugin org.apache.ant is missing libraries (like ant-jai.jar, etc), but
MANIFEST.MF of the org.apache.ant have them in the classpath. This leads to the
following error whe
6 matches
Mail list logo
