lized bytes, before it is digested.
My guess is that it is something subtle (it always is) probably with
namespaces. You may also try using the Java XML DSig implementation in
JDK 6 or XMLSec 1.4.1, which is more up to date.
--Sean
Ulrich Ackermann wrote:
> Hi all,
>
> I have got a quest
Hi all,
I have got a question concerning the interoperability between the Apache XML
Security framework (we are currently using the version 1.3.0) and the Sun
implementation of XML DSIG (Java XML Digital Signature API, 1.0 EA2).
Currently we are running into problems because the opposite applica
I am using a symmetric key for encryption, so if
it is possible to encrypt with the private key of the sender, that would be
even better.
Kind regards
Joseph
-Original Message-
From: Ulrich Ackermann [mailto:[EMAIL PROTECTED]
Sent: 15 June 2007 21:45
To: security-dev@xml.apache.org
Su
Hi Thomas,
this is exactly what I was stating in a previous post to Joseph:
"Why do you want to SIGN a document with a PUBLIC key? I have never heard of
anything like that. There is no authenticy involved when signing with a public
key, but I guess you know that."
Cheers,
Ulrich
-Ursprüng
throw new CustomException (ex.getMessage(), ex);
} // end catch
catch (ParserConfigurationException pce) {
pce.printStackTrace();
} // end catch
return dc;
} // end sign()
Kind regards
atch
catch (ParserConfigurationException pce) {
pce.printStackTrace();
} // end catch
return dc;
} // end sign()
Kind regards
-Original Message-
From: Ulrich Ackermann
Sent: 06 June 2007 23:57
To: security-dev@xml.apache.org
Subject: RE: En
database, so
there is no difficutly retrieving it.
Thanks and Regards
Joseph
-Original Message-
From: Ulrich Ackermann [mailto:[EMAIL PROTECTED]
Sent: 05 June 2007 22:50
To: security-dev@xml.apache.org
Subject: Re: Encrypt with public key
Hi Joseph,
Sure is this possible. That's
Hi Joseph,
Sure is this possible. That's what Apache XML Security is all about, isn't it?
:)
But I would first sign the message and encrypt it afterwards. That gives a
hacker less information because all signature related information is in the
encrypted part of the receipt.
Cheers,
Ulrich
---
t how you do
signing?
Regards,
On 12/6/06, Ulrich Ackermann <
[EMAIL PROTECTED]> wrote:Hello Dominik,
If I take your Base64 encoded SHA-1 hash value and make a hex string out of it,
I get exactly what you stated as your CrypTool result.
It seems to me, that your conversion from Base64 to
Hello Dominik,
If I take your Base64 encoded SHA-1 hash value and make a hex string out of it,
I get exactly what you stated as your CrypTool result.
It seems to me, that your conversion from Base64 to hex string is incorrect.
I used the following code:
String base64Encoded = "oZMIFC8bdyDbF4e42Q
providers
that register when you initialize the jss, which causes different
signaturevalues. I have no idea why they calculate different values, but they
do, even if the data that gets sent in is the same.
miha
-Original Message-----
From: Ulrich Ackermann [mailto:[EMAIL PROTECTED]
Sen
he misleading question,
Ulrich
security-dev@xml.apache.org schrieb am 23.01.06 23:13:40:
Does the card support PKCS#11? If so, have you tried using it with a
PKCS#11 JCE provider, such as the one in Sun's JDK 5.0? :
http://java.sun.com/j2se/1.5.0/docs/guide/security/p11guide.html
--Sean
Ulrich Ac
Hi,
I've been looking quit a while without any luck for any advice or examples for
getting an XMLSignature done with the constraint, that the private key can't be
offered the XML Security framework (because he is on a Smartcard, e.g.).
All attempts getting or creating the "right" digest and encr
13 matches
Mail list logo
