Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • G Gesfi-Project2
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Prog
  • Gesfi-Project2
  • Merge requests
  • !1

Open
Created Feb 03, 2018 by Prog@ProgMaintainer
  • Report abuse
Report abuse

Initial Update

  • Overview 0
  • Commits 1
  • Changes 1

Created by: pyup-bot

This is my first visit to this fine repo so I have bundled all updates in a single pull request to make things easier for you to merge.

Close this pull request and delete the branch if you want me to start with single pull requests right away

Here's the executive summary:

Updates

Here's a list of all the updates bundled in this pull request. I've added some links to make it easier for you to find all the information you need.

Django 2.0.1 » 2.0.2 PyPI | Changelog | Homepage

Changelogs

Django 2.0.1 -> 2.0.2

2.0.2

==========================

February 1, 2018

Django 2.0.2 fixes a security issue and several bugs in 2.0.1.

CVE-2018-6188: Information leakage in AuthenticationForm

A regression in Django 1.11.8 made :class:~django.contrib.auth.forms.AuthenticationForm run its confirm_login_allowed() method even if an incorrect password is entered. This can leak information about a user, depending on what messages confirm_login_allowed() raises. If confirm_login_allowed() isn't overridden, an attacker enter an arbitrary username and see if that user has been set to is_active=False. If confirm_login_allowed() is overridden, more sensitive details could be leaked.

This issue is fixed with the caveat that AuthenticationForm can no longer raise the "This account is inactive." error if the authentication backend rejects inactive users (the default authentication backend, ModelBackend, has done that since Django 1.10). This issue will be revisited for Django 2.1 as a fix to address the caveat will likely be too invasive for inclusion in older versions.

Bugfixes

  • Fixed hidden content at the bottom of the "The install worked successfully!" page for some languages (🎫28885).
  • Fixed incorrect foreign key nullification if a model has two foreign keys to the same model and a target model is deleted (🎫29016).
  • Fixed regression in the use of QuerySet.values_list(..., flat=True) followed by annotate() (🎫29067).
  • Fixed a regression where a queryset that annotates with geometry objects crashes (🎫29054).
  • Fixed a regression where contrib.auth.authenticate() crashes if an authentication backend doesn't accept request and a later one does (🎫29071).
  • Fixed a regression where makemigrations crashes if a migrations directory doesn't have an __init__.py file (🎫29091).
  • Fixed crash when entering an invalid uuid in ModelAdmin.raw_id_fields (🎫29094).

==========================

Once you have closed this pull request, I'll create separate pull requests for every update as soon as I find them.

That's it for now!

Happy merging! 🤖

Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: pyup-initial-update