Django-otp

Latest version: v1.5.0

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

Scan your dependencies

Page 10 of 11

0.2.4

-------------------------------------------------------------

- Per the RFC, :class:`~django_otp.plugins.otp_totp.models.TOTPDevice` will no
longer verify the same token twice.

- Cosmetic fixes to the admin login form on Django 1.6.

.. warning::

This includes a model change in TOTPDevice. If you are upgrading and your
project uses South, you should first convert it to South with ``manage
migrate otp_totp 0001 --fake``. If you're not using South, you will need to
generate and run the appropriate SQL manually.

0.2.3

-------------------------------------

- OTPMiddleware no longer interferes with pickling request.user.

0.2.2

-------------------------------------------------

- Update Django requirement to 1.4.2, the first version with django.utils.six.

0.2.1

------------------------------------

- Fix unicode representation of devices in some exotic scenarios.

0.2.0

---------------------------------------

- Now supports Django 1.4 to 1.6 on Python 2.6, 2.7, 3.2, and 3.3. This is the
first release for Python 3.

0.1.8

-----------------------------------------------

- Add :func:`django_otp.user_has_device` to detect whether a user has any
devices configured. This change supports a fix in django-otp-agents 0.1.4.

Page 10 of 11

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.