201405140153 25hsuk
inferred encrypted filler
N=7
From the post to its content
As posted (encrypted)
66047eea616b3a93e33571c59cdc10bb 792e3166a138a0b2ef6e4aaafe4ff43e 1dc41f8b20aca5ef757dfac72aa3f7d0 829e890a5463d05b72f72ee8050f8fac bb4e65f0aa00f7768314aa9770991421 f43c7b549b029720fa7f2a5112c5b84b eca4897979b73fe5b4862bfd281fecf2 1e9f4b8ebbacd90c2894b46fee38c45b 42cb32de8afc5aa0c1fbc257ffca8287 11d0a53970a0701ba3ad3b7e8e3b07d5 cbd504ac347df77191bd7f26df1b3ac1 1f3bcd9560f1d8f653051c26ff2a8620 52a9b35064f20b1b8a83e3f4d84e3dec 181b3a3e253ca9d17f11f93f2ccc282d 49d4e7b28f6db02b
Explanation
- Read the length. 464 hex characters = 64 × 7 + 16, i.e. N = 7 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 28 of Run 63 (seed 1,506,676,046):
new Random(1506676046), Next(0,33) per post. The RNG predicts N = 7; the post has N = 7 ✓. The seed is the machine's uptime in ms when the app started (boot F 2014-04-10 10:33–11:39). - Conclusion. Filler. Structure and count are explained; the GUIDs are presumed filler like every decrypted post before the cutover.