Sean, you've been a huge help. Last round of questions, I promise. In the
context of the J2SE 1.4.2_03 distro:
rt.jar (Sun JCA provider part 1/2)
(SHA1 hash algorithm)
sunrsaasign.jar (Sun JCA provider part 2/2)
(SHA1withRSA signature algorithm - assumed PKCS#1 impl as opposed to NIST
X9.42 imp
Anderson Jonathan wrote:
Many, many thanks Sean. You just settled quite a few discussions in my
shop.
You're welcome.
A follow up question:
Slides presented at JavaOne referred to JSR 105 and 106 being included in
J2SE 1.5. What does this imply, exactly?
105/106 were originally targeted for J
Many, many thanks Sean. You just settled quite a few discussions in my
shop.
A follow up question:
Slides presented at JavaOne referred to JSR 105 and 106 being included in
J2SE 1.5. What does this imply, exactly? Are JSR 105 and 106 built around
an SPI model like JCA/JCE are? Will there be a
Anderson Jonathan wrote:
Hi everyone,
Apologies in advance for what is probably a rather naive question. Current
distributions of Apache XML-Security contain no third party JCE, but all of
the documentation points to using the latest versions of the Bouncy Castle
JCE as the provider for XM
Hi everyone,
Apologies in advance for what is probably a rather naive question. Current
distributions of Apache XML-Security contain no third party JCE, but all of
the documentation points to using the latest versions of the Bouncy Castle
JCE as the provider for XML-Security. I am dealing
Hi,
there are cases where the receiver of an XML document that includes encrypted data is
not the consumer of that data (e.g. does not own the private key). This "proxy" entity
is expected to copy the encrypted information into another document and send it to the
intended consumer.
The existing
When I set XSECURIResolverGenericWin32 I got an error when
verifying detached signature in separate file, if signed file have space
(" ") in its folder or file name. Example:
XSECURIResolverGenericWin32 theResolver;
sig->setURIResolver(&theResolver);
Best regards,
Milan
Hi heyjung,
IMHO you should use the ed.getElementsByTagNameNS()
method to get the xenc:... element because its a
namespace qualified element. Please refer to
DOM API documentation.
Regards,
Werner
> -Ursprüngliche Nachricht-
> Von: news [mailto:[EMAIL PROTECTED] Im Auftrag von hyejun
