myMPD-25.3.0-alt1.x86_64	unsafe-tmp-usage-in-scripts	fail	The test discovered scripts with errors which may be used by a user for damaging important system files. For example if a script uses in its work a temp file which is created in /tmp directory, then every user can create symlinks with the same name (pattern) in this directory in order to destroy or rewrite some system or another user's files. Scripts _must_ _use_ mktemp/tempfile or must use $TMPDIR. mktemp/tempfile is safest. $TMPDIR is safer than /tmp/ because libpam-tmpdir creates a subdirectory of /tmp that is only accessible by that user, and then sets TMPDIR and other variables to that. Hence, it doesn't matter nearly as much if you create a non-random filename, because nobody but you can access it. Found error in /usr/bin/mympd-config: $ grep /tmp/ /usr/bin/mympd-config roottext=,blue disabledentry=gray, entry=white,gray' set_default() { $MYMPD_BIN | $MYMPD_BIN | awk '/^ /{print toupper($1) $2}' > /tmp/mympd_defaults while read KEY VALUE do eval "MYMPD_$KEY=$VALUE" done < /tmp/mympd_defaults rm /tmp/mympd_defaults if ! MYMPD_CA_CERT_STORE=$(curl-config 2>/dev/null) then MYMPD_CA_CERT_STORE_PATHS="/etc/ssl/certs/ca-certificates.crt \ /etc/ssl/certs/ca-bundle.crt \ /etc/pki/tls/certs/ca-bundle.crt \; 
