201404222329 23pvg1
inferred encrypted filler
N=4
From the post to its content
As posted (encrypted)
a2a32fc0fc413253c0931e20357dd7d3 3ef21bf54851106bece05501bf7b554a a2ce21bb99c9f6b2eee45273d398b2ed f28176c685c2699b3761b96c0e0fb43d 6dee633ae01fd9f2995280a84f9f7708 aa8b5fbdcf0a240a01715c119218f8c4 36522fc9a08de2d65e0c5712b9c63639 77497dd04056ea1db00856ff67bcdc89 ff786ae03d133d2c
Explanation
- Read the length. 272 hex characters = 64 × 4 + 16, i.e. N = 4 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 160 of Run 62 (seed 507,820,296):
new Random(507820296), Next(0,55) per post. The RNG predicts N = 4; the post has N = 4 ✓. 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.