201406062359 27icpg
inferred encrypted filler
N=6
From the post to its content
As posted (encrypted)
6854792810779bd6ca2f8a5054ea7e06 dc0b9bfc3f12983d082c10d9dab4d1f6 36766af1d2772d8efff0425cc7aa64b7 84fe1f60555f9aed171a17c4ab98a214 804fa3f8c417f1777d768d29a4691311 58785c2a77d5801445afb94c1bf955c8 dc0fabf63657c803829a82409fa82ce7 a9f9318464d37e2f6655b3805342a19f 99977dcfb12d5a71292dae55b0092583 7dba421b6ba4ce8cc4b1190e9ac7cc67 f0bf3194d3f415dbab578a48128c6c79 b0d2025e5fa2b9bbc5481b709a549ad8 03168a29a0a28db9
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 51 of Run 65 (seed 1,582,093,843):
new Random(1582093843), Next(0,22) 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:31–11:31). - Conclusion. Filler. Structure and count are explained; the GUIDs are presumed filler like every decrypted post before the cutover.