In particular, reject ssh-dss keys here. They don't work anymore since
an upgrade, for security reasons, but there was not really a way for the
user to know why. With this they will at least know if when they try to
save or change the keys.
Update the recognized conference guidelines in the "Financial"
section to be clearer as to how to create a statement of how
financial proceeds are applied.
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.
The code was supposed to pick the latest version of the repo rpm in this
scenario, but at some point the data structure was updated and the code
was not, so it ended up actually picking the *oldest* version of the
repo rpm.
There is no navFooter class defined in the CSS, a fact made quite
clear due to one of its uses being misspelled without any problems.
Remove class declaration.
http://www.opensource.org/licenses/postgresql redirects with a
301 to its https counterpart, update the link to save a redirect
for our users.
This link is present in all the presskits as well, but the amount
of clicks there should be low enough to not bother.
There is no such thing as OSX anymore, it is now macOS. This
updates the version 10 presskit, but leaves the backbranch
presskits even though Apple has retroactively renamed the old
versions macOS as well.
The <img .. /> tag is required to be to closed in XHTML, as opposed
to HTML where <img ..> is valid. Properly close all currently open
img tags and also add alt="" attributes where missing.
That just generates a completely empty page in the output, so remove the
link completely instead.
For supported versions we list all of them, including if they have no
patches.
This also removes the two previous static pages for this information.
Access to the old "security archives" URL is now redirected back to the
main security page, since the archive is replaced with a dynamically
built of per-version security patches.
Previously we just used "is member of staff", but for better granuality
explicitly also check membership of groups. This introduces the new
group "varnish purgers" for that permission.
This finally moves the patches into the db, which makes it a lot easier
to filter patches in the views.
It also adds the new way of categorising patches, which is assigning
them a CVSSv3 score.
For now, there are no public views to this, and the old static pages
remain. This is so we can backfill all existing security patches before
we make it public.
This callback can prevent new users from being created based on specific
criteria. The plugin is defined in settings.py, so it can be any python
code. For example, it can look up in a specific table if this user is
supposed to be allowed to log in at all.
This sample is used across most of our other sites, so add functionality
to install without having a local master repo.
Back-patch of pgeu commit 3e4d8c9101c2d309b134c2f5638aa40db8ef2cf5
Don't say version 0.0 in the emails that are sent out. That's what we
call it internally, but the URL should have /devel/ in it. Fix this both
in the template, and then if it comes through in the form again in case
the user picked up a link elsewhere that is incorrect.
