201403260559 21eicd
inferred encrypted filler
N=4
From the post to its content
As posted (encrypted)
c64b4950d47f3550b265d5c3c998590b 7223154b26c1548a4b7ec0f7a13630db 5154d7b5f212caf41b8a702fe8d0fb8c c8c182e887867f25122acc8aee69919b 8d74c1923bb606d769bb20b91848be41 90f8fd053e4e29d5e228af2e749bd983 a30c35f0736ac1c8c1627a24e9859b56 8a23386a6dab323759c84a6103dc0adb 7012e26546c72375
Explanation
- Read the length. 272 hex characters = 64 × 4 + 16, i.e. N = 4 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. This post is draw 166 of Run 60 (seed 19,858,187):
new Random(19858187), Next(0,50) per post. The RNG predicts N = 4; the post has N = 4 ✓. The seed is the machine's uptime in ms when the app started (boot 2014-03-12 08:29–10:29). - Conclusion. Filler. Structure and count are explained; the GUIDs are presumed filler like every decrypted post before the cutover.