general_hardcoded_tmp only considers /tmp and not other FHS locations
Bug #1473725 reported by
Dave Walker
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Bandit |
Fix Released
|
Undecided
|
Dave Walker | ||
Bug Description
Currently, only /tmp is considered when looking for hard coded uses of temporary files. Other places that should be part of this test are /var/tmp and /dev/shm.
Maybe also /run, /var/run and /var/lock ?
| Changed in bandit: | |
| assignee: | nobody → Dave Walker (davewalker) |
| status: | New → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to bandit (master) | #1 |
| Changed in bandit: | |
| status: | In Progress → Fix Committed |
Revision history for this message
| Eric Brown (ericwb) wrote | #2 |
| Changed in bandit: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: master
commit a8325942e41b0df
Author: Dave Walker (Daviey) <email address hidden>
Date: Sun Jul 12 13:44:33 2015 +0100
Consider other hardcoded tmp paths
Previously general_
for hard-coded usage of "/tmp/", however the same issues
can be present on other FHS locations such as /var/tmp/
and /dev/shm.
This change adds these additional locations for
consideration.
Closes-Bug: #1473725
Signed-off-by: Dave Walker (Daviey) <email address hidden>
Change-Id: I76f154134e6cc9