#13579: test_executable security risk
---------------------------------------------------------------+------------
Reporter: vbraun | Owner:
mvngu
Type: defect | Status:
needs_work
Priority: blocker | Milestone:
sage-5.4
Component: doctest | Resolution:
Keywords: | Work issues:
Report Upstream: Not yet reported upstream; Will do shortly. | Reviewers:
Volker Braun, Jeroen Demeyer
Authors: Jeroen Demeyer, Volker Braun | Merged in:
Dependencies: | Stopgaps:
---------------------------------------------------------------+------------
Comment (by jdemeyer):
Replying to [comment:41 robertwb]:
> I agree with Volker, we shouldn't be modifying the default behavior for
Python imports to break their spec. A Python program implicitly includes
all sibling .py files. If you place a file in a world- (or group-)
writable location and then execute it, that's your fault.
As I already argued, I totally disagree with this. If the spec is bad
then the spec must be fixed.
I'll report this upstream and see what happens...
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/13579#comment:43>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
