![[BACK]](/icons/back.gif){kind=icon}
Up to [cvs.NetBSD.org] / pkgsrc / security / py-service_identity
Request diff between arbitrary revisions
Keyword substitution: kv
Default branch: MAIN
py-service_identity: updated to 24.2.0 24.2.0 Added - Python 3.13 is now officially supported. Changed - pyOpenSSL's identity extraction has been reimplemented using *cryptography*'s primitives instead of deprecated pyOpenSSL APIs. As a result, the oldest supported pyOpenSSL version is now 17.1.0.
py-service_identity: updated to 24.1.0 24.1.0 Changed - If a certificate doesn't contain any `subjectAltName`s, we now raise `service_identity.CertificateError` instead of `service_identity.VerificationError` to make the problem easier to debug.
python/wheel.mk: simplify a lot, and switch to 'installer' for installation This follows the recommended bootstrap method (flit_core, build, installer). However, installer installs different files than pip, so update PLISTs for all packages using wheel.mk and bump their PKGREVISIONs.
*: remove more references to Python 3.7
py-service_identity: restore PKGNAME
service_identity: update to 23.1.0. ## [23.1.0](https://github.com/pyca/service-identity/compare/21.1.0...23.1.0) - 2023-06-14 ### Removed - All Python versions up to and including 3.7 have been dropped. - Support for `commonName` in certificates has been dropped. It has been deprecated since 2017 and isn't supported by any major browser. - The oldest supported pyOpenSSL version (when using the `pyopenssl` backend) is now 17.0.0. When using such an old pyOpenSSL version, you have to pin *cryptography* yourself to ensure compatibility between them. Please check out [`contraints/oldest-pyopenssl.txt`](https://github.com/pyca/service-identity/blob/main/tests/constraints/oldest-pyopenssl.txt) to verify what we are testing against. ### Deprecated - If you've used `service_identity.(cryptography|pyopenssl).extract_ids()`, please switch to the new names `extract_patterns()`. [#56](https://github.com/pyca/service-identity/pull/56) ### Added - `service_identity.(cryptography|pyopenssl).extract_patterns()` are now public APIs (FKA `extract_ids()`). You can use them to extract the patterns from a certificate without verifying anything. [#55](https://github.com/pyca/service-identity/pull/55) - *service-identity* is now fully typed. [#57](https://github.com/pyca/service-identity/pull/57)
py-service_identity: update to 21.1.0. 21.1.0 (2021-05-09) ------------------- Backward-incompatible changes: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - Python 3.4 is not supported anymore. It has been unsupported by the Python core team for a while now, its PyPI downloads are negligible, and our CI provider removed it as a supported option. It's very unlikely that ``service-identity`` will break under 3.4 anytime soon, which is why we do *not* block its installation on Python 3.4. But we don't test it anymore and will block it once someone reports breakage. Changes: ^^^^^^^^ - ``service_identity.exceptions.VerificationError`` can now be pickled and is overall more well-behaved as an exception. This raises the requirement of ``attrs`` to 19.1.0.
fighting a losing battle against the py-cryptography rustification, part 5 Convert py-OpenSSL users to versioned_dependencies.mk
py-service_identity: mark as not for python 2.x
*: bump PKGREVISION for egg.mk users They now have a tool dependency on py-setuptools instead of a DEPENDS
py-service_identity: updated to 18.1.0 18.1.0 - pyOpenSSL is optional now if you use service_identity.cryptography.* only. - Added support for iPAddress subjectAltName\ s. You can now verify whether a connection or a certificate is valid for an IP address using service_identity.pyopenssl.verify_ip_address() and service_identity.cryptography.verify_certificate_ip_address().
Updated py-service_identity to 17.0.0. 17.0.0 (2017-05-23) ------------------- Deprecations: ^^^^^^^^^^^^^ - Since Chrome 58 and Firefox 48 both don't accept certificates that contain only a Common Name, its usage is hereby deprecated in ``service_identity`` too. We have been raising a warning since 16.0.0 and the support will be removed in mid-2018 for good. Changes: ^^^^^^^^ - When ``service_identity.SubjectAltNameWarning`` is raised, the Common Name of the certificate is now included in the warning message. `#17 <https://github.com/pyca/service_identity/pull/17>`_ - Added ``cryptography.x509`` backend for verifying certificates. `#18 <https://github.com/pyca/service_identity/pull/18>`_ - Wildcards (``*``) are now only allowed if they are the leftmost label in a certificate. This is common practice by all major browsers. `#19 <https://github.com/pyca/service_identity/pull/19>`_
Remove python33: adapt all packages that refer to it.
Fix MASTER_SITES.
py-service_identity from version 16.0.0 also needs attrs module (hi wiz! :)) DEPENDS on devel/py-attrs now that we have it and bump PKGREVISION. While here also simplify MASTER_SITE.
Update py-service_identity to 16.0.0. 16.0.0 (2016-02-18) ------------------- Backward-incompatible changes: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - Python 3.3 and 2.6 aren't supported anymore. They may work by chance but any effort to keep them working has ceased. The last Python 2.6 release was on October 29, 2013 and isn't supported by the CPython core team anymore. Major Python packages like Django and Twisted dropped Python 2.6 a while ago already. Python 3.3 never had a significant user base and wasn't part of any distribution's LTS release. - pyOpenSSL versions older than 0.14 are not tested anymore. They don't even build with recent OpenSSL versions. Changes: ^^^^^^^^ - Officially support Python 3.5. - ``service_identity.SubjectAltNameWarning`` is now raised if the server certicate lacks a proper ``SubjectAltName``. [`#9 <https://github.com/pyca/service_identity/issues/9>`_] - Add a ``__str__`` method to ``VerificationError``. - Port from ``characteristic`` to its spiritual successor `attrs <https://attrs.readthedocs.org/>`_.
Import py34-service_identity-14.0.0 as security/py-service_identity. service_identity aspires to give you all the tools you need for verifying whether a certificate is valid for the intended purposes. In the simplest case, this means host name verification. However, service_identity implements RFC 6125 fully and plans to add other relevant RFCs too.