Even More DiscoMD5 Nonsense
-
If you want to see it, copy my raw from that post and add an
8
to the end of the hash.But yeah, it made the page just a little bit big...
-
But this has, allegedly, been fixed upstream...
-
But this has, allegedly, been fixed upstream...
"fixed" in that the replacement text is no longer predictable? yes.
fixed as in the exploit is no longer possible? no.
-
Hence "allegedly", my dear fox.
We could all have guessed that it would be disco fixed. Interestingly, I typed that by accident as discofuxed, and it was autocorrected by iPad. Not sure I had it wrong to start with though..
-
...wait, that expands to like 13.5 MB... how the heck did you ever get it to post? I was getting server errors just trying to post a 3 MB post...
-
Yeah because the forum doesn't crash enough. Goddamned you assholes.
Test on your local machines.
-
Honestly?
No idea.
Maybe because the md5 "reflection" was much smaller? Or maybe it compressed really, really well?
500 Internal Server Error
-
can you tone that down a bit?.... Chrome does NOT like.
Chrome doesn't like a bunch of testicles thrown in it's face?
-
Yeah because the forum doesn't crash enough. Goddamned you assholes.
Test on your local machines.
JOKE 1: If the Discodevs don't, why should we?
JOKE 2: If you can think of a way to install Discourse, please let us know
JOKE 3: My local machine doesn't have enough RAM
JOKE 4: (some MD5 string-- probably testicles)
JOKE 5: :moon:
-
who does?
no. it was @sloosecannons's megabytes of the letter
a
-