201410241626 2k6hq1
inferred encrypted filler
N=19
From the post to its content
As posted (encrypted)
f83a124fc82c6e9a5e02f37078bb5b83 8771ce7090fc5f9a1bf908c1f5e4e9a8 d01d4e05e233dba4dbc088e78280769f 2abc3814c8f742253b4e62f3035241b2 76390e7064803cc16a366c78f9f2ec56 2cd96c3dd3b98f55f36d7603b86611ef 1463be232ba13d67f83e85dcc976f2f0 affb05b3c7c6c608de35236f9df417e9 18fd9385345adb9e3823ac41742d2483 df67b63cfe0a8d07e4a2ed2ca9a57152 98bbe59d6b155c1e50104999eae1bfac a1955a1f4a7b354d9d8be8aab069e6a2 b03d9e27126ee1c879715fd5fa707514 bbe9590d139c651a774b9798ebe3b9c9 dff3f558b68a05b1a705e7a1e411ab8e 8e3cccac9735e47417222491b639b4e8 dd3c4c7b282eb9064b4303607411dd56 507505d52ab0efbc402584393ed61c55 c86c37b2fa1071838339b83a2abf117d 33ae03fa526a1a0b2b79fd2c73ec6b7a 2d82e28eccd19d21ef104110395328b8 bfdd734da6839b56157eb1551e388b92 7bcc4d556a3e5879d52d9474690723fd c78613b559f9d0c80f9fa60ae79e8c96 75d9355730c2b424ef44f8262242aa3b 5824a8dec095998f433b298037cf9bdb bcc661d03e63626d1f554a770c49cf48 ed4dc18ef3d5dc8a3cf986fdf3215cc3 adf365e2a2299590861fa6d75628d2cc 309547fe550272e478eb8045f6fc763f c7ba6fc20849d1f7cad0b3fc09baf176 d459afbed166bf5e75c2784e4a6b2d93 8db654762f66345b03a181d9473734c3 780140ea6bc5df42e29c420c0b4a2da4 4162fbf274fb585732388b5b76890bc2 b0e8db7f1ff0c0031135495ec94a28b9 3e7253bbe51772e77bfb050dd0954166 6cdb6d9780d283e4cb2fa9ab6bb85317 227a2568df9f937b
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.