201404201629 23ijwz
inferred encrypted filler
N=17
From the post to its content
As posted (encrypted)
0d217ce8a119e54257593660ec93f8ac f1350bdd390bfff45dc56163e7023a69 74d713d8106034e055bea21f9fb8099c 3577dbe1b926c349dd846b0ad4ca956b 78292ef2f6a98b7176a973ed9c9a966e a9e8b282b7495364d66f50caf87a14fd 70aa5dc128409bf55d94e59ef21d89a0 8f638d1de11398b549f801ce247e6d23 9d4b836edee3131a44964b65f099d195 4eb197eba90bc833354374079cf24e92 bebc6fc6350b38cc00c2ececa5c78256 e81d80165295e2033f915423720f3264 1881c6039690b5f71d8050309e201917 8ac41e820c7f3348e64b35941033f9c6 e1589f69eab2b00d64b2630c34270f78 c94924580a5265bd83cecd6f79a45299 73d06ae599683235dfbb39f449825044 f44d4bc150d020ee5fcf8513417ac5c8 b074e1ff3bd1d37ff6fad76a71ffef82 1b777ade450c94f42fa434c59fe9c19c 696d5c00495741be5cde94807eeff884 f32ebc756e8af0aed6a5c6d044152043 d0af3b6f98bb0632834cfc02b01939b8 9aa8bb3e5ba4a0a52418406a5c6b97f3 bae822efffc9501a3672cd29f9c4d294 d5e275f6d3b1875acfe37b5ed99320a6 08845bb1483dd5916db791ae20238c51 63658b14f156534653cbc25332b988ab 909cb842f3668a10440c2a827da721a4 dd8c016bf8db600a73cfbfec02bffe95 7f3065601248f4228169aacb09f50c7f bf792a86e7fc15102b8618201c44dd59 969d1be155b1ed0eea28a92dfd43473d c440a5c943d9aba9045bef5cdc853d86 c931bb6a175ad1f0
Explanation
- Read the length. 1,104 hex characters = 64 × 17 + 16, i.e. N = 17 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 105 of Run 62 (seed 507,820,296):
new Random(507820296), Next(0,55) per post. The RNG predicts N = 17; the post has N = 17 ✓. 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.