Wagtail-2fa

Latest version: v1.6.9

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

Scan your dependencies

Page 3 of 3

1.3.0

Not secure
==================
- Add OtpRequiredMixin to enforce OTP checks in views
- Resolve possible vulnerabilities:
- [CWE-290](http://cwe.mitre.org/data/definitions/290.html)
- [CWE-20](http://cwe.mitre.org/data/definitions/20.html)

1.2.0

Not secure
==================
- Added missing deps for generation of the docs
- Added Microsoft Authenticator as example app and removed double space
- Allow admins to delete devices from user accounts

1.1.0

Not secure
==================
- Require the user to enter their password when creating a new token. This is
done based on feedback of a security test by an external company.
- Remove the "Manage 2FA button" on the user listing for now since that didn't
actually work. It always managed the devices of the current logged in user.
This will be added properly in a later version.
- Make the package compatible with django-hosts. The middleware initially
resolved a number of paths on start up time, this is now lazy.
- Update django-otp to version 5.2.0
- Update qrcode to version 6.1

1.0.1

Not secure
==================
- Add Dutch translations (9)
- Add support for Wagtail running in a subdirectory (10)
- Add WAGTAIL_2FA_OTP_TOTP_NAME for easier identification the site (11)
- Update badges in README file (GitHub organisation rename)

0.1.0

Not secure
==================
- Require atleast Wagtail 2.1 for the new account management hooks
- Add information about how to add a device
- Added several unittests

0.0.1

Not secure
==================
- Created package

Page 3 of 3

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.