test/test_mails/memoryhole_mails_README
changeset 1269 95e8c36adf13
     1.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
     1.2 +++ b/test/test_mails/memoryhole_mails_README	Wed Oct 12 15:33:55 2016 +0200
     1.3 @@ -0,0 +1,115 @@
     1.4 +The memoryhole mails here correspond to the memoryhole corpus at http://modernpgp.org/memoryhole/corpus/ and should be used for checking memoryhole compliance. (Also, they're a way to reverse engineer empty parts of the spec). These are part of the examples specification guidance and are included for the repository for testing purposes only. The actual emails have been extracted and are in memoryhole_[A-H].eml in this directory.
     1.5 +
     1.6 +Some of these will have to be changed by us to have keys we can actually use to decrypt the contents for testing, but the descriptions below of those emails tell us what they should contain:
     1.7 +
     1.8 +Contents
     1.9 +
    1.10 +    A: alternative text/html message with embedded header, signed
    1.11 +    B: alternative text/html message with embedded header, unsigned
    1.12 +    C: alternative text/html message with embedded header, signed, with Subject tampered
    1.13 +    D: alternative text/html message with embedded header, encrypted+unsigned
    1.14 +    E: alternative text/html message with embedded header, encrypted+signed
    1.15 +    F: headers in top-level MIME object: signed plaintext email
    1.16 +    G: headers in top-level MIME object: signed multipart email
    1.17 +    H: headers in top-level MIME: tampered subject and from
    1.18 +
    1.19 +Email A:
    1.20 +
    1.21 +alternative text/html message with embedded header, signed
    1.22 +
    1.23 +└┬╴multipart/signed 1711 bytes (Subject: alternative text/html message with embedded header, signed)
    1.24 + ├┬╴multipart/mixed 827 bytes
    1.25 + │├─╴text/rfc822-headers attachment 205 bytes
    1.26 + │└┬╴multipart/alternative 450 bytes
    1.27 + │ ├─╴text/plain 86 bytes
    1.28 + │ └─╴text/html 202 bytes
    1.29 + └─╴application/pgp-signature 455 bytes
    1.30 +
    1.31 +
    1.32 +Email B:
    1.33 +
    1.34 +alternative text/html message with embedded header, unsigned
    1.35 +
    1.36 +└┬╴multipart/mixed 1036 bytes (Subject: alternative text/html message with embedded header, unsigned)
    1.37 + ├─╴text/rfc822-headers attachment 207 bytes
    1.38 + └┬╴multipart/alternative 450 bytes
    1.39 +  ├─╴text/plain 86 bytes
    1.40 +  └─╴text/html 202 bytes
    1.41 +
    1.42 +
    1.43 +Email C:
    1.44 +
    1.45 +alternative text/html message with embedded header, signed, with Subject tampered
    1.46 +
    1.47 +└┬╴multipart/signed 1706 bytes (Subject: the subject has been tampered!)
    1.48 + ├┬╴multipart/mixed 850 bytes
    1.49 + │├─╴text/rfc822-headers attachment 228 bytes
    1.50 + │└┬╴multipart/alternative 450 bytes
    1.51 + │ ├─╴text/plain 86 bytes
    1.52 + │ └─╴text/html 202 bytes
    1.53 + └─╴application/pgp-signature 455 bytes
    1.54 +
    1.55 +
    1.56 +Email D:
    1.57 +
    1.58 +alternative text/html message with embedded header, encrypted+unsigned
    1.59 +
    1.60 +└┬╴multipart/encrypted 2496 bytes (Subject: Memory Hole Encrypted Message)
    1.61 + ├─╴application/pgp-encrypted 10 bytes
    1.62 + └─╴application/octet-stream 2064 bytes
    1.63 +
    1.64 +
    1.65 +Email E:
    1.66 +
    1.67 +alternative text/html message with embedded header, encrypted+signed
    1.68 +
    1.69 +└┬╴multipart/encrypted 2903 bytes (Subject: Memory Hole Encrypted Message)
    1.70 + ├─╴application/pgp-encrypted 10 bytes
    1.71 + └─╴application/octet-stream 2471 bytes
    1.72 +
    1.73 +
    1.74 +Email F:
    1.75 +
    1.76 +headers in top-level MIME object: signed plaintext email
    1.77 +
    1.78 +This message demonstrates including the memoryhole headers inside the
    1.79 +top-level MIME object. The signed Subject and From are headers of the
    1.80 +text/plain part, rather than having their own rfc822-headers part.
    1.81 +
    1.82 +└┬╴multipart/signed 1242 bytes (Subject: headers in top-level MIME object: signed plaintext email)
    1.83 + ├─╴text/plain 207 bytes (Subject: headers in top-level MIME object: signed plaintext email)
    1.84 + └─╴application/pgp-signature 455 bytes
    1.85 +
    1.86 +
    1.87 +Email G:
    1.88 +
    1.89 +headers in top-level MIME object: signed multipart email
    1.90 +
    1.91 +This message demonstrates including the memoryhole headers inside the
    1.92 +top-level MIME object. The signed Subject and From are headers of the
    1.93 +multipart/alternative part, rather than having their own
    1.94 +rfc822-headers part.
    1.95 +
    1.96 +└┬╴multipart/signed 1566 bytes (Subject: headers in top-level MIME object: signed multipart email)
    1.97 + ├┬╴multipart/alternative 684 bytes (Subject: headers in top-level MIME object: signed multipart email)
    1.98 + │├─╴text/plain 218 bytes
    1.99 + │└─╴text/html 202 bytes
   1.100 + └─╴application/pgp-signature 455 bytes
   1.101 +
   1.102 +
   1.103 +Email H:
   1.104 +
   1.105 +headers in top-level MIME: tampered subject and from
   1.106 +
   1.107 +This email demonstrates including the memoryhole headers inside the
   1.108 +top-level MIME object. The signed Subject and From are headers of the
   1.109 +text/plain part, rather than having their own rfc822-headers part.
   1.110 +
   1.111 +This email has been tampered with. It was originally sent by Winston,
   1.112 +who signed the body (including the memoryhole headers). Eve has
   1.113 +fiddled with the From and Subject headers in-flight.
   1.114 +
   1.115 +└┬╴multipart/signed 1416 bytes (Subject: headers in top-level MIME: tampered subject and from)
   1.116 + ├─╴text/plain 393 bytes (Subject: headers in top-level MIME: subject restored to original)
   1.117 + └─╴application/pgp-signature 455 bytes
   1.118 +