XML Digital Signature · enveloping tokens · PHP

Sign it, read it, verify it.
Then try to break it.

Every token on this page is created and analyzed by the real ezxmldsig library, running in PHP behind this page. Read each block of the signature, follow the receiver's checks one by one, and replay the attacks that version 1.0.0 refuses.

The keys of demo/certs/ are public: they are published with the library. Never use them, or trust their CA, outside this demo.

Issuer

Signs the user data with sign.key.pem.

Token

Hover or select a block to read what it does.

PHP code of the issuer

Receiver

What it trusts and what it checks.

Trust anchor CA chain caCertPath: the CA certificates trusted, intermediate.cert.pem and root.cert.pem; the certificate of the signer must chain up to them Pinned signer signerCertPath: the token must be signed with this very certificate, sign.cert.pem Expected subject expectedSubject: fields of the subject of the signer's certificate

O, organization OU, organizational unit

Audience Expected audience expectedAudience: who this receiver is

Name

Decryption Recipient's private key crypt.key.pem: decrypts the tokens the issuer encrypted for its certificate, crypt.cert.pem

Expected algorithms

Signature Digest Encryption

Follows the issuer. Change one to see the token refused.

Your checks

Time to live s

Refuse replayed tokens token ids stored server-side

Memory: 0 ids

Verification

The library's checks, then yours.

PHP code of this receiver

05 Attack lab

Forge, wrap, swap, replay.

Each attack starts from the last token of the issuer, alters it on the server, and submits it to the receiver configured above, with a replay memory of its own. No vulnerable code runs here: this is what 1.0.0 does with each forged token.

Sign it, read it, verify it.Then try to break it.

Data read back

Sign it, read it, verify it.
Then try to break it.