RE: [VOTE] 1.4.1 Release

+1 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Raul Benito Sent: mercredi, 25. avril 2007 11:34 To: security-dev@xml.apache.org Subject: [VOTE] 1.4.1 Release I haven't recived any bad thing about 1.4.1 releas (ok, I have only receive only one

RE: 1.4.1Beta1 Release

I have tested this version with my JUnit Test cases and it seems that this version is ok, specially for the problem of UTF bug. Regards. Yvan Hess From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Raul Benito Sent: vendredi, 6. avril 2007 11:56 To:

RE: Problems with creating a detached Signature with Java

Hi Jochen, In my case, I sign XML documents having also external reference (non XML document). What you have to do is to add an URI refererence to your external document to your XMLSignature element using something like that sig.addDocument(uri, null, Constants.ALGO_ID_DIGEST_SHA1); And then

RE: 1.4.1 Release planning

Can you send me a pre-release of this version and I will test it against all my Junit test I have. Regards. Yvan From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Raul Benito Sent: vendredi, 9. mars 2007 15:12 To: security-dev@xml.apache.org Subject

RE: Signed document can be corrupted in certain circumstances

with this bug and several others. And we have to reconsider my release strategy as it seems that nobody, not too many people test the release candidates :(. On 2/13/07, Hess Yvan <[EMAIL PROTECTED]> wrote: > > > Hi everybody, > > I think I found a critical bug in

Signed document can be corrupted in certain circumstances

er "☺" (263A) is converted as ":" (3a) but should be (e298ba); this is wrong. It seems that the Canonicalizer class doesn't manage correctly "UTF-8" characters coded on three bytes ! Anybody has an idea ? Can someboy help me because it occurs in the context of

RE: VOTE: Apache xmlsec 1.4RC1 tonight?

-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Raul Benito Sent: lundi, 11. septembre 2006 15:24 To: security-dev@xml.apache.org Subject: VOTE: Apache xmlsec 1.4RC1 tonight? I think we have enough bug fixes to do a RC tonight, what do you think? [x] +1

RE: Version 1.4 doesn't sign XML document correctly

ore correct and incorrect signatures like you send. Anyway feel free to prove me wrong. And really thank for the bug report. One question do you have any performance testing? If you do, I hope you see the outcome of your problems. Regards, Raul On 8/10/06, Hess Yvan <[EMAIL PROTECTED]> wrote: &g

RE: Version 1.4 doesn't sign XML document correctly

ribed bellow? Did you find something ? -Original Message- From: Hess Yvan [mailto:[EMAIL PROTECTED] Sent: jeudi, 10. août 2006 09:18 To: security-dev@xml.apache.org Subject: RE: Version 1.4 doesn't sign XML document correctly Raul, Here is the example of signed XML document. Let

RE: Version 1.4 doesn't sign XML document correctly

That will be great. There is already a regression test but still it does not contain a lot of xpath2 transformations examples(indeed only one). Feel free to send you patches for more tests ;) Regards, Raul On 8/9/06, Hess Yvan <[EMAIL PROTECTED]> wrote: > Raul, > > I can s

RE: Version 1.4 doesn't sign XML document correctly

reate them and check what should be the correct c14n, this takes me "long" time(1 hour, but currently I can only reserve half an hour for xml-sec hacking). So if you can provide me a failling example I can speed up this process. Sorry. Regards, Raul On 8/8/06, Hess Yvan <[

RE: Version 1.4 doesn't sign XML document correctly

: security-dev@xml.apache.org Subject: Re: Version 1.4 doesn't sign XML document correctly Then it is a bug that I introduce rewriting xpath2 filter. I will try to reproduce it with a xfilter with only intersect nodes. Thanks, Regards, Raul On 8/7/06, Hess Yvan <[EMAIL PROTECTED]>

RE: Version 1.4 doesn't sign XML document correctly

t; is including the signature and this is a problem when signing, it depends in the order of doing the reference your going to obtain different digest values. What do you think,can it be your case? Regards, Raul On 8/7/06, Hess Yvan <[EMAIL PROTECTED]> wrote: > It will be difficult t

RE: Version 1.4 doesn't sign XML document correctly

see I am signing one part of the XML document and two external binary documents. The problem seems to come from the first Reference (). The digest value doesn't match after signature verification. The digest values of the two external reference matches. 2006-08-07T12:24:18 Hess

Version 1.4 doesn't sign XML document correctly

Hi,   XML security version 1.4 Beta0 and Beta1 doesn't sign the XML document correctly. I developped a Java library that uses XML security to sign/verify and to encrypt/decrypt XML documents. When I executed my JUNIT tests, they failed when XML document are verified. I have two tests that fa

RE: Version 1.4 doesnt' generate the same XML as V1.3: A default namespace is used for XMLSIG and this causes problem!

4B0-A0033464"WARN  [main] [11:00:25]  Reference - Verification failed for URI "urn:hypersuite:8F1F8E64-C0A8024E0160C4B0-A0033464"WARN  [main] [11:00:25]  Reference - Verification failed for URI "urn:hypersuite:8F1F8E64-C0A8024E0160C4B0-A0033464"  

RE : Version 1.4 doesnt' generate the same XML a s V1.3: A default namespace is used for XMLSIG and thi s causes problem!

he correct behaviour. What do you think? On 7/13/06, Hess Yvan <[EMAIL PROTECTED]> wrote: > Raul, > > I downloaded the XML security source code from apache to check where is > the problem. I saw in your example that your are calling a > Constants.setSignatureSpecNSprefix("

RE: Version 1.4 doesnt' generate the same XML as V1.3: A default namespace is used for XMLSIG and this causes problem!

setSignatureSpecNSprefix("ds"). Pleas tell us if it helps you. Regards, Raul On 7/13/06, Hess Yvan <[EMAIL PROTECTED]> wrote: > > > Hi, > > Due to a problem in XML security library version 1.3 that was not > thread safe, I got the version xmlsec-1.4.Beta0.ja

Version 1.4 doesnt' generate the same XML as V1.3: A default namespace is used for XMLSIG and this causes problem!

Hi,   Due to a problem in XML security library version 1.3 that was not thread safe, I got the version xmlsec-1.4.Beta0.jar. Doing some test I detected that the generated XML encryption block of XML encrypted document is NOT THE SAME in version 1.4 and in the version 1.3. Version 1.4 sets a

RE: XML security seems to be not thread safe...Please Help

ageDigest objects, but mantain one for thread. Also don't change the key if it was already used. (raul) On 7/6/06, Hess Yvan <[EMAIL PROTECTED]> wrote: > OK I will try this version and give you a feedback One question > about this version. It is a beta0 ver

RE: XML security seems to be not thread safe...Please Help

release that will fix this problem here: http://xml.apache.org/security/dist/java-library/xmlsec-1.4.Beta0.jar And you can help debugging the next version, so it does not happen the same problem again. Regards On 7/5/06, Hess Yvan <[EMAIL PROTECTED]> wrote: > > > > It see

XML security seems to be not thread safe...Please Help

environment (all documents are treated by only on thread), I never got an error.   Can somebody help me to resolve the problem? It is critical problem because our application failed and we have to work in a multi-thread environment.   Thanks for your answer. Yvan Hess   Yvan Hess Chief software

RE: xml encryption/decryption of binary data

: security-dev@xml.apache.org Subject: Re: xml encryption/decryption of binary data Hess Yvan wrote: > 3. Then I have to encrypt the external binary > "urn:hypersuite:534177D3-C0A8027601B4E829-57982AC1" MANUALLY. I didnt > find a chance to do it using XML security. It seems

RE: xml encryption/decryption of binary data

: security-dev@xml.apache.orgSubject: RE: xml encryption/decryption of binary data OK. To decrypt, there is xmlCipher.decryptToByteArray(), but I haven't tested it yet.   -Message d'origine-De : Hess Yvan [mailto:[EMAIL PROTECTED]Envoyé : mardi 4 avril 2006 11:56À : se

RE: xml encryption/decryption of binary data

with attachments messages).   -Message d'origine-De : Hess Yvan [mailto:[EMAIL PROTECTED]Envoyé : mardi 4 avril 2006 11:29À : security-dev@xml.apache.orgObjet : RE: xml encryption/decryption of binary data Where you binary datas are stored ? Inside the XML document or o

Bug into XMLCiper.loadEncryptedKey() method

I loaded an EncryptedKey element using the method:  EncryptedKey encryptedKey = XMLCipher.getInstance().loadEncryptedKey(encryptedKeyElt)   When I ask for the CarriedKeyName using encryptedKey.getCarriedName() method,  I got a null value that is wrong because my element c

RE: xml encryption/decryption of binary data

Title: xml encryption/decryption of binary data Where you binary datas are stored ? Inside the XML document or outside the document ? Actualy I am "using" XML security to encryt external binary data and may be I can help you if you explain me the problem in detail.   Regards. Yvan Hess Fr

How to encrypt an external reference ?

Hi,   I have an external document attached to my XML document and I would to encrypt it. Finally, I expect to have in my XML document the following result bellow.   How do I have to proceed, I didn't find a way how to encrypt an external reference using Apache XML security.   Thanks for you

RE: Problem with rsa-1_5 padding mechanism

PROTECTED] Sent: jeudi, 30. mars 2006 11:07 To: security-dev@xml.apache.org Cc: [EMAIL PROTECTED] Subject: Re: Problem with rsa-1_5 padding mechanism Hess Yvan wrote: > - Does it means that XML apache security using RSA/ECB/PKCS1Padding is > the correct one and that IBM XSS4J contains a critic

RE: Problem with rsa-1_5 padding mechanism

ave to use padding. Btw, padding is not something complex and can be easily implemented. Hope it helps, Milan --- Hess Yvan <[EMAIL PROTECTED]> wrote: > I encrypted a XML document containing a element > and a element using XML Apache XML security. I > tried to decrypt it using X

Problem with rsa-1_5 padding mechanism

I encrypted a XML document containing a element and a EncryptedData> element using XML Apache XML security. I tried to decrypt it using XSS4J library and I didn't succeed!!! The problem seems to occur when the secret key encapsulated into the element is decrypted by XSS4J library.   Doin

Error message signing external content as FileInputStream

Title: Error message signing external content as FileInputStream Hi, I sign a XML document having an external content using java version 1.2.1. I pass the external content as a FileInputStream into the XMLSignatureInput constructor and I got on the error console the following message "Mark

RE: When can we expected to have a new official release

:06 +0100, Hess Yvan <[EMAIL PROTECTED]> wrote: > Some bugs has been found into the verson 1.2 and seems to be corrected. When > can we expect to have a new official release ? > > Regards. Yvan Hess > > Yvan Hess > Chief Software Architect > > e-mail: [EMAIL PROTEC

When can we expected to have a new official release

Some bugs has been found into the verson 1.2 and seems to be corrected. When can we expect to have a new official release ? Regards. Yvan Hess Yvan Hess Chief Software Architect e-mail: [EMAIL PROTECTED] phone : +41 (0)26 460 66 66 fax : +41 (0)26 460 66 60 Informatique-MTF SA Route du

RE: Resolving external references doesn't work with version 1.2

d message Read-ahead limit < 0 I hope you will find an other way to solve the problem... Regards. Yvan -Original Message- From: Raul Benito [mailto:[EMAIL PROTECTED] Sent: dimanche, 2. janvier 2005 23:32 To: security-dev@xml.apache.org Subject: Re: Resolving external references doesn

Resolving external references doesn't work with version 1.2

Hi, I am signing a XML document having external references. I created my own Resolver (extending ResourceResolverSpi) that returns a XMLSignatureInput object. My resolver works fine with version 1.1 but not with version 1.2. Here is the code... public XMLSignatureInput engineResolve(Attr uri, Str

RE: Bug or Corrupted version 1.2: version 1.2 doesn't sign docum ent a s the version 1.1 !!!

t; ** > Here is the signature result of my XML document with version 1.1: > **** > ** > > id="Revision-1-Signature-1">2004-12-16T15:19:57 gnatureDate>Hess Yvan (first signature) > http://www.w3.org/2000/09/xmldsig#";> > > Algorithm="http://www.

Bug or Corrupted version 1.2: version 1.2 doesn't sign document a s the version 1.1 !!!

Hi, I used version 1.1 and I signed documents that has external URI references using JUNIT tests. Applying the same test with version 1.2, my JUNIT tests failed. I compare the signature and digest value and they are DIFFERENT ! *

RE: Problem of retrieving signature element using XPath expressio n ha ving different namespaces

Problem of retrieving signature element using XPath expression ha ving different namespaces Yvan, Please see inline ... Hess Yvan wrote: >Hi, > >I have a problem to retrieve the Signature element of my signed XML document >using XPath expression. My document looks like that: > > >

Problem of retrieving signature element using XPath expression ha ving different namespaces

Hi, I have a problem to retrieve the Signature element of my signed XML document using XPath expression. My document looks like that: http://www.imtf.com/e-document/dcmi"; xmlns:edoc="http://www.imtf.com/e-document"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; version="1.0"> http://ww

Signing fragment element using XML XPATH transformer

Hi, I would like to sign only a fragment (edoc:metadata) of my XML document using an enveloped signature. Can somebody help me by giving me an example. I did like that but I am not sure I am right and I don't uderstand XPathContainer class and xpath.getElement() result Transforms trans