Maybe it's RC4 with a constant key or some other stream cipher like that. Wouldn't make a difference, it all winds up being a static XOR anyway.
Show this thread
Random Japanese file format obfuscation no.fivebajillion: "encrypting" the 32-byte file header that contains the subsection offsets and sizes with a constant XOR pad. Rest of the file is plaintext. Subsections are marked by an obvious FOURCC anyway. Who comes up with this stuff?
-
-
-
I'm just going to leave this here: b2393398 a6164f0e 9030fd17 0b4ee0f2 e381571d c17f4b2c a14f1dac 7f009ab6 d7dffe83 97ea45ba a54e8228 6b853fdb 95d8bb6e 4f4d4fe6 ae12e8ff 89079560
Show this thread -
Next up is Yet Another LZSS Variant used in two of the subsections. Conveniently marked with a 'SSZL' header.
Show this thread -
Is there a site cataloguing LZSS variants? I've seen at least two dozen. At some point we've gotta have run out of ways of implementing it, right?
Show this thread
End of conversation
New conversation -
-
-
electrical and mechanic engineers ? they're usually very bad at cryptography
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Management
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
My favourite is a Japanese PC DRM scheme that just appended the to-be-protected executable to the unpacker with a few bytes from the entry point XORed with a publisher-set key
-
...assuming the publisher set one. The default is 0. Yes, they made money off licensing this.
End of conversation
New conversation -
-
-
*Best* homegrown JP archive encryption I've come across: - seed = md5(salt + entry_filename), salt in executable, hard to guess - no two entries ever have same name - initialize mt19937 with seed, use >80 bytes of output as xorpad - plaintext is deflated so also hard to guess
-
Obviously all kinds of wrong in theory but I've wracked my brain about how to break this in practice (i.e. no convenient data or oracle, let alone access to plaintext executable code at which point it's w/e) and couldn't figure it out. Then again, I'm not a cryptographer.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.