This repository has been archived by the owner on Sep 5, 2020. It is now read-only.
forked from django/django
-
Notifications
You must be signed in to change notification settings - Fork 0
2.2upgrade #2
Open
KavinKaviarasan1
wants to merge
3,180
commits into
nimbis
Choose a base branch
from
2.2upgrade
base: nimbis
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
2.2upgrade #2
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…h Sphinx 2.1.0. Backport of 5ab75ad from master
Backport of f3a03d5 from master
… and updated example of custom aggregate functions. Backport of 76b3fc5 from master
Backport of 175656e from master
…rom_email. Backport of 0c2ffdd from master
Backport of 036362e from master
Backport of a7038ad from master
…ation. Backport of 00169bc from master
Backport of 5333117 from master
Backport of 2ef6f20 from master
Backport of ad7b438 from master.
Backport of 8590726 from master.
Backport of 2f91e78 from master
Backport of 8338784 from master
…ule doesn't have __file__ attribute. Backport of 8454f6d from master
…database. Backport of 4305fbe from master
Backport of 30b3ee9 from master
…PROXY_SSL_HEADER if set. An HTTP request would not be redirected to HTTPS when the SECURE_PROXY_SSL_HEADER and SECURE_SSL_REDIRECT settings were used if the proxy connected to Django via HTTPS. HttpRequest.scheme will now always trust the SECURE_PROXY_SSL_HEADER if set, rather than falling back to the request scheme when the SECURE_PROXY_SSL_HEADER did not have the secure value. Thanks to Gavin Wahl for the report and initial patch suggestion, and Shai Berger for review. Backport of 54d0f5e from master
Backport of fc41401 from master
Backport of 868cd56 from master
…to email addresses without single quotes. Backport of c2f381e from master
…s for custom UserAdmin with a custom user model. Backport of c13e371 from master
….to_python() means no match. Backport of f197c3d from master
Backport of 08e69ca from master
Backport of 24e8f7f from master
Backport of 69e2cd6 from master.
Backport of a4e4737 from master.
Backport of 678f958 from master
"term" role became case sensitive in Sphinx 3.0.1. Backport of cc70a03 from master
Backport of 0668164 from master.
Backport of 81dc710 from master
…eyRawIdWidget.
…ached backends.
…ces_to on Python 3.5.
Backport of 926148e from master.
Backport of 0f3aecf from master.
…ces_to on Python 3.5.
…e notes. Backport of 392036b from master
This applies a patch to allow the use of Django on a FIPS-compliant system with MD5 disabled. This utilizes the optional 'usedforsecurity=False' parameter that is passed into the hashlib.md5 function. This allows the use of MD5 even when MD5 has been disabled at the system level.
Had to add the try/except loop to make the md5 fixes work/pass during testing.
kevinrobbins
approved these changes
Jul 31, 2020
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I could not find anymore instances of hashlib.md5()
that did not have usedforsecurity
added (with the exception of the exception handling calls).
Thanks for the review @kevinrobbins . I don't think we should actually merge this into the nimbis branch, though. The best way to do this would probably be to have our separate release-2.2 branch that we sync with upstream, and then cherry pick the md5 commits on top of, for every new patch release. Then make our own release. No merge involved. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added md5 patches to the django 2.2 fork