Martin Panter added the comment:

Thomas: My check for os.path.devnull was just a half-hearted attempt to check 
for special device names like NUL on Windows. It is far from foolproof, and 
would fail my CON.fusion test that I mentioned above. Anyway, to address this 
specific bug it would be better to keep the changes to a minimum and not add 
any new APIs.

One slight concern I have with Philipp’s patch is the new os_path parameter. I 
am a bit squeamish about adding parameters that are just to help testing. 
Perhaps it is enough to just rely on testing this on Windows, or to 
monkey-patch os.path = ntpath in the test suite? What do others think?

I am posting a modified version (v3) of Philipp’s patch. This version 
monkey-patches os.path in the tests and avoids the os_path parameter. It is 
also stricter, by ignoring any path component that does not appear to be a 
simple file or directory name.

This version will change how some questionable URLs are handled, but I expect 
that all of these URLs won’t have genuine use cases. Let me know if you think 
it is okay or not.

----------
stage:  -> patch review
Added file: http://bugs.python.org/file42352/fix-path-traversal-26657.v3.patch

_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue26657>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

Reply via email to