201508262201 3ijnep
inferred encrypted filler
N=6
From the post to its content
As posted (encrypted)
9af656b5da0744a573ca038a58fd6140 22cdc87b59660cf519c2dd09a64de432 a46ec2f11077c2313f86102281f7f8d6 ecd63caa854a268386b475f876d4d84c 68bbc447be1f4b2f18fc1dc43ac8e9a2 701c6ec687ac5d21039a71e661c49585 046320bf41414baba3487544b0506c05 e9872fadcec7b8b773e4d320976460a3 64ef1bd35ec1abcbe2d0ea5cf5cf1818 68717343df6a16a40731aa8f57fd5f5c 2d4f2b1814d1c9b227545d8eb12caa7f 1ccd520dd44ab9f0282bce1964c4dc31 1ed352a9b6373076
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 17 of Run 68 (seed 316,235,227):
new Random(316235227), Next(0,22) +2 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 2015-08-22 00:11–02:11). - Conclusion. Filler. Structure and count are explained; the GUIDs are presumed filler like every decrypted post before the cutover.