201405261732 26jwoz
inferred encrypted filler
N=6
From the post to its content
As posted (encrypted)
3153a4b7a91aef9195a0d5882278cd19 11d747c38c7b36b065695cfe0bb6b061 32bb915bfce64f2412a91d3d453bd59c 7bf56ff92e520f5a5afc477e11c386a6 4d322a38861d706ea84ff33c3446aab0 f1efbb55207d41cd72277a18df4154ec d388b73de8c25c1cc9ec696e6699562a 1f5e61c0eb4a42f5ff2e2913ac13e6e2 7a206ebe988215ce7f2905b2ca34aa6c e53769919861929ce679c101d463234f ca31e699f06cd889072355b651b86ea7 a02c90a6627288ac315a1488421801e4 f224251285160b1d
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 174 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.