Characterize, tag, and sort security-related crash data

Registered by John Moser on 2006-07-12

This specification aims to tweak automated-problem-reports to characterize, tag, and sort problems based on security-related factors. The ultimate goal is to organize automated-problem-reports in such a way that skilled developers can specifically look for security vulnerabilities, whether revealed by a detection system such as GccSsp or exposed by the nature of a crash.

Blueprint information

Status:
Not started
Approver:
None
Priority:
Undefined
Drafter:
None
Direction:
Needs approval
Assignee:
None
Definition:
Discussion
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

This should be clean but I have no idea what pitti and friends are up to with automated-problem-reports. The parent tagging spec is more broad-based, but I have a very specific goal in mind.

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.