diff options
-rw-r--r-- | meta-python/recipes-devtools/python/python-backports-ssl_3.4.0.2.bb | 23 |
1 files changed, 23 insertions, 0 deletions
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 000000000..9caae41bf --- /dev/null +++ b/meta-python/recipes-devtools/python/python-backports-ssl_3.4.0.2.bb | |||
@@ -0,0 +1,23 @@ | |||
1 | SUMMARY = "The ssl.match_hostname() function from Python 3.4" | ||
2 | DESCRIPTION = "The Secure Sockets layer is only actually secure if you check the hostname in the \ | ||
3 | certificate returned by the server to which you are connecting, and verify that it matches to hostname \ | ||
4 | that you are trying to reach. But the matching logic, defined in RFC2818, can be a bit tricky to implement \ | ||
5 | on your own. So the ssl package in the Standard Library of Python 3.2 and greater now includes a \ | ||
6 | match_hostname() function for performing this check instead of requiring every application to \ | ||
7 | implement the check separately. This backport brings match_hostname() to users of earlier versions of Python" | ||
8 | HOMEPAGE = "https://pypi.python.org/pypi/backports.ssl_match_hostname" | ||
9 | SECTION = "devel/python" | ||
10 | |||
11 | LICENSE = "GPLv2" | ||
12 | LIC_FILES_CHKSUM = "file://PKG-INFO;md5=77b684960b86b7a4bb4a450ffde08605" | ||
13 | |||
14 | SRCNAME = "backports.ssl_match_hostname" | ||
15 | |||
16 | SRC_URI = "https://pypi.python.org/packages/source/b/${SRCNAME}/${SRCNAME}-${PV}.tar.gz" | ||
17 | |||
18 | SRC_URI[md5sum] = "788214f20214c64631f0859dc79f23c6" | ||
19 | SRC_URI[sha256sum] = "07410e7fb09aab7bdaf5e618de66c3dac84e2e3d628352814dc4c37de321d6ae" | ||
20 | |||
21 | S = "${WORKDIR}/${SRCNAME}-${PV}" | ||
22 | |||
23 | inherit setuptools | ||