201405150416 25lcpl
inferred encrypted filler
N=6
From the post to its content
As posted (encrypted)
294c8a3674a2429182d0567046981f13 7ed0535acfd78eedbd46c777537998e8 e941436b758ca905a0038ca0f6eb7e42 5e46037cf236e2d048d1b79cd65f751a a21e78e09abc99c37f0ce865c2e63f9a cc36dadf6c4b694163c632679da54c02 2920ecc1339bb4965337dcc2c72fdac5 e96926bb36589433e52ab72c04d1eabe 86f6ea3c6511886bf85e918f7accb484 c0e99d9219894e7c6b0fbace4a860d68 bf3f1e4c897a6a5390f899bbd7b1ead0 49de1cebf610db51b8ce29369f59c933 72eaf94d65cc3dbb
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 52 of Run 63 (seed 1,506,676,046):
new Random(1506676046), Next(0,33) 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 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.