Ensure that each #nosec usage has an accompanying explanation
Registered by
Travis McPeak
#nosec tags should not just be used to make problems go away. Every time somebody uses #nosec it should be accompanied by an explanation for why this really isn't a security issue.
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- Travis McPeak
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Obsolete
- Series goal:
- None
- Implementation:
-
Not started
- Milestone target:
- None
- Started by
- Completed by
- Eric Brown
Related branches
Related bugs
Sprints
Whiteboard
icordasc (2015-06-02) - So would it look something like
# nosec(sigmaviru
(?)
