| Key | Value |
|---|---|
| FileName | ./usr/lib/python2.7/site-packages/backports.ssl_match_hostname-3.4.0.2-py2.7.egg-info/SOURCES.txt |
| FileSize | 401 |
| MD5 | 21F1ED6AB4580F3F228E76B43B15DE6F |
| SHA-1 | 5B1C5C8C13064F05E6FB73840605EB58FAE1DCB6 |
| SHA-256 | C15DD4F8ED6DB3D631D17401E7DB53F8D186B5C6474B0E924F355F39ED41E3B0 |
| SSDEEP | 12:1x0Q++SXRCMXRCdXRCGjXRCid7XRC9RUQc:f0Q+JXRhXRyXRhjXRxd7XRCRUh |
| TLSH | T180E0ED7F923FF68B23A2F48CE36F83117E9BE1B39C4194E196520348B0D48505D1B654 |
| hashlookup:parent-total | 9 |
| hashlookup:trust | 95 |
The searched file hash is included in 9 parent files which include package known and seen by metalookup. A sample is included below:
| Key | Value |
|---|---|
| MD5 | 162008329E647B913A943E8B1FC33B55 |
| PackageArch | noarch |
| PackageDescription | 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 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. The actual code inside comes verbatim from Python 3.2. |
| PackageMaintainer | Fedora Project |
| PackageName | python-backports-ssl_match_hostname |
| PackageRelease | 4.fc21 |
| PackageVersion | 3.4.0.2 |
| SHA-1 | E0D12AF7B34372C590AFFC82605F12C76FD3A7B9 |
| SHA-256 | E7709D878B74A70C2784FB43DA60278BFF5385DE86746F5B1A6A2307064E3CA1 |
| Key | Value |
|---|---|
| MD5 | B71A76F827CC0EEFCF3868F31369529A |
| PackageArch | noarch |
| PackageDescription | 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 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. The actual code inside comes verbatim from Python 3.2. |
| PackageMaintainer | Fedora Project |
| PackageName | python-backports-ssl_match_hostname |
| PackageRelease | 4.fc21 |
| PackageVersion | 3.4.0.2 |
| SHA-1 | 9A7DE6C564DC53B620F5F5C981CE556696381A60 |
| SHA-256 | E0B845E722FB30C8127F4AC10E6E9CE30821F047476AA684F8CA3B8802B83404 |
| Key | Value |
|---|---|
| MD5 | 88884CAEAD1BE42FA8D3917918556453 |
| PackageArch | noarch |
| PackageDescription | 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 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. The actual code inside comes verbatim from Python 3.2. |
| PackageMaintainer | Fedora Project |
| PackageName | python-backports-ssl_match_hostname |
| PackageRelease | 4.fc22 |
| PackageVersion | 3.4.0.2 |
| SHA-1 | 53710B6ACAECA400A6707A1BCBE19CBFBC2168F4 |
| SHA-256 | CBC0E1942B91CAC3E1FCC95EBD660EF713D437C60DFDF6FF153B086FD7876161 |
| Key | Value |
|---|---|
| MD5 | 90B3BA947FEFDA00A34E39371860E28A |
| PackageArch | noarch |
| PackageDescription | 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 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. The actual code inside comes verbatim from Python 3.2. |
| PackageMaintainer | Fedora Project |
| PackageName | python-backports-ssl_match_hostname |
| PackageRelease | 4.fc21 |
| PackageVersion | 3.4.0.2 |
| SHA-1 | 63C14D7896CEA6A0E873A9CDEC025F206301E77B |
| SHA-256 | 73E6CEDD7E88E1F1AA0C83636C46D8C0FED9821D71078EC7C12DFE7D9902F733 |
| Key | Value |
|---|---|
| MD5 | A7F896864EF4CDEC890286EFB26AE720 |
| PackageArch | noarch |
| PackageDescription | 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 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. The actual code inside comes verbatim from Python 3.2. |
| PackageMaintainer | Fedora Project |
| PackageName | python-backports-ssl_match_hostname |
| PackageRelease | 4.fc22 |
| PackageVersion | 3.4.0.2 |
| SHA-1 | 406E6424CAADCC839D0CB927E1ABEF14D3288CFE |
| SHA-256 | E241DA541B838C65783EFA9FF62A0B6DF4452CA088EB7521DFE807227F269979 |
| Key | Value |
|---|---|
| MD5 | 08B6E225214F06742E5EDCA76461FDE7 |
| PackageArch | noarch |
| PackageDescription | 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 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. The actual code inside comes verbatim from Python 3.2. |
| PackageMaintainer | Fedora Project |
| PackageName | python-backports-ssl_match_hostname |
| PackageRelease | 4.fc22 |
| PackageVersion | 3.4.0.2 |
| SHA-1 | 64938307FBACCC6F6F9234499E37E8B255AF9E01 |
| SHA-256 | 7F5B7F818B801D86AC84F34A3C09694655C9A6F5301D591F975383F886F820E7 |
| Key | Value |
|---|---|
| MD5 | E534C79840D59C06C25A78BA412C7B98 |
| PackageArch | noarch |
| PackageDescription | 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 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. The actual code inside comes verbatim from Python 3.2. |
| PackageMaintainer | Fedora Project |
| PackageName | python-backports-ssl_match_hostname |
| PackageRelease | 4.fc22 |
| PackageVersion | 3.4.0.2 |
| SHA-1 | F8DEBB1CE2F606BD936E344883E1408DB6C3079B |
| SHA-256 | 5BB495EFE95BDAFCAF14E22CDBE0898E820464792CF9400566D3F5328568E28C |
| Key | Value |
|---|---|
| MD5 | 96869692F504F67328670246608F0B37 |
| PackageArch | noarch |
| PackageDescription | 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 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. The actual code inside comes verbatim from Python 3.2. |
| PackageMaintainer | Fedora Project |
| PackageName | python-backports-ssl_match_hostname |
| PackageRelease | 4.fc22 |
| PackageVersion | 3.4.0.2 |
| SHA-1 | 69BF68530E28A1EC65D27AEC55DC557734CCA442 |
| SHA-256 | A6A0E003E85D2EDC9E2C54406F371FEFB64CEBA5912D4DDD789A86F92FC15103 |
| Key | Value |
|---|---|
| MD5 | 6AADF79A982C5257C04A8FAA075FAD7C |
| PackageArch | noarch |
| PackageDescription | 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 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. The actual code inside comes verbatim from Python 3.2. |
| PackageMaintainer | Fedora Project |
| PackageName | python-backports-ssl_match_hostname |
| PackageRelease | 4.fc22 |
| PackageVersion | 3.4.0.2 |
| SHA-1 | FF36A738D5BFFA0B6F9C8855050B1D6417B26CB2 |
| SHA-256 | E81DEC5D16558FBDB145094A09826D085A7DEC9CA6EC8C6D5CE9A249F7A5C2F7 |