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" by W3C/IETF
> XML encryption i
> 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"/>
>
ED]>
To: <[EMAIL PROTECTED]>
Sent: Sunday, February 17, 2002 8:29 AM
Subject: Re: xml-signature
> 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
Jason Foster wrote:
>> What about a SigningTransformer and a VerifyingTransformer ? The
>> SigningTransformer would then sign the referenced portions as the
>> last transformer in a pipeline; the VerifyingTransformer would check
>> the signatures as the first transformer, either passing the co
> What about a SigningTransformer and a VerifyingTransformer ? The
> SigningTransformer would then sign the referenced portions as the last
> transformer in a pipeline; the VerifyingTransformer would check the
> signatures as the first transformer, either passing the correct content
> through
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 documents serialized as
