| commit | 852aec21e30d39747df78071e3aeea166dcc0fb4 | |
| author | Magnus Hagander <magnus@hagander.net> | |
| Sun, 25 Feb 2018 17:28:01 +0000 (25 18:28 +0100) | ||
| committer | Magnus Hagander <magnus@hagander.net> | |
| Sun, 25 Feb 2018 17:31:43 +0000 (25 18:31 +0100) | ||
| tree | a14da3b547c799124799becbe8934168a1f3d2ab | treesnapshot (tar.gz zip) |
| parent | 90b7e2a637b64f9ecc886ff6d2545672b0cccdf9 | commitdiff |
Allow unlinked CVEs and poll for valid links
This way new CVEs that are added will start off being listed, but not
with a link. When upstream (currently redhat) publishes the CVE, a
cronjob will pick this up and update it with a link.
Of course, we still only show CVEs that are listed as public, but this
should hopefully get rid of some of the questions of why we link to a
404.
This way new CVEs that are added will start off being listed, but not
with a link. When upstream (currently redhat) publishes the CVE, a
cronjob will pick this up and update it with a link.
Of course, we still only show CVEs that are listed as public, but this
should hopefully get rid of some of the questions of why we link to a
404.
| pgweb/security/management/__init__.py | [new file with mode: 0644] | blob |
| pgweb/security/management/commands/__init__.py | [new file with mode: 0644] | blob |
| pgweb/security/management/commands/update_cve_links.py | [new file with mode: 0644] | blob |
| pgweb/security/migrations/0002_cve_visible.py | [new file with mode: 0644] | blob |
| pgweb/security/models.py | diffblobblamehistory | |
| templates/security/security.html | diffblobblamehistory |