Skip to content

Conversation

thestinger
Copy link
Contributor

I can't really think of a use case for a randomized directory name which other users have read/write permissions on. If there is some edge case, it can be dealt with by doing a chmod after the fact (but you can't do the security retroactively).

Closes #2349.

This removes the FIXME suggesting that mkdtemp should rely on the
default umask, because that would make it unusable for making a secure
work area in a world writable directory (have to assume that other users
have created files, directories, hard links, etc. in your directory).
The POSIX mkdtemp function creates a directory with 700 permissions to
avoid this problem.
catamorphism added a commit that referenced this pull request Jan 20, 2013
clean up tempfile module and rm FIXME
@catamorphism catamorphism merged commit 0a8c039 into rust-lang:incoming Jan 20, 2013
@catamorphism
Copy link
Contributor

Looks good, thanks!

@thestinger thestinger deleted the mkdtemp branch January 20, 2013 22:21
RalfJung added a commit to RalfJung/rust that referenced this pull request Sep 18, 2025
Add minimal functionality for using GenMC mode
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants