201410241316 2k66jj
inferred encrypted filler
N=19
From the post to its content
As posted (encrypted)
a979e2f47d561e366a4f9576a2604429 ddc680345fd2cf2f380e00f1ae4a490b 01db3ebba0085ec9225756ec12cba8b2 c0ffef9ea29e397564e4e66979d5cc6d 8f0fbc5418f65647904407dbcb864a0c 3a9553f13d680ca8a4b43881ae708e4a 6342858924df6c29b07fbc09ccab8b80 18bec63c133b40b20535ad50208f138a 10dc1dc70407d2d5a756cf79579a03f0 1c1bbfb74c65270bf0012fbe1d209af9 4ca713036b6203cc8a6ae488bae72a41 52bbb3553e26c33de53ce3b2a478949c 1eef700558e647e0db2f1513836aa26d 93eecd5e59ee854e08e97e589fdda9b1 26ea9200dd934ec45a15de2e0cbd4248 6df556006061bdd9c7450ffb61da39f8 6f03bf0ac2be8e980983c23d8538c651 7f892e180622b66ed11b1352df7d85e8 21a920fe9d7b04eec2013b31dc498a66 83f3cb43487f92c9a7500d2f5b5dad19 4b464b7056316efce66d91dbf5060634 98a23687a71f9b270d435412c820826b b7ad2ad63e8b344eeb45b7cc00fa398d 9117f3bdac2b0b6a92a1e372e2ae431d 05bb82b712cca59f14bf6b4d61410c6b f5ee5fd5fd215276e84fce984e67f5cd bc548578503bae1b14562897de7c3fb1 e1b2ff11a8006376c7cd310bd36d2985 d892fdbae5ce58100dc3800c8eb96f17 3f47f99b7c1620e8c0cecc4921e5d824 0f5da9bf70eb494106919d7d3bc5d7d5 1f7d7946f3afc355424f449f65eab07e 9dec1371cda4328db6d467bbaa5a7021 0fa50bf702083fb998e4faf1c6977dad 7bdf51b19b753d501c540b3434d1a0d8 171e6dbedcb671230690a5329a59f9f0 0235cd4547feec32d2e51159ebc91e53 2b63ba589b4ba822f8a0f8f9b4822129 97221880311e0b10
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.