Am 19.03.19 um 17:23 schrieb Giampaolo Rodola': > @Sebastian >> If there are valid use cases for mktemp(), I recommend renaming >> it to mkname_unsafe() or something equally obvious. > I'm -1 about adding an alias (there should be one and preferably only > one way to do it). Also mkstemp() and mkdtemp() are somewhat poorly > named IMO, but I wouldn't add an alias for them either. > Just to clarify: I was not suggesting creating an alias, I was suggesting renaming the function, but keeping the old name for a normal deprecation cycle. But I had another thought: If I understand correctly, the exploitability of mktemp() relies on the fact that between determining whether the file exists and creation an attacker can create the file themselves. Couldn't this problem be solved by generating a filename of sufficient length using the secrets module? This way the filename should be "unguessable" and safe. - Sebastian
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4