Merge ~sbeattie/ubuntu-cve-tracker/+git/ubuntu-cve-tracker:check-cves_ignore_cache into ubuntu-cve-tracker:master
Status: | Needs review |
---|---|
Proposed branch: | ~sbeattie/ubuntu-cve-tracker/+git/ubuntu-cve-tracker:check-cves_ignore_cache |
Merge into: | ubuntu-cve-tracker:master |
Diff against target: |
106 lines (+46/-7) 2 files modified
scripts/check-cves (+9/-7) scripts/check_cves/ignored_cache.py (+37/-0) |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Alex Murray | Approve | ||
Seth Arnold | Approve | ||
Review via email:
|
Commit message
[WIP] check-cves: add a cache of 5 last ignored reasons
Often times when performing triage I bounce between CVEs of a few
different products from the same vendor that end up being ignored. It's
useful to have roughly a cache of five or so entries, plus the debian
reason if available plus the heuristic guess.
Implement a small cache of previously used reasons for ignoring a cve.
It keeps the ordering the same as before, with the cache entries added
last, orted in most recently used order.
Using this results in things looking like:
Debian CVE Tracker: NOT-FOR-US: Node sds
A]dd (or R]epeat), I]gnore forever, S]kip for now, or Q]uit? [ignore]
Reason to be ignored?
a) Node sds
b) sds from
c) BlogEngine.NET
d) InHand Networks InRouter302
e) OpenClinica
f) Intel(R) NUCs
g) Check Point Enterprise Endpoint
Signed-off-by: Steve Beattie <email address hidden>
TODO: unit tests. Sorry.
Unmerged commits
- cea1697... by Steve Beattie
-
unit-tests:0 (build) check-cves:0 (build) 1 → 2 of 2 results First • Previous • Next • Last
Need unit tests, otherwise LGTM :P