| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
It had no consequences in security-tracker: the
next-oldstable-point-update.txt file is empty and the
next-point-update.txt CVEs are not used yet for what I can see via this
code path.
|
|
|
|
|
|
| |
Although this is probably subject to personal preference, switch to
octal representation directly instead of specifying the mode in decimal
variant. Reading 0o700 makes it immediately clear what is meant.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
If ~/.cache does not already exist, then this happens:
$ ./bin/lts-cve-triage.py
Updating ~/.cache/debian_security_tracker.json from https://security-tracker.debian.org/tracker/data/json ...
Traceback (most recent call last):
File "./bin/lts-cve-triage.py", line 94, in <module>
tracker = TrackerData(update_cache=not args.skip_cache_update)
File "/home/roberto/src/freexian/security-tracker.git/bin/tracker_data.py", line 40, in __init__
self.update_cache()
File "/home/roberto/src/freexian/security-tracker.git/bin/tracker_data.py", line 77, in update_cache
with open(self.cached_data_path, 'w') as cache_file:
FileNotFoundError: [Errno 2] No such file or directory: '/home/roberto/.cache/debian_security_tracker.json'
|
|
|
|
|
| |
This also removes the normalize_release method, and Issue::get_status()
no longer supports passing aliases such as 'stable' or 'lts'.
|
|
|
|
|
|
|
| |
Shift mappins for oldstable to stretch, stable to buster and new testing
to bullsyeye.
Make LTS suite jessie oldoldstable distribution.
|
|
|
|
|
|
|
|
| |
('<ignored>' precedence over '<undetermined>')
e.g. in lts-cve-triage.py, don't classify undermined 2017 jasperreports issues
specifically marked '<ignored>' in the 'undetermined' report section
(no more triage work needed in that case)
(alternate fix would be rewritting history and reclassify those as <end-of-life>)
|
| |
|
|
|
|
|
| |
These are python classes used by other scripts, but they are
not scripts themselves.
|
| |
|
|
|
|
| |
distribution.
|
|
|
|
|
|
|
|
| |
Use git-ls-remote instead of svn-info to determine the head revision.
v2: Adjust GIT_URL to the security-tracker.git repository
git-svn-id: svn+ssh://svn.debian.org/svn/secure-testing@59027 e39458fd-73e7-0310-bf30-c45bca0a0e42
|
|
|
|
| |
git-svn-id: svn+ssh://svn.debian.org/svn/secure-testing@52645 e39458fd-73e7-0310-bf30-c45bca0a0e42
|
|
|
|
| |
git-svn-id: svn+ssh://svn.debian.org/svn/secure-testing@47794 e39458fd-73e7-0310-bf30-c45bca0a0e42
|
|
|
|
| |
git-svn-id: svn+ssh://svn.debian.org/svn/secure-testing@41166 e39458fd-73e7-0310-bf30-c45bca0a0e42
|
|
|
|
|
|
|
| |
This looks for issues fixed in LTS but yet unfixed in lts_next taking
into account next-oldstable-point-update.txt.
git-svn-id: svn+ssh://svn.debian.org/svn/secure-testing@39374 e39458fd-73e7-0310-bf30-c45bca0a0e42
|
|
|
|
| |
git-svn-id: svn+ssh://svn.debian.org/svn/secure-testing@38839 e39458fd-73e7-0310-bf30-c45bca0a0e42
|
|
|
|
| |
git-svn-id: svn+ssh://svn.debian.org/svn/secure-testing@33868 e39458fd-73e7-0310-bf30-c45bca0a0e42
|
|
|
|
| |
git-svn-id: svn+ssh://svn.debian.org/svn/secure-testing@33573 e39458fd-73e7-0310-bf30-c45bca0a0e42
|
|
It helps doing CVE triage by comparing status of issues with the
"next_lts" release (managed by the security team instead of the LTS team).
git-svn-id: svn+ssh://svn.debian.org/svn/secure-testing@33498 e39458fd-73e7-0310-bf30-c45bca0a0e42
|