201410241704 2k6jl4
inferred encrypted filler
N=19
From the post to its content
As posted (encrypted)
9bb67ca759b5d5b387b2031e0532919c 9883f4dc527ca053b0886ed2c0d9e877 abc9b9830e206197d21df7463a47460c 3a17780d0135f494a16bbcf4346a7d06 7d07d78255f9cf51484e838704ace9f5 d369e5a96045f6a678af5e1d3f8ff067 20bde2a43de1818c3c3aae62d7a13e68 0e7db88f4fae0324d9ca7282c5524631 34d346bae7fa9d71f1a8effa3c2fe1b3 ba591b948e46fe0718bcb09d42439118 cb5afbdcf25b58ce83331a76a20f8037 56cf350bf482d9210091c50d0ee8727f 60edfeab2ab72cacb9fb6691c6d6256d cc98eff1481e799a7e38d26bc596b139 4247b71c6a0a6b30727c009b842e1e18 a248365c8e5fbfd2877a19dd8930190d c4347edf9a3001076a9c7ea556509258 35c98f56d84bf586a14be909b44a3afd 4aa19153010d64c8cd278b49e4065c06 54041a94ead58969234941621836fda6 cfde0a15178499b354d832dcf6518c42 780b492972ee62376009b51d4dd737f6 fcb4ac3337bb6e39bb224bcb13d5f2e2 030a3ca0ade77f5d55687b96cfb941a9 bb21229df03fea705ddf469684bbc915 4b96ff1b356b29785847de23bd372610 42ff68aea6a80879fadb276753fbb97c bcfa5adf83b7569499a5da5306dbb389 407d60f9eef7e2e3ecf271af4926ba1b 5872eaf970898263ee4d77b338382389 72e871f5fb8171d31626e0d086fe6082 d028373fc4950fa1031f10cbb6b6214e 9e315bd54f202d3488161d2f9ff94cb4 e355baf7504ceca116757a112175ea85 3eb03ecd7aada5b8ac20309b9cb974e7 ddb6b9470c63a1e147d3972a34e77cac 976692797d37c38f8de4ca0b69c7d53c 66c25972c32283f06f22b80a95c6627a 751bfa808c2b8815
Explanation
- Read the length. 1,232 hex characters = 64 × 19 + 16, i.e. N = 19 GUIDs encrypted with 3DES plus one 8-byte padding block. Every post-cutover filler post has exactly this shape.
- Key unknown. The post-cutover key (2013-10-16 onwards) has not been found, so the GUIDs themselves cannot be read. Everything else about the post is accounted for.
- Explain the count. Part of Fixed N=19 from 2k623r: an app start that posted N = 19 every time.
- Conclusion. Filler. Structure and count are explained; the GUIDs are presumed filler like every decrypted post before the cutover.