Signed-off-by: Derek Straka <[email protected]> --- .../python/python-backports-ssl_3.4.0.2.bb | 23 ++++++++++++++++++++ 1 file changed, 23 insertions(+) create mode 100644 meta-python/recipes-devtools/python/python-backports-ssl_3.4.0.2.bb
diff --git a/meta-python/recipes-devtools/python/python-backports-ssl_3.4.0.2.bb b/meta-python/recipes-devtools/python/python-backports-ssl_3.4.0.2.bb new file mode 100644 index 0000000..9caae41 --- /dev/null +++ b/meta-python/recipes-devtools/python/python-backports-ssl_3.4.0.2.bb @@ -0,0 +1,23 @@ +SUMMARY = "The ssl.match_hostname() function from Python 3.4" +DESCRIPTION = "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 backport brings match_hostname() to users of earlier versions of Python" +HOMEPAGE = "https://pypi.python.org/pypi/backports.ssl_match_hostname"; +SECTION = "devel/python" + +LICENSE = "GPLv2" +LIC_FILES_CHKSUM = "file://PKG-INFO;md5=77b684960b86b7a4bb4a450ffde08605" + +SRCNAME = "backports.ssl_match_hostname" + +SRC_URI = "https://pypi.python.org/packages/source/b/${SRCNAME}/${SRCNAME}-${PV}.tar.gz"; + +SRC_URI[md5sum] = "788214f20214c64631f0859dc79f23c6" +SRC_URI[sha256sum] = "07410e7fb09aab7bdaf5e618de66c3dac84e2e3d628352814dc4c37de321d6ae" + +S = "${WORKDIR}/${SRCNAME}-${PV}" + +inherit setuptools -- 1.7.9.5 -- _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-devel
