201403280559 21kynb
inferred encrypted filler
N=6
From the post to its content
As posted (encrypted)
0dc51030f1841be84751c5d8371c5b31 79bb8c4948e2bb15041c262fbb7454b1 bb4311755e96a0ec9cf878fb6211ae84 3fcc5c924d6260a88419c4374a777d51 d82e04d3f706e01ce7cf3c3067f36574 6d26e27324c6a49b02ac1f400c695c5e c7024ff69d8339c1c77f55fa771e2cf5 0c45fa906deebc76ab01b53d53d6e82c 4c5f1425b02aade1c0d35d63a548060a f3ffd516a3591fe612d3efb6e44510e2 c208b385ce738eab9c05eaf597771b45 951fed981ed162f8c27161a59c769461 f967606f113a18c4
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 190 of Run 60 (seed 19,858,187):
new Random(19858187), Next(0,50) 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-03-12 08:29–10:29). - Conclusion. Filler. Structure and count are explained; the GUIDs are presumed filler like every decrypted post before the cutover.