201405231532 26blwt
inferred encrypted filler
N=6
From the post to its content
As posted (encrypted)
32d732682d5eb202056db7719527826e 28801599c3a026a75fd8bf1dd8a108cc 5c8a4d268c3b1fddb5aa4db358c235fd bc9b848d4feee0ccc756f00a4fe4acda fef3f8ed100853dfe8d64c157ac77d58 c9ce4cd95a14a4c9409f09b236cc4c5b 0513dc24bdba9cd5a6d1ca218e7ef701 13b068a9ed2b31405b2e94e7b4ccdef2 fbf2607bd69e0c42eac33f6b10156f15 0d0cf4137ead823c2509ffff3fbb9eb2 8c55854b457b36f18004e8aaa718d81c 5830d4c2a09ff9be8370fbf2fd12da33 e1cdaa03d1307ac1
Explanation
- Read the length. 400 hex characters = 64 × 6 + 16, i.e. N = 6 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 100 of Run 64 (seed 367,071,562):
new Random(367071562), Next(0,33) per post. The RNG predicts N = 6; the post has N = 6 ✓. The seed is the machine's uptime in ms when the app started (boot 2014-05-15 09:35–10:35). - Conclusion. Filler. Structure and count are explained; the GUIDs are presumed filler like every decrypted post before the cutover.