201403202359 20yvyg
inferred encrypted filler
N=5
From the post to its content
As posted (encrypted)
649f7317e335f8b81070537a1fd37047 e9c5affaf463638a2fee5e7f41fdb9c1 4dcd66a972a3ae35856a5499c2d72174 6c4c4f02ee1c5b8a1a8082099e60266f b0c05647f38987c1937e24c5bb452adf 9cccb6410ac58aa5d46ec4773ba1fb41 a5743f88478a8ff731a142b6d4834054 4f93d8480554f9811bb33b3d547e7b04 6ca8ef8255e95093a325b69d383e7f1f 7a35ddfc51c625b9ffcce34b06f97f97 4415ce2e105d4447
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 103 of Run 60 (seed 19,858,187):
new Random(19858187), Next(0,50) 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 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.