[issue25288] readline.py file in current directory caused unexpected code execution.

Akira Li added the comment: python3 -I could be used as a workaround. -- nosy: +akira ___ Python tracker ___ ___ Python-bugs-list mai

[issue25288] readline.py file in current directory caused unexpected code execution.

Hiroki Kiyohara added the comment: I see. Thank you very much, guys. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsub

[issue25288] readline.py file in current directory caused unexpected code execution.

R. David Murray added the comment: Well, so much for my memory :(. The actual discussion was in issue 12238, where *my* conclusion was that this should be fixed (readline should be special cased), but the issue is still open. Patches welcome :) -- resolution: -> duplicate stage: ->

[issue25288] readline.py file in current directory caused unexpected code execution.

R. David Murray added the comment: This is not a bug, this is the way python works. When running in interactive mode (only) the current directory is first on the path. Now, should this behavior be changed? I think we've discussed this before and decided not to change it (for backward compati

[issue25288] readline.py file in current directory caused unexpected code execution.

Xiang Zhang added the comment: I can reproduce this action on Ubuntu. The forged readline.py in python's execution directory can steal the permission of python and do something dangerous. -- nosy: +xiang.zhang ___ Python tracker

[issue25288] readline.py file in current directory caused unexpected code execution.

New submission from Hiroki Kiyohara: Running `python` interpreter will import `readline.py` file in current directory. It causes unexpected code execution. This problem is reported by 'Japan Vulnerability Notes' as a bug on Windows version Python http://jvn.jp/jp/JVN49503705/ It says that when