201404090820 22lruz
inferred encrypted filler
N=5
From the post to its content
As posted (encrypted)
60d5d155549fe68bd868ebc9501a7631 b488648ceaf73274d28a73980c5f0d03 8b233c76fe30a7aa57183505c8a2e833 bd7096d7b5d134cdc308230bec5e536e 80f33c14bbeb99fa6799bcec9144172c b960eb50477a3442132721c95e0fb015 7c9b2e9358fb5c6a24adba3aa5c084f7 142568c6852ed3da56860584b22581b3 bd1337e45b000f33e7600dab30adb9ed e97e3baf6a5db55be231dec3d45ae017 24b89e579c6cf4ce
Explanation
- Read the length. 336 hex characters = 64 × 5 + 16, i.e. N = 5 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 38 of Run 61 (seed 2,007,067,968):
new Random(2007067968), Next(0,20) per post. The RNG predicts N = 5; the post has N = 5 ✓. The seed is the machine's uptime in ms when the app started (boot F 2014-03-12 08:00–09:06). - Conclusion. Filler. Structure and count are explained; the GUIDs are presumed filler like every decrypted post before the cutover.