201404180330 23bpmz
inferred encrypted filler
N=6
From the post to its content
As posted (encrypted)
c1fe003595c5f27866b2b0515b03633c 09e87e2c6e8c7d5518f8689d5ca8aa97 4d3982bc30c78e64021ed6512d20e173 541ac637867a577c1b3bbe2e3da097a3 bdbe0ad796e23a95039ae6f23b9a404b 2460f03f658051cc8f315ab68718f59a ea9206064d471b52d5b503dd47173e84 8d20492de2d021ecc92ff95da781e1eb 89440d061e69c5aefabcbac05dc9b5c7 d6c8a4b9117b2a456ae86f7cc88acacd 78ea53cdf14c45a17ffcd5ce1eff7ed1 1c07f6f9b17b8746c794a14cb21bfc13 e6110115da5b9987
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 44 of Run 62 (seed 507,820,296):
new Random(507820296), Next(0,55) 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-04-10 09:27–10:27). - Conclusion. Filler. Structure and count are explained; the GUIDs are presumed filler like every decrypted post before the cutover.