201410241510 2k6dow
inferred encrypted filler
N=19
From the post to its content
As posted (encrypted)
facd785d228834d65dba2507ac0df23b 26ffd83c31dc384887f34e1f07352a0d 550cfa769a12effcf13b7997ee8d79f7 70afb36b5b86cdaf82b6f83ea261a0c6 dde22f93958727ccbbabd1a0a1c8baae 6fdf04081bb5cddcaa9e067be3d22f1d ff0d48d619d2ff129dd6c02fbe26b805 ef987fadab2aa951f82880f9e13f38e3 878b5a2c650c959c89f24110bde376cd c203193c36ea53f9d25423fa527ebf58 99e2db870f0fed4fb84937b902f1996a d40829b1f3d5e72d47d02cdd06316101 d3de1c0a64c0a9eb8342d9df58af1bcd 70e41a61cafdb55d0e2f96b3b1e52ec9 7dea050e00f31992570d35fe0de1dbdb c1f5118dfd11f98b2244ff7305e771f0 528a2f5815f7d0b9acb4f8533f265782 8f25edf4dcc10934a163a2d4b9952848 422efec20b15d03354291db82066a246 139c7c34a3da97cbe034a20accafcd5e 64fdd3e3d367ca4c0ac9ed6a578478bd a3c433945f796ab78758b26ab627dbfe ef3bb767ad1f5e1dfb30667a4d48d0b0 de1720293610fef6cef774202352cf30 168019e579a9a93c04915ecaa9b2a1ac fc96d1f73e92efc4774c029e5f43032e 0407279bd0534a36b1ceca27898b96e1 bc1532759a8c274cc4385583b4667da2 0632bf87c17622a0a0d8cf2e4bff07c9 783ed298c5525483788373eba618173d 59fb27885f6630bd23197c1d69079c79 ef19ccf58eaf92ba8d8052dac060f1ce f04ffd71dd5e4bce6818296cc082bc2f 6a1fbde9bf144200454e92d7a3417338 71effd31fb2034471bd9df49004a20eb ac75365e9346644b8ab582e118c08dcd d5ffd3e83ce4aae89c54cfb2f27ebbe3 a4f54f4173933faa6d47c02d7041d055 145d023fbd33281e
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.