Group :: Sistema/Configurações/Rede
RPM: alterator-mass-management
Navegação
| package id | estatus | teste | mensagem |
|---|---|---|---|
| alterator-mass-management-0.1.7-alt1.noarch |
 fail | unsafe-tmp-usage-in-scripts |
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/lib/alterator/backend3/mass-management: $ grep /tmp/ /usr/lib/alterator/backend3/mass-management mkdir "$TASKS_DIR/task-$number" cat >"$TASKS_DIR/task-$number.yml" < |
| alterator-mass-management-0.1.7-alt1.noarch |
 ok | checkbashisms | |
| alterator-mass-management-0.1.7-alt1.noarch |
ok | sisyphus_check | |
| alterator-mass-management-0.1.7-alt1.noarch |
ok | buildroot |