Absolutelly :) Any patches are welcome :) Please note that if you use
CVS then
you need to pull XMLSEC_0_0_X_BRANCH instead of the tip.
Thanks,
Aleksey
Aleksey.
Rich Salz wrote:
Would be be interested in a patch that took the DTD as a command-line
parameter? Yes, I know I can add it, but WS-S
Would be be interested in a patch that took the DTD as a command-line
parameter? Yes, I know I can add it, but WS-Security is about SOAP
messages and SOAP doesn't allow DTD, so any DTD or Schema info has to be
external.
This might not be of general interest -- import DTD from ... -- so I won't
be
There is no way to do it thru xmlsec command line utility.
I believe that you can safely add the DTD declaration to
the signed document because DTD nodes are ignored
by c14n.
Aleksey
Rich Salz wrote:
(No DTD, so no recognization of id attr as an ID)
That makes sense. Any tips on where to hack
(No DTD, so no recognization of id attr as an ID)
That makes sense. Any tips on where to hack into apps/xmlsec so that I
can specifier the DTD on the command line?
tnx.
/r$
___
xmlsec mailing list
[EMAIL PROTECTED]
http://www.aleksey.com/mai
In XML ID attribute has a meaning only if there is a DTD or schema.
Using "#XXX" references w/o schema is meaningless. Actually, you do
not need to load full DTD, you may just specify the DTD for one
particular attribute (see section 3.2 of the FAQ
http://www.aleksey.com/xmlsec/faq.html
for exampl
It looks like it's not finding the ID in the Reference/@URI. Do I
need to load a DTD (hope not...)
This is a WS-Security signature using IBM's XSS4J.
I just used the commandline "xmlsec verify {filename}".
; xmlsec verify xslbench3-xsl.verify-alice.ref
xmlSecTransformStateParseUri (transforms.c
