Django-axes

Latest version: v7.0.0

Safety actively analyzes 679296 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 17 of 25

5.0.2

Not secure
------------------

- Add ``AXES_ENABLED`` setting for disabling Axes with e.g. tests
that use Django test client ``login``, ``logout``, and ``force_login``
methods, which do not supply the ``request`` argument to views,
preventing Axes from functioning correctly in certain test setups.
[aleksihakli]

5.0.1

Not secure
------------------

- Add changelog to documentation.
[aleksihakli]

5.0

Not secure
----------------

- Deprecate Python 2.7, 3.4 and 3.5 support.
[aleksihakli]

- Remove automatic decoration and monkey-patching of Django views and forms.
Decorators are available for login function and method decoration as before.
[aleksihakli]

- Use backend, middleware, and signal handlers for tracking
login attempts and implementing user lockouts.
[aleksihakli, jorlugaqui, joshua-s]

- Add ``AxesDatabaseHandler``, ``AxesCacheHandler``, and ``AxesDummyHandler``
handler backends for processing user login and logout events and failures.
Handlers are configurable with the ``AXES_HANDLER`` setting.
[aleksihakli, jorlugaqui, joshua-s]

- Improve management commands and separate commands for resetting
all access attempts, attempts by IP, and attempts by username.
New command names are ``axes_reset``, ``axes_reset_ip`` and ``axes_reset_username``.
[aleksihakli]

- Add support for string import for ``AXES_USERNAME_CALLABLE``
that supports dotted paths in addition to the old
callable type such as a function or a class method.
[aleksihakli]

- Deprecate one argument call signature for ``AXES_USERNAME_CALLABLE``.
From now on, the callable needs to accept two arguments,
the HttpRequest and credentials that are supplied to the
Django ``authenticate`` method in authentication backends.
[aleksihakli]

- Move ``axes.attempts.is_already_locked`` function to ``axes.handlers.AxesProxyHandler.is_locked``.
Various other previously undocumented methods have been deprecated and moved inside the project.
The new documented public APIs can be considered as stable and can be safely utilized by other projects.
[aleksihakli]

- Improve documentation layouting and contents. Add public API reference section.
[aleksihakli]

4.5.4

Not secure
------------------

- Improve README and documentation
[aleksihakli]

4.5.3

Not secure
------------------

- Remove the unused ``AccessAttempt.trusted`` flag from models
[aleksihakli]

- Improve README and Travis CI setups
[aleksihakli]

4.5.2

Not secure
------------------

- Added Turkish translations
[obayhan]

Page 17 of 25

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.