201404100513 22okz2
inferred encrypted filler
N=5
From the post to its content
As posted (encrypted)
41cd6e70ff2f1fb0a283135e2183bac6 eaca9a4ed44538a65988ee7ebe2f8cf8 9e8ab2dd527715ce78ea969628c0463b 0410946defc3ebcf0436ee0a49c61db3 f628355e0ed2f0f7fd19e4b9af527081 0c40661e89d85d720635acb26564cc51 89631c854545a5b3957c03df328cb15e 3c8bfa5572d23b522afad1edfb5ad28c 8905ee56b96e3d9fb5903c737c28e316 0562780b4710bd85b27b158c90d297d3 356260ac1c4cd1ab
Explanation
- Read the length. 336 hex characters = 64 × 5 + 16, i.e. N = 5 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 57 of Run 61 (seed 2,007,067,968):
new Random(2007067968), Next(0,20) per post. The RNG predicts N = 5; the post has N = 5 ✓. The seed is the machine's uptime in ms when the app started (boot F 2014-03-12 08:00–09:06). - Conclusion. Filler. Structure and count are explained; the GUIDs are presumed filler like every decrypted post before the cutover.