|
|
| Line 70: |
Line 70: |
| * XXX | | * XXX |
| |} | | |} |
|
| |
| ;'''sec-audit''': Bugs marked sec-audit are typically for tasks to investigate a particular component of concern, or pattern of concern. It should NEVER be used for an actual, identified vulnerability. Either a sec-audit bug should cause additional bugs to be opened for specific instances, or a specific bug should cause a sec-audit bug to be opened for investigating variants of the original.
| |
| {| class="wikitable collapsible " style="width: 100%"
| |
| ! ''sec-audit Examples:''
| |
| |-
| |
| |
| |
| * XXX
| |
| |} | | |} |
|
| |
|
| ;'''sec-vector''': Flaws not in Mozilla controlled software, but can cause security problems for Mozilla users.
| | A historical keyword is <b>sec-incident</b>, which is no longer used. <b>sec-want, sec-audit,</b> and <b>sec-vector</b> are not used for Web client bugs. |
| {| class="wikitable collapsible " style="width: 100%"
| |
| ! ''sec-vector Examples:''
| |
| |-
| |
| |
| |
| * XXX
| |
| |}
| |
| ;'''sec-want''': New features or improvement ideas related to security. As with sec-audit, it should NEVER be applied to an actual vulnerability; but a sec-want may cause new bugs to be opened for specific vulnerabilities, or a vulnerability may spawn a follow-up bug tagged sec-want.
| |
| | |
| {| class="wikitable collapsible " style="width: 100%"
| |
| ! ''sec-want Examples:''
| |
| |-
| |
| |
| |
| * XXX
| |
| |}
| |
| |}
| |
|
| |
|
| === wsectype- Keywords === | | === wsectype- Keywords === |