[issue21515] Use Linux O_TMPFILE flag in tempfile.TemporaryFile?
STINNER Victor
report at bugs.python.org
Fri May 16 11:47:35 CEST 2014
STINNER Victor added the comment:
"I don't think we can use this by default, or it will break the expected semantics of temporary files under Unix (visible by other processes)."
I proposed to change TemporaryFile, not NamedTemporaryFile. Do you mean that other processes are supposed to have access to the temporary file descriptor? Access through /proc/pid/fd/<tmp_fd>?
O_TMPFILE should increase the security because there is no more race condition between os.open() and os.unlink() (window where an attack can access the file).
My patch uses O_EXCL. It makes possible to use linkat() to create a path for the temporary file (I didn't try it, but I read that it's possible). I don't know if using O_EXCL should be the default.
----------
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue21515>
_______________________________________
More information about the Python-bugs-list
mailing list