Changes between Version 2 and Version 3 of T12_Security/WS-Security


Ignore:
Timestamp:
16/08/06 16:04:31 (13 years ago)
Author:
pjkersha
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • T12_Security/WS-Security

    v2 v3  
    1717 
    1818== XML Signature == 
    19 pyGridWare uses sha package for digest generation and M2Crypto for signing.  A DOM based canonicalisation algorithm has been added to ZSI.  This get a mention on a Python mailing list from May 2002: http://mail.python.org/pipermail/xml-sig/2001-May/005462.html 
     19pyGridWare uses sha package for digest generation and M2Crypto for signing.  A DOM based canonicalisation algorithm has been added to ZSI (SZI.wstools.c14n).  This gets a mention on a Python mailing list from May 2002: http://mail.python.org/pipermail/xml-sig/2001-May/005462.html 
    2020 
    2121=== Custom Signature Code === 
    2222Objective: emulate digital signature using the above and validate against pyXMLSec Version. 
    2323 
    24 pyXMLSec has been used in NDG up until now with enveloped signature e.g. for signed Attribute Certificates.  For WS-Security we need to be able to use a reference instead, set to the particular part of the SAOP message body to be signed. 
     24pyXMLSec has been used in NDG up until now with enveloped signature e.g. for signed Attribute Certificates.  For WS-Security we need to be able to use a reference instead, set to the particular part of the SOAP message body to be signed. 
    2525 
    2626== XML Encryption == 
     27Tackle digital signature first :)