From 935fec95d094da8db319c9004bcae75a18fb2dc3 Mon Sep 17 00:00:00 2001 From: Zang Ruochen Date: Thu, 24 Oct 2019 13:54:35 +0800 Subject: python-backports-ssl: upgrade 3.5.0.1 -> 3.7.0.1 Signed-off-by: Zang Ruochen Signed-off-by: Khem Raj --- .../python/python-backports-ssl_3.7.0.1.bb | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) create mode 100644 meta-python/recipes-devtools/python/python-backports-ssl_3.7.0.1.bb (limited to 'meta-python/recipes-devtools/python/python-backports-ssl_3.7.0.1.bb') diff --git a/meta-python/recipes-devtools/python/python-backports-ssl_3.7.0.1.bb b/meta-python/recipes-devtools/python/python-backports-ssl_3.7.0.1.bb new file mode 100644 index 0000000000..9032a7c1ed --- /dev/null +++ b/meta-python/recipes-devtools/python/python-backports-ssl_3.7.0.1.bb @@ -0,0 +1,18 @@ +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" + +LICENSE = "GPLv2" +LIC_FILES_CHKSUM = "file://PKG-INFO;md5=b2adbe8bfdeb625c9a01afd9aaa66619" + +SRC_URI[md5sum] = "32d2f593af01a046bec3d2f5181a420a" +SRC_URI[sha256sum] = "bb82e60f9fbf4c080eabd957c39f0641f0fc247d9a16e31e26d594d8f42b9fd2" + +PYPI_PACKAGE = "backports.ssl_match_hostname" +inherit pypi setuptools + +RDEPENDS_${PN} += "${PYTHON_PN}-pkgutil" -- cgit v1.2.3-54-g00ecf