| Key | Value |
|---|---|
| FileName | ./usr/lib/python3.8/site-packages/hyper/__pycache__/ssl_compat.cpython-38.pyc |
| FileSize | 9565 |
| MD5 | 2C0C7BC5E998DC3B077C865E70B06966 |
| SHA-1 | 268419512D6F5AD9584F70550B9DDC6C383AF6E7 |
| SHA-256 | D9BB4A87B775B47BEF98E16B5AE306EFA8B4B3751EB2C07E9963318EA1329C84 |
| SSDEEP | 192:l9ftxdjKkwlMMOMFTxrk54lMuWMU61Pt/qCvAUEFrjXTkzEpybDdS3OIy30:Lftx5hwDOMFTVU6Kbh3230 |
| TLSH | T1A91270DDAE439D6BFF71F2FA40441250A35AD376B3D9D63B0930D09A2EC92C85FA4588 |
| hashlookup:parent-total | 2 |
| hashlookup:trust | 60 |
The searched file hash is included in 2 parent files which include package known and seen by metalookup. A sample is included below:
| Key | Value |
|---|---|
| MD5 | 0194DCC0D0138FDAF7BB9A0AADCE2BCF |
| PackageArch | x86_64 |
| PackageDescription | hyper supports the final draft of the HTTP/2 specification: additionally, it provides support for drafts 14, 15, and 16 of the HTTP/2 specification. It also supports the final draft of the HPACK specification. hyper is intended to be a drop-in replacement for http.client, with a similar API. However, hyper intentionally does not name its classes the same way http.client does. This is because most servers do not support HTTP/2 at this time: I don't want you accidentally using hyper when you wanted http.client. |
| PackageName | python3-hyper |
| PackageRelease | 5.4 |
| PackageVersion | 0.7.0+git88.18b629b |
| SHA-1 | EE2B4B530D63A98FFA824EDF4F19B6F168C45D27 |
| SHA-256 | 95FE73F3732D0B9D3902B9C5DD1A8AB905B74BDCA6605511EA39A7D437F6CC5B |
| Key | Value |
|---|---|
| MD5 | 90B6C13527ED658F186955D3090003D1 |
| PackageArch | i586 |
| PackageDescription | hyper supports the final draft of the HTTP/2 specification: additionally, it provides support for drafts 14, 15, and 16 of the HTTP/2 specification. It also supports the final draft of the HPACK specification. hyper is intended to be a drop-in replacement for http.client, with a similar API. However, hyper intentionally does not name its classes the same way http.client does. This is because most servers do not support HTTP/2 at this time: I don't want you accidentally using hyper when you wanted http.client. |
| PackageName | python3-hyper |
| PackageRelease | 5.4 |
| PackageVersion | 0.7.0+git88.18b629b |
| SHA-1 | 33350A3F029B1B4232ED956213916893674A6D97 |
| SHA-256 | BAC62FD10BB43D329B2AB972DFA0700260374DEA5C44B7823766CE8C73D83617 |