201312300632 1u0czi
inferred encrypted filler
N=5
From the post to its content
As posted (encrypted)
c1b1f9523853c56bced46f35b9ed1dae 5ffc126539339e49bd47716a386fbf67 146e5e3d225c5352444b8dc191a32ef9 aeeaff7ec38a1b85c93ea4cd453d658b 1340e16b866ab0056fa01ce97599baa2 5e53074c64ec4fbab39eb5ed78e6acf5 dda355ae444a19b4966833fc7defc395 63a089b1a70eb0787a8c61aefd89ae25 0070110588344450db874b1131d448c3 8db53d29cc9752bde980e406e249e98c 639279d4a04c7c47
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 97 of Run 56 (seed 561,089,375):
new Random(561089375), Next(0,98) 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 2013-12-11 20:41–23:41). - Conclusion. Filler. Structure and count are explained; the GUIDs are presumed filler like every decrypted post before the cutover.