Congratulations, #afd#
- Thread starter AFoxhoodleDog
- Start date
- Status
you're right... nobody would have figured it out, and we would have had to take the thread down. But since it was figured out almost instantly (you guys are smart cookies) everyone got to experience it for themselves 
We *knew* it was going up, and it still was a shock to even us to see it and read it...
We *knew* it was going up, and it still was a shock to even us to see it and read it... For the non geeky, pass over this please. ACooper, please FW to hubby
Actually it was more complicated than that for a number of reasons. First there no handy way to eval() the output via normal forum inputs... and most everything gets stripped away as it flows through the program execution (both in and out) by various filters. Second is that since all the filters run on both save AND display, even once the proper filter in which to modify the text was found it had to be a 2 pass hack... so that going in it changed from X to Y and then displaying changed from Y to Z. And even then... when and where the filters were used in the forum code was inconsistent. I had to shore up several of the more obvious bypass points before it was even remotely believable. There are still a couple of "exposed surfaces" left as it is (e.g. when you hit reply is showing DemitriousK, and you also see DemitriousK if you've subscribed to the thread to get e-mail updates...)
So: A) find a good filter to put the hack into
Actually it was more complicated than that for a number of reasons. First there no handy way to eval() the output via normal forum inputs... and most everything gets stripped away as it flows through the program execution (both in and out) by various filters. Second is that since all the filters run on both save AND display, even once the proper filter in which to modify the text was found it had to be a 2 pass hack... so that going in it changed from X to Y and then displaying changed from Y to Z. And even then... when and where the filters were used in the forum code was inconsistent. I had to shore up several of the more obvious bypass points before it was even remotely believable. There are still a couple of "exposed surfaces" left as it is (e.g. when you hit reply is showing DemitriousK, and you also see DemitriousK if you've subscribed to the thread to get e-mail updates...)
So: A) find a good filter to put the hack into
EDIT! hubby playing around with php button
and if you were trying to figure it out rather than explain it... Good try, but no cigar
He says it took some tricky work on your part, but I chose to pass on another "geek" session :lol-sign:
EDIT: A big meaty bone just isn't worth it
I like him already
He was actually trying to demonstrate his earlier explanation (BORING) of when I first read the AFD post, and show me it DIDN'T work that way (I ask dumb questions, LOL) but he hit submit instead of preview by mistake.
He says it took some tricky work on your part, but I chose to pass on another "geek" session :lol-sign:
EDIT: A big meaty bone just isn't worth it
He says it took some tricky work on your part, but I chose to pass on another "geek" session :lol-sign:
EDIT: A big meaty bone just isn't worth it
- Status