201403242159 21abo5
inferred encrypted filler
N=6
From the post to its content
As posted (encrypted)
35be95d8302fa6362963914e60119886 78349a1cf498a3091e7ad22be7c83c01 610b22ba02f2bfe0faf6f57a013d07cc e03167326fa3c668f3f0725b7b3b0153 ffda65cf8afd589ad07bb9d5b623d68a 93f5585892985b4e23006f990085a249 67e9fc2be3267f3600c158b3939f203a eede80a56c20a7d25db46c9829d79084 57c28678a90b119965ce96d7768daf15 e4f6314bdaa7e7f1b917bad12457aea0 d5aa42db31807006600f47676ebb3417 36c409be4fcca0005483a8ae5b91c969 b4f6dcabe0f33ea3
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 150 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.