A missing string never got flagged though. When I comment out the
line I call the C line everything worked.
I submitted this as a bug since being the worse kind of exploiter
I love seeing things like this. I'd go gung ho at using
this for malicious activities if I was a hacker.
"Concentrationi
Oh, for me I just moved on to a proper bit of code.
I filed the bug for the perfection of the parser so
it's less exploitable. :)
"I code therefore I am!"
On 1/26/19 8:17 PM, Timo Paulssen via RT wrote:
> I believe the problem comes from `"{"` which actually starts an
> interpolated code block c
A missing string never got flagged though. When I comment out the
line I call the C line everything worked.
I submitted this as a bug since being the worse kind of exploiter
I love seeing things like this. I'd go gung ho at using
this for malicious activities if I was a hacker.
"Concentration
Oh, for me I just moved on to a proper bit of code.
I filed the bug for the perfection of the parser so
it's less exploitable. :)
"I code therefore I am!"
On 1/26/19 8:17 PM, Timo Paulssen via RT wrote:
I believe the problem comes from `"{"` which actually starts an
interpolated code block con
I believe the problem comes from `"{"` which actually starts an
interpolated code block containing a string immediately. That's also why
it doesn't complain about the "else" being in an odd place; it's also
inside the string!
So here's an equivalent piece of code that shows what's wrong:
if reque
I believe the problem comes from `"{"` which actually starts an
interpolated code block containing a string immediately. That's also why
it doesn't complain about the "else" being in an odd place; it's also
inside the string!
So here's an equivalent piece of code that shows what's wrong:
if reque
