4 XML cryptographic libraries
All Application Manual Name SummaryHelp

  • Documentation
    • Reference manual
    • Packages
      • SWI-Prolog SSL Interface
        • XML cryptographic libraries
          • library(saml): SAML Authentication
          • library(xmlenc): XML encryption library
          • library(xmldsig): XML Digital signature
            • xmld_signed_DOM/3
            • xmld_verify_signature/4

4.3 library(xmldsig): XML Digital signature

See also
- http://www.di-mgt.com.au/xmldsig.html
- https://www.bmt-online.org/geekisms/RSA_verify
- http://stackoverflow.com/questions/5576777/whats-the-difference-between-nid-sha-and-nid-sha1-in-openssl

This library deals with XMLDSIG, RSA signed XML documents.

[det]xmld_signed_DOM(+DOM, -SignedDOM, +Options)
Translate an XML DOM structure in a signed version. Options:
key_file(+File)
File holding the private key needed to sign
key_password(+Password)
String holding the password to op the private key.

The SignedDOM must be emitted using xml_write/3 or xml_write_canonical/3. If xml_write/3 is used, the option layout(false) is needed to avoid changing the layout of the SignedInfo element and the signed DOM, which will cause the signature to be invalid.

[det]xmld_verify_signature(+DOM, +SignatureDOM, -Certificate, +Options)
Confirm that an ds:Signature element contains a valid signature. Certificate is bound to the certificate that appears in the element if the signature is valid. It is up to the caller to determine if the certificate is trusted or not. Raises an exception if the signature is not valid.

DOM is the complete document. Each ds:Reference must refer to exactly one element of DOM with an ID, Id or id attribute that has the referenced value. Options:

references(-Elements)
Unify Elements with the list of elements (in DOM) whose content is protected by the signature. It is the responsibility of the caller to verify that these are the elements it uses. Notably when verifying a SAML message, the content used must be (part of) one of these elements to avoid signature wrapping attacks.
weak_algorithms(+Boolean)
If true (default false), accept the SHA1 and MD5 based signature and digest algorithms.

Note: The DOM and SignatureDOM must have been obtained using the load_structure/3 option keep_prefix(true) otherwise it is impossible to generate an identical document for checking the signature. See also xml_write_canonical/3.