201406051959 27elor
inferred encrypted filler
N=6
From the post to its content
As posted (encrypted)
19b0c875c68b8244ab6b83e6bfd40b0c 99df5d8efefa6d3b0e557e963efb893d 1b560b4a3faadbf0eac0d3e811e024f3 dac8effe1bdd7687881061e1ea61eac7 694be06df67a0568e69ffd5ae7d99905 e493a228fef9869fb719c995e015feae 22671d94021239b8ea2f4a73d9cbefa5 dc5271aa9a54cc1c90ca906e2bf0a9de 4f8c7869f3f0038f5b909f7d0193d81f 21869906b95b51bde93b39612538f5a6 67c4cf284505bbbdf35e48d8ae1d2cc4 7dc6f75c986387a1aefd2725c5209393 c0f9942d4d568de8
Explanation
- Read the length. 400 hex characters = 64 × 6 + 16, i.e. N = 6 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 37 of Run 65 (seed 1,582,093,843):
new Random(1582093843), Next(0,22) per post. The RNG predicts N = 6; the post has N = 6 ✓. The seed is the machine's uptime in ms when the app started (boot 2014-05-15 09:31–11:31). - Conclusion. Filler. Structure and count are explained; the GUIDs are presumed filler like every decrypted post before the cutover.