201410241607 2k6gpy
inferred encrypted filler
N=19
From the post to its content
As posted (encrypted)
d5f7ad0979eed00ded40496f697faa61 f118d4d2ffa9ae6fef69d32a97946a52 8e1330c38f2e41a7461722739c6ddc36 b25b2040de9520a20bc4922c2d265ec0 594c8bf0c6f560ee8dfcfac2f1db179e 3320571fa39cc29ec06b9c21d2d3e284 ccecec6a49cb36ea4da9791537489e4b 4c39a30789ff3763f99e944aa78d5141 f71956e37abfd7f7212df83e72f67604 f9cdc6f5a689451f6ea28c7133f478ff 836d5050114421f5a32f14953aa1e770 45dba5da2a1547cc1d4356513b96c952 43295a0da704da7d6aeb5cb2caef76ec 62e609a45b8421e85aa1da422d1d50c5 e43037e838d912f2b45fdb41609e6f14 e97c0d20c55adc8e707bd76117386a96 633a8facb3b0b8e0e08f4f1dc5b9b34d 8b38d36106afd8cf7208eff83fab6f1e 39278496479a03aa192c27706c86f670 afaf6223baab5abcca83a7f6ada94a32 4eb92a244d077bb23d8c28e8d03e40c1 6d78c6c67b656c2924f532d7ed7ff9d9 f144f739e915722dee02d15b78b89f89 02ee4344da277da395177ce5dc68eae7 16fef07b1388ee842f4831d82a0da34b 079bd1a2a77acaf09f67c8b7fe99b3f7 a067ea31191ee84e8fb55ffec5f6663a 8b8fe3d1080edb3be64a658b4f7059f3 28b1b9d8a8165da09ffa3b46db65b86f f77b1fc835406191a92f91a366b0adb5 4424966658f5477665f7fa86dd67aa58 d6d9a069f2b05eb10525746460755c6c fafaac05527c23f4c697aca449835bf7 f2ef164996aa2ade1a00f7abb9eaf6f1 eefc28ddb1904905bc5e6dd2b4a4c1dd 22b113065c936896c75cfd924b4b1be3 5783db9ec2711ca2f8d2b4316ea749f5 948d65199b460c6e45d4ef68d6f6c18a 2e67200a1af20122
Explanation
- Read the length. 1,232 hex characters = 64 × 19 + 16, i.e. N = 19 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. Part of Fixed N=19 from 2k623r: an app start that posted N = 19 every time.
- Conclusion. Filler. Structure and count are explained; the GUIDs are presumed filler like every decrypted post before the cutover.