Colin Britton wrote:
>
> We looked a while ago at building a transformer based on the IBM XML
> security suite, but the licence is a commercial one. It has some good
> features...
>
> Digital signature implementation based on "XML-Signature Syntax and
> Processing&quo
> We could handle it like X/CIncludeTransformers work, letting the
> SignatureTransformer fire up on something like
>
> http://some.external.doc/to/be/sig.ned";>
>
> Algorithm="http://www.w3.org/TR/2001/REC-xml-c14n-20010315"/>
>
>http://www.w3.org/2000/09/xmldsig#sha1"/>
>
We looked a while ago at building a transformer based on the IBM XML
security suite, but the licence is a commercial one. It has some good
features...
Digital signature implementation based on "XML-Signature Syntax and
Processing" by W3C/IETF
XML encryption implementation bas
ication, but I can't claim perfect understanding,
> is that it covers signing any kind of content. Quoting from the
> Introduction:
>
>> XML Signatures can be applied to any digital content (data object),
>> including XML. An XML Signature may be applied to the content of o
that it covers signing any kind of content. Quoting from the Introduction:
> XML Signatures can be applied to any digital content (data object),
> including XML. An XML Signature may be applied to the content of one or
> more resources. Enveloped or enveloping signatures are over data wit
Jason Foster wrote:
> Now that the W3 has recommended xml-signature, does it make sense to
> try and figure out how to incorporate it into the Cocoon pipeline model?
> I've put a (very) little thought into this and I'm not sure what
> approach makes the most sense. For d
Just to toss an idea out into the fray...
Now that the W3 has recommended xml-signature, does it make sense to try
and figure out how to incorporate it into the Cocoon pipeline model?
I've put a (very) little thought into this and I'm not sure what approach
makes the most s
