201512042000 3vhkap
inferred encrypted filler
N=16
From the post to its content
As posted (encrypted)
7acee4172e17138c744330d95e66d340 58f1f9a83b3bd3e8bb6d094d555706fa 27ee12e7cf64623b3d51c8b4e13a2d8c 13e2479903214c3310f71948e5b6b51d 69373804600b0d19272eb8820d28e6ed 2bc1ab87b648f1b77a5703e6e1fa4ee8 bda998fa9cac0fd01d5fcab69220922d ccaf33a85e88e213b0f0a0fc84d79221 b381f2618b3678e7c77832d8367ff676 6f8b9e7d65c766954a7061e7714c814d aef987215d9def637d83a4aeae45c7a8 9550e66f1d09b7e2c68b688aa4afcbe6 b88ee7ba97ec97033074d5bb4397c365 8d535736dceb37154009a4da498d3766 716ce08b1b8f1d8f0d30c4e846bdcd3c a3a0091a6245e0868196dd83c878566f c202288d418c5069cff1341709f2948d a538be88c17119fd270c6b610782bd7b b7f11ff20500bfe7a0276fc324036c83 3279bd328b51378ed0bd3021314791b1 d0eedec481865abf07093f86e9eae997 8f6e28d2122605620fc76374b83b7426 e2ad7a7054a7c86d1c9d45c9a51aafa4 5dbe1cd64224315061fbb3957035c0c4 0ecd31dd3909bcf777d833a35c69b5d1 e65a842c964ff9be7bfd8ab4a618cd41 61f6a9e607a425e2274218fd7137626d 32c52cd18b9c2aef48f0286fb9a5b543 bd804bf4a398660ebedd15185cb6c667 cb177e0c7c99f08b4b3781b3c87f1912 f10139f39b0f0d16caae1cb524167a38 ad66cb9b049c994bfcf4a930e8680b1b 5b6f62b35377b79e
Explanation
- Read the length. 1,040 hex characters = 64 × 16 + 16, i.e. N = 16 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 73 of Run 71 (seed 1,220,915,585):
new Random(1220915585), Next(10,24) per post. The RNG predicts N = 16; the post has N = 16 ✓. The seed is the machine's uptime in ms when the app started (boot 2015-11-17 20:51–21:51). - Conclusion. Filler. Structure and count are explained; the GUIDs are presumed filler like every decrypted post before the cutover.