To whom it may engage...
This is an automated request, but not an unsolicited one. For help understanding the
request please visit http://jakarta.apache.org/gump/nagged.html, and/or contact [EMAIL
PROTECTED]
Project xml-security has an issue affecting it's community integration. This is
To whom it may engage...
This is an automated request, but not an unsolicited one. For help understanding the
request please visit http://jakarta.apache.org/gump/nagged.html, and/or contact [EMAIL
PROTECTED]
Project xml-security has an issue affecting it's community integration. This is
> For now I've fixed the bug in CVS - probably best to not introduce
> anything majorly new until after 1.1.
Thanks much. I'm hoping to be able to ship the next Shibboleth/OpenSAML
releases with the 1.1 versions of both languages, this will give me
additional incentive. ;-)
-- Scott
Many thanks Berin,
I have to track the validation code again, as it validates a signature that
was produced just a few seconds before, then the XML is written to disk, and
then read in again.
I will let you know about my progress.
Many thanks again
Jozef
-
From: Berin Lautenbach <[
Jozef Aerts - Comp.Chem.Cons. - XML4Pharma wrote:
Dear Berin,
Many thanks.
Does the cascading down HAVE to happen ? Or can it be avoided ?
As I understand it (and maybe someone else can comment here!) - yes it does.
The C++ library bypasses this by keeping a record of the cascaded
namespace attr
Dear Berin,
Many thanks.
Does the cascading down HAVE to happen ? Or can it be avoided ?
If it cannot be avoided, is there a way to "uncascade" it after signing, or
at verification time ?
Unfortunately, the code from "the code below" was missing in your mail.
Could you send it to me ?
Many tha
