pkgsrc/security/py-backports.ssl_match_hostname/PLIST

@comment $NetBSD: PLIST,v 1.3 2017/11/22 11:00:24 markd Exp $
${PYSITELIB}/${EGG_FILE}
${PYSITELIB}/backports/ssl_match_hostname/__init__.py
${PYSITELIB}/backports/ssl_match_hostname/__init__.pyc
${PYSITELIB}/backports/ssl_match_hostname/__init__.pyo
py-backports.ssl_match_hostname: depend on py-backports 2017-11-22 12:00:24 +01:00			`@comment $NetBSD: PLIST,v 1.3 2017/11/22 11:00:24 markd Exp $`
Update security/py-backports.ssl_match_hostname to 3.5.0.1. pkgsrc changes: * Switch to distutils.mk in order to avoid installation error in the install phase (``error: option --single-version-externally-managed not recognized'' ref. to setup.py). No functional changes intended. * Use MASTER_SITE_PYPI instead of hard-coding the entire pypi.python.org URL. Changes: * It was updated in python-3.5 to handle IPAddresses in ServerAltName fields (something that backports.ssl_match_hostname will do if you also install the ipaddress library from pypi). 2015-12-30 16:02:06 +01:00			`${PYSITELIB}/${EGG_FILE}`
Import py27-backports.ssl_match_hostname-3.4.0.2 as security/py-backports.ssl_match_hostname. The Secure Sockets layer is only actually secure if you check the hostname in the certificate returned by the server to which you are connecting, and verify that it matches to hostname that you are trying to reach. But the matching logic, defined in RFC2818, can be a bit tricky to implement on your own. So the ssl package in the Standard Library of Python 3.2 and greater now includes a match_hostname() function for performing this check instead of requiring every application to implement the check separately. This package contains the backport of this functionality to Python 2. 2014-01-27 20:53:30 +01:00			`${PYSITELIB}/backports/ssl_match_hostname/__init__.py`
			`${PYSITELIB}/backports/ssl_match_hostname/__init__.pyc`
			`${PYSITELIB}/backports/ssl_match_hostname/__init__.pyo`