On Thu, Mar 5, 2015 at 12:39 AM, Dave Farrance
wrote:
> Ben Finney wrote:
>
>>Chris Angelico writes:
>>
>>> import base64; exec(…)
>>
>>That's all I need to know. Code with ‘exec()’ calls, I consider unsafe
>>by default.
>
> Indeed. replacing exec with print...
>
print(base64.b64decode(b"eD
On Thu, Mar 5, 2015 at 5:44 PM, Ben Finney wrote:
> Chris Angelico writes:
>
>> import base64; exec(…)
>
> That's all I need to know. Code with ‘exec()’ calls, I consider unsafe
> by default.
Well yes, there is that :)
ChrisA
--
https://mail.python.org/mailman/listinfo/python-list
Ben Finney wrote:
>Chris Angelico writes:
>
>> import base64; exec(…)
>
>That's all I need to know. Code with ‘exec()’ calls, I consider unsafe
>by default.
Indeed. replacing exec with print...
>>> print(base64.b64decode(b"eD0neD0lcjsgZXhlYyh4JSV4KSc7IGV4ZWMoeCV4KQ=="))
x='x=%r; exec(x%%x)'; e
Chris Angelico writes:
> import base64; exec(…)
That's all I need to know. Code with ‘exec()’ calls, I consider unsafe
by default.
--
\ Lucifer: “Just sign the Contract, sir, and the Piano is yours.” |
`\ Ray: “Sheesh! This is long! Mind if I sign it now and read it |
_o__)
import base64;
exec(base64.b64decode(b"eD0neD0lcjsgZXhlYyh4JSV4KSc7IGV4ZWMoeCV4KQ=="))
Or do, but don't blame me if Python crashes out badly. It seems Py3 is
safer than Py2 here.
ChrisA
--
https://mail.python.org/mailman/listinfo/python-list
