Creating temporary files in bash

by

The mktemp(1) man page explains it fairly well:

Traditionally, many shell scripts take the name of the program with
the pid as a suffix and use that as a temporary file name. This kind
of naming scheme is predictable and the race condition it creates is
easy for an attacker to win. A safer, though still inferior, approach
is to make a temporary directory using the same naming scheme. While
this does allow one to guarantee that a temporary file will not be
subverted, it still allows a simple denial of service attack. For
these reasons it is suggested that mktemp be used instead.

In a script, I invoke mktemp something like

mydir=$(mktemp -d "${TMPDIR:-/tmp/}$(basename $0).XXXXXXXXXXXX")

which creates a temporary directory I can work in, and in which I can safely name the actual files something readable and useful.

mktemp is not standard, but it does exist on many platforms. The “X”s will generally get converted into some randomness, and more will probably be more random; however, some systems (busybox ash, for one) limit this randomness more significantly than others

By the way, safe creation of temporary files is important for more than just shell scripting. That’s why python has tempfile, perl has File::Temp, ruby has Tempfile, etc…

More Related Contents:

  1. Looping through the content of a file in Bash
  2. Why should eval be avoided in Bash, and what should I use instead?
  3. Setting an argument with bash [duplicate]
  4. How do I write standard error to a file while using “tee” with a pipe?
  5. How to kill a child process after a given timeout in Bash?
  6. How to generate a core dump in Linux on a segmentation fault?
  7. What does $@ mean in a shell script?
  8. Better way to rename files based on multiple patterns
  9. How to set environment variable for everyone under my linux system?
  10. Linux: copy and create destination dir if it does not exist
  11. What is the difference between using `sh` and `source`?
  12. What is the difference between “#!/usr/bin/env bash” and “#!/usr/bin/bash”?
  13. Extract file basename without path and extension in bash [duplicate]
  14. How do you find the original user through multiple sudo and su commands?
  15. How to sort a file in-place?
  16. How can I remove the last character of a file in unix?
  17. Managing log files created by cron jobs
  18. How to run a shell script on a Unix console or Mac terminal?
  19. How do I syntax check a Bash script without running it?
  20. How to check if a file is empty in Bash?
  21. Is it OK to use the same input file as output of a piped command?
  22. Should PATH contain directories or full paths to binaries?
  23. Execute a command without keeping it in history [closed]
  24. When to wrap quotes around a shell variable?
  25. Running shell script in parallel
  26. Difference between shell and environment variables
  27. What’s the point of eval/bash -c as opposed to just evaluating a variable?
  28. What are the rules for valid identifiers (e.g. functions, vars, etc) in Bash?
  29. Need to remove the count from the output when using “uniq -c” command
  30. How do you run a script on login in *nix?

Leave a Comment