Dittmann,
There's another approach you can try:
- Canonicalize once.
- Create a document (again) out of the c14n output.
- Serialize the document and in the process add xmlns="" at the desired
place.
Note that the last step of this procedure is not a c14n step. Good Luck!
:-)
On 27/05/2004, at 17:34, Dittmann Werner wrote:
Raul,
already tried that hack, the problem with that is that
c14n outputs either a byte buffer that is the XML
docu as String or as a node set - this has to be
serialized then deadlock.
Well, I try to ask the WSS guys how they think this
problem c
Raul,
already tried that hack, the problem with that is that
c14n outputs either a byte buffer that is the XML
docu as String or as a node set - this has to be
serialized then deadlock.
Well, I try to ask the WSS guys how they think this
problem can be sloved.
Regards,
Werner
> -Ursprün
> Raul,
> thanks.
>
> However, the element that I create is a top level
> elemen, i.e. an apex node (as far as I understand the
> c14n specs). According to the WSS specs
>
>
> * Finally, employ the canonicalization method specified as a parameter to
> the transform to
> serialize N to produce the
Raul,
thanks.
However, the element that I create is a top level
elemen, i.e. an apex node (as far as I understand the
c14n specs). According to the WSS specs
* Finally, employ the canonicalization method specified as a parameter to the
transform to
serialize N to produce the octet stream outpu
> All,
>
> a question to the c14 gurus on the list.
>
> I set up an Element node and set the default namespace
> to "" using the following code:
>
>elem.setAttributeNS(WSConstants.XMLNS_NS, "xmlns", "");
>
> This seems to work.
>
> The element is c14n'ed using the following code:
>
>XMLUtil
All,
a question to the c14 gurus on the list.
I set up an Element node and set the default namespace
to "" using the following code:
elem.setAttributeNS(WSConstants.XMLNS_NS, "xmlns", "");
This seems to work.
The element is c14n'ed using the following code:
XMLUtils.circumventBug2650(e
>> and what about the sun.misc.BASE64Decoder
>
> And what if you're not on that JDK? The problem with using any other
> decoder, including Xerces', is that not everybody uses those components.
> Until Sun standardizes a BASE64 API in the JDK, there's no good answer.
>
> -- Scott
>
>
What abou
Hi Berin,
thanks
for your response. It works well, now!
To the mentioned
"Id not found" problem, I have read that in C++, the Id attribute
inside the XML file must be exactly like that: "Id="#ToSign">". My error was caused by this issue,
cause I have the "ID" in uppercase mode
Hello,
> Apologies - I should have read all my e-mail before I started replying.
>
np :)
>
> Would your input have had multi-byte characters in it? That would
> explain why you got the error.
yes :) you are right on 100%, i use windows-1251 codepage and multi-byte
chars .
regards,
dech
Apologies - I should have read all my e-mail before I started replying.
Ignore last message on this :>.
You are quite correct - I missed the logic for handling large buffers.
I will update the CVS version this weekend.
On the second problem (detailed below), bytesEaten is a reference that
should
Hello Berin
there are 2 bugs in sorce
i fix them and sent to maillist fixed function
decho
- Original Message -
From: "Berin Lautenbach" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, May 27, 2004 12:10 PM
Subject: Re: decryption ?
> Decho,
>
> No - there shouldn't be (I
Ivan,
Have a look-see at
http://xml.apache.org/security/c/programming.html#simplehmac
The main problem I can see is you are using newSignatureFromDOM which
assumes a DOM Signature structure already exists in the document. You
need to use the "newSignature" method, followed by createBlankSignatur
Decho,
No - there shouldn't be (I'm assuming the C++ library?). The library
uses buffers to process input in chunks, so the size shouldn't matter.
Can you give me some XML that isn't decrypting?
Cheers,
Berin
Nedelcho Stanev wrote:
Hello,
Is there are some limit of size for encripted b
Rude words. I think that was mentioned by someone else some time back.
Thankyou for picking up the reason. I tend to equate bit-wise
operations (unspecified ordering) with logical operations (defined
ordering) and so get caught in this trap.
Thanks! I will fix in CVS this weekend.
Cheers,
15 matches
Mail list logo
