| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
The first revision on the website doesn't have a postfix.
The second revision has a postfix of -2.
I was going to do something similar for DSA too, but found regression update
advisories are not available on the website for DSAs.
|
|
|
|
|
|
| |
This reverts commit 7177c0e348acbd70b76de7fc36116d02201bc9bf.
I accidentally pushed this to the wrong branch.
|
|
|
|
|
|
|
|
|
| |
The first revision on the website doesn't have a postfix.
The second revision has a postfix of -2.
I was going to do something similar for DSA too, but found regression update
advisories are not available on the website for DSAs.
|
|
|
|
|
|
|
| |
The novell.com address is historical and deprecated.
Requested-by: Alexandros Toptsoglou <atoptsoglou@suse.com>
Requested-in: <a3bc5c9f-d52d-a79d-e1da-6a6484cee9ea@suse.com>
|
|
|
|
|
|
|
|
|
|
|
| |
Update references for backports suites for buster-backports,
stretch-backports and jessie-backports for status overview pages.
For testing migration canidates (which is helpful during freeze periods
to determine which fixes from usntable need to go to testing yet), make
bullseye the new testing distribution.
Updates lists of releases to sid, bullseye, buster, stretch and jessie.
|
|
|
|
|
| |
...for non-main packages. For those, emptying pkg_name is not enough,
we also need to set title to None.
|
|
|
|
|
|
|
|
|
|
|
| |
As discussed in https://bugs.debian.org/859122 DLAs and DSAs will be
separated in different supages. This needs adaption for the URL
referenced in the source fields of the security-tracker for DLAs.
v2: Correct URL to actually match the final location under
/lts/security. Cf. https://bugs.debian.org/859122#82
Thanks: Laura Arjona Reina, Holger Levsen and Antoine Beaupré
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
In commit 49e287d2574ed385e31ce3d36cb3cb19f4c7785f "tracker_service:
send a Last-Modified header for /tracker/data/json" I made the
json_timestamp update conditional on whether the data had changed. That
meant that after a few minutes, we would consider the data to be always
stale, and recompute it every single time, as long as it didn't change.
To fix this, use separate timestamps for "when did we check last"
(json_timestamp) and "when did it change last" (json_last_modified).
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Hosting the tracker at an URL different from /tracker/ was not possible
without these changes. There's still one small glitch left with the
hardcoding of /tracker/logo.png in static/style.css.
|
| |
|
|
|
|
| |
git-svn-id: svn+ssh://svn.debian.org/svn/secure-testing@59022 e39458fd-73e7-0310-bf30-c45bca0a0e42
|
|
|
|
|
|
|
|
|
|
|
| |
Replace reference to bin/tracker_service.py via the salsa/gitlab
webinterface.
Referece the security-tracker project instead of the SVN repository.
Signed-off-by: Salvatore Bonaccorso <carnil@debian.org>
git-svn-id: svn+ssh://svn.debian.org/svn/secure-testing@59021 e39458fd-73e7-0310-bf30-c45bca0a0e42
|
|
|
|
|
|
| |
Signed-off-by: Salvatore Bonaccorso <carnil@debian.org>
git-svn-id: svn+ssh://svn.debian.org/svn/secure-testing@59020 e39458fd-73e7-0310-bf30-c45bca0a0e42
|
|
|
|
|
|
| |
Thanks: Andreas Stieger <astieger@suse.com>
git-svn-id: svn+ssh://svn.debian.org/svn/secure-testing@58680 e39458fd-73e7-0310-bf30-c45bca0a0e42
|
|
|
|
|
|
| |
Thanks: Andreas Stieger <astieger@suse.com>
git-svn-id: svn+ssh://svn.debian.org/svn/secure-testing@58677 e39458fd-73e7-0310-bf30-c45bca0a0e42
|
|
|
|
| |
git-svn-id: svn+ssh://svn.debian.org/svn/secure-testing@58437 e39458fd-73e7-0310-bf30-c45bca0a0e42
|
|
|
|
| |
git-svn-id: svn+ssh://svn.debian.org/svn/secure-testing@58188 e39458fd-73e7-0310-bf30-c45bca0a0e42
|
|
|
|
|
|
|
|
|
| |
Disconnect Search just redirects to DuckDuckGo now.
Also rename the functions from disconnect to web_search
in case of future changes to the usual web search engine.
git-svn-id: svn+ssh://svn.debian.org/svn/secure-testing@58046 e39458fd-73e7-0310-bf30-c45bca0a0e42
|
|
|
|
|
|
| |
The current URLs redirect to the new URLs.
git-svn-id: svn+ssh://svn.debian.org/svn/secure-testing@58045 e39458fd-73e7-0310-bf30-c45bca0a0e42
|
|
|
|
| |
git-svn-id: svn+ssh://svn.debian.org/svn/secure-testing@54914 e39458fd-73e7-0310-bf30-c45bca0a0e42
|
|
|
|
|
|
| |
"postponed" no-dsa substates
git-svn-id: svn+ssh://svn.debian.org/svn/secure-testing@54582 e39458fd-73e7-0310-bf30-c45bca0a0e42
|
|
|
|
| |
git-svn-id: svn+ssh://svn.debian.org/svn/secure-testing@54581 e39458fd-73e7-0310-bf30-c45bca0a0e42
|
|
|
|
| |
git-svn-id: svn+ssh://svn.debian.org/svn/secure-testing@52646 e39458fd-73e7-0310-bf30-c45bca0a0e42
|
|
|
|
| |
git-svn-id: svn+ssh://svn.debian.org/svn/secure-testing@50157 e39458fd-73e7-0310-bf30-c45bca0a0e42
|
|
|
|
| |
git-svn-id: svn+ssh://svn.debian.org/svn/secure-testing@50156 e39458fd-73e7-0310-bf30-c45bca0a0e42
|
|
|
|
| |
git-svn-id: svn+ssh://svn.debian.org/svn/secure-testing@46696 e39458fd-73e7-0310-bf30-c45bca0a0e42
|
|
|
|
| |
git-svn-id: svn+ssh://svn.debian.org/svn/secure-testing@43223 e39458fd-73e7-0310-bf30-c45bca0a0e42
|
|
|
|
| |
git-svn-id: svn+ssh://svn.debian.org/svn/secure-testing@43038 e39458fd-73e7-0310-bf30-c45bca0a0e42
|
|
|
|
| |
git-svn-id: svn+ssh://svn.debian.org/svn/secure-testing@42500 e39458fd-73e7-0310-bf30-c45bca0a0e42
|
|
|
|
| |
git-svn-id: svn+ssh://svn.debian.org/svn/secure-testing@41133 e39458fd-73e7-0310-bf30-c45bca0a0e42
|
|
|
|
| |
git-svn-id: svn+ssh://svn.debian.org/svn/secure-testing@41130 e39458fd-73e7-0310-bf30-c45bca0a0e42
|
|
|
|
|
|
|
|
| |
OSVDB is now closed officially:
https://blog.osvdb.org/2016/04/05/osvdb-fin/
git-svn-id: svn+ssh://svn.debian.org/svn/secure-testing@40780 e39458fd-73e7-0310-bf30-c45bca0a0e42
|
|
|
|
| |
git-svn-id: svn+ssh://svn.debian.org/svn/secure-testing@40725 e39458fd-73e7-0310-bf30-c45bca0a0e42
|
|
|
|
| |
git-svn-id: svn+ssh://svn.debian.org/svn/secure-testing@40514 e39458fd-73e7-0310-bf30-c45bca0a0e42
|
|
|
|
| |
git-svn-id: svn+ssh://svn.debian.org/svn/secure-testing@40422 e39458fd-73e7-0310-bf30-c45bca0a0e42
|
|
|
|
|
|
|
|
|
|
|
| |
This is often very confusing because it lists the state only for the main
archive, not the security archive, so stable will be shown as vulnerable
for many weeks after a DSA has been issued, until the next point release.
That's not very relevant information. It also duplicates the table below
with fixed status per suite and archive.
git-svn-id: svn+ssh://svn.debian.org/svn/secure-testing@40387 e39458fd-73e7-0310-bf30-c45bca0a0e42
|
|
|
|
| |
git-svn-id: svn+ssh://svn.debian.org/svn/secure-testing@40125 e39458fd-73e7-0310-bf30-c45bca0a0e42
|
|
|
|
|
|
|
|
|
|
| |
* once computed, keep the JSON data cached in memory for 5
minutes (default value) before regenerating it
* at the very minimum we'll need to send along a Last-Modified header
exposing when the data was last generated
git-svn-id: svn+ssh://svn.debian.org/svn/secure-testing@39406 e39458fd-73e7-0310-bf30-c45bca0a0e42
|
|
|
|
| |
git-svn-id: svn+ssh://svn.debian.org/svn/secure-testing@39403 e39458fd-73e7-0310-bf30-c45bca0a0e42
|
|
|
|
|
|
|
|
|
| |
This reverts commit 8610b300608199e8be73ccda726f539fa217471b.
We tentatively reenable the json export after Seb's changes. Let's see
how it goes.
git-svn-id: svn+ssh://svn.debian.org/svn/secure-testing@39402 e39458fd-73e7-0310-bf30-c45bca0a0e42
|
|
|
|
| |
git-svn-id: svn+ssh://svn.debian.org/svn/secure-testing@39343 e39458fd-73e7-0310-bf30-c45bca0a0e42
|
|
|
|
| |
git-svn-id: svn+ssh://svn.debian.org/svn/secure-testing@39342 e39458fd-73e7-0310-bf30-c45bca0a0e42
|
|
|
|
| |
git-svn-id: svn+ssh://svn.debian.org/svn/secure-testing@39315 e39458fd-73e7-0310-bf30-c45bca0a0e42
|
|
|
|
| |
git-svn-id: svn+ssh://svn.debian.org/svn/secure-testing@37789 e39458fd-73e7-0310-bf30-c45bca0a0e42
|