201410241645 2k6in1
inferred encrypted filler
N=19
From the post to its content
As posted (encrypted)
6679d109379735c9db8928d7cd87924d 7a11873b107e79bdb5d98fc0064c8571 ff21638f6323e514209f73730c67870d 9d019acf2db70460e89cd228b7181d85 dad8e247250026425f3573e02d7e681e 5abbfc22f3216a6c434a4f27ab99b307 c8d4d0fa7d23f50faa69090f6abc666d cb78fca23fa199a6a9b97fc3b0ddfccb 56c2ff94da1d8c3df0ad085b0dba9815 7a4386f1f37536da7909d0cb367be718 87cc3754a8c271a53319e039b032f071 cfe496bccf034c4b187c3b86eece7b71 9a19d70343f92e42e169b64c098eb3ef 996430106e373af339dbeaafb94c3e55 bca31cc02b6492315886d42968363b03 17711c8bea39fbf52f34f0e7bf010c6e 8181f3f2eab9258d024acd1200030d56 978353824932f9c48c1f66b3e9d942b7 e1a515cfe5d4f483ecf6a08a0317fe81 81f1484f4f2e036946b8ffe9b77c8301 a794dfe21805a95e7b29982939a89ace 860c1ffdf0c3c3756361d8266aaf4838 07a085c578272b7a92b4acfc8d853508 5e273921b8cd51e590d1f5b7a7abb87c 01415d3c379431e93d1bb6082e92f3b8 168a20260f9bd64d667daee6358468b3 ef4804cc33ddf4fd9794932302d36319 dd0ac7f89ca6b42744e4aa27b1554ab0 c6bd855440de40870af0b150265b508a 27ff69e378a6c99055bbcdd915c88b98 eb185e0e7b2ed1f48de559383a34f40e 087f90167e3e9e62cda66510de5d15e5 4eea66592265a730d6683391dde151b4 d455c3938c9ff38092f75e25bfd5379f bd16513ac827885c2548256698e0ae36 1250685dc0b004610e23c9cfde36d411 6106c9e65c631fc972f61c6ea75f2315 e59ff780141bd3afa8ff91a3799765f4 87196c790aeb30e8
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.