To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project xml-security has an issue affecting its community integration.
This issue affects
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project xml-security has an issue affecting its community integration.
This issue affects
[EMAIL PROTECTED] wrote:
Hi,
I am trying to verify the following XML digital signature:
http://www.w3.org/2000/09/xmldsig#";
xmlns:C="http://www.routeone.com/namespace.messaging.CreditApplication#";
xmlns:wsse="http://schemas.xmlsoap.org/ws/2002/07/secext";>
http://www.w3.org/2001/10/xml-exc-c
Hi,
I am trying to verify the following XML digital signature:
niQfM6RR1CP+V1Puf9FlaXRNcFQ=
EQjU1zV9WpsCj0+tTJ6pYw4YjM3Ir+OgWsCGijjKGZ1kkNOgWlFkdbDbmb8wzcAaYHVVJrplVpOVC05jd4cX7N9doFDDjRhKobaYUogRErJV86wWpsZ4iP77/DqPy0Egw9laycMv0BxxoWgeW3TQ11EioKiA/sx
I'm looking at an existing problem with some of our code and couldn't
find a definitive answer in the W3C Recommendation. Basically, it's not
clear from the spec how moving a namespace definition affects the
validity of a signature. For instance, if I have:
http://www.wibble.com/CM/envelope";>
Hello all,
xml-security C++:
I'm trying to create an external References within XMLSignature via a
URI specification. The reference should be hashed (and perhaps
transformed). So far, I got local files to work
("file://localhost/file.xxx") as well as files via http that reside
inside our firewal
