201403280759 21l42o
inferred encrypted filler
N=6
From the post to its content
As posted (encrypted)
8ee3321e08c4ee6c68097a3d6f9beece b10dd080f31d113495b2e2998b508a97 f4be36427c028c6c3f8c68168c829f71 b3694e7282164893ad26c30443d1ee01 ae28686947dd446f9f779b82662c7bf5 31a3af987102f976b22cb638058349ca 0f7e17685fd0fa030d42fb304ff760fe c3d4b906d62e1d683deb746237221412 11beb564a9a0e2467c744b912f7f77dd 9b5ef0d79651dfeb017c377047f6c7a3 66b34aded5e058ac557caa44f1b0bf31 0d47bc6859d79c242a7a37d4bb113d62 82317f218f27843e
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 191 of Run 60 (seed 19,858,187):
new Random(19858187), Next(0,50) 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-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.