201405260132 26i1hr
inferred encrypted filler
N=3
From the post to its content
As posted (encrypted)
b9ef63a38f778abfc33a51b8f9b2525a 105c6061d68b9e1693f835c3802c10f3 5b7e1e8878431d6b5dc0e2c34dd5d356 9182e3fe8bc10065c408741f8862a844 3173eff79d91328f9fc9a0a176d96c17 434b9b0664cc711afed40540271f8c78 a4213479d7fc8b9d
Explanation
- Read the length. 208 hex characters = 64 × 3 + 16, i.e. N = 3 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 158 of Run 64 (seed 367,071,562):
new Random(367071562), Next(0,33) per post. The RNG predicts N = 3; the post has N = 3 ✓. The seed is the machine's uptime in ms when the app started (boot 2014-05-15 09:35–10:35). - Conclusion. Filler. Structure and count are explained; the GUIDs are presumed filler like every decrypted post before the cutover.