Zope.password

Latest version: v6.0

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

Scan your dependencies

Page 2 of 3

4.2.0

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

- Drop support for Python 2.6.

- Converted documentation to Sphinx, including testing doctest snippets
under ``tox``.

- Add support for Python 3.5.

4.1.0

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

- Add support for PyPy. (PyPy3 is pending release of a fix for:
https://bitbucket.org/pypy/pypy/issue/1946)

- Add supprt for Python 3.4.

- Add support for testing on Travis.

4.0.2

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

- Fix some final resource warnings.

4.0.1

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

- Fix test failures under Python 3.3 when warnings are enabled.

4.0.0

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

- Make ``zpasswd`` a proper console script entry point.

- Add ``tox.ini`` and ``MANIFEST.in``.

- Add support for Python 3.3

- Replace deprecated ``zope.interface.implements`` usage with equivalent
``zope.interface.implementer`` decorator.

- Drop support for Python 2.4 and 2.5.

- Add a new ``IMatchingPasswordManager`` interface with a 'match' method,
which returns True if a given password hash was encdoded with the scheme
implemented by the specific manager. All managers in this package implement
this interface.

- Use "{SHA}" as the prefix for SHA1-encoded passwords to be compatible with
RFC 2307, but support matching against "{SHA1}" for backwards compatibility.

- Add a crypt password manager to fully support all methods named in RFC 2307.
It is contained in the ``legacy`` module however, to flag crypt's status.

- Add a SMD5 (salted MD5) password manager to fully support all encoding
schemes implemented by OpenLDAP.

- Add a MySQL ``PASSWORD()`` (versions before 4.1) password manager, as also
found in Zope2's ``AccessControl.AuthEncoding`` module.

- Remove the useless, cosmetic salt from the MD5 and SHA1 password managers,
and use base64 encoding instead of hexdigests. This makes the output of
these managers compatible with other MD5 and SHA1 hash implementations such
as RFC 2307 but doesn't lower it's security in any way. Checking passwords
against old, still 'salted' password hashes with hexdigests is still
supported.

- Use the ``standard_base64encode`` method instead of ``url_base64encode``
to maintain compatibility with LDAP.

3.6.1

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

- The SSHAPasswordManager.checkPassword() would not handle unicode input
(even if the string would only contain ascii characters). Now, the
``encoded_password`` input will be encoded to ascii, which is deemed safe
as it should not contain non-ascii characters anyway.

Page 2 of 3

© 2025 Safety CLI Cybersecurity Inc. All Rights Reserved.