| Key | Value |
|---|---|
| FileName | ./usr/lib/python3.8/site-packages/hyper/__pycache__/tls.cpython-38.pyc |
| FileSize | 3998 |
| MD5 | C2EE126B501A014899E59F454C7465F6 |
| SHA-1 | 2C350C8B4D331A47F08DC0D317B2F97F21B22308 |
| SHA-256 | 3707648AE804985EE30193FC92C6B39A321E49D4B3B5B89EEB247B27835416D1 |
| SSDEEP | 96:xdGWiLCxpEjhb/21ZEpKcSxga9W5t/LYYLvwtH3nsR:xdGWiiajhy1ZEpKcSxg+wt/L7LvwtHXm |
| TLSH | T17181B55AB8955F39FE026370D50A81E0A72D817F632D841A789CD28C1FF6DA0D27A7CD |
| hashlookup:parent-total | 3 |
| hashlookup:trust | 65 |
The searched file hash is included in 3 parent files which include package known and seen by metalookup. A sample is included below:
| Key | Value |
|---|---|
| MD5 | D65F069CF43D2DA4587DD88381293A40 |
| PackageArch | armv7hl |
| 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 | python38-hyper |
| PackageRelease | 27.2 |
| PackageVersion | 0.7.0+git88.18b629b |
| SHA-1 | 170E5BC1F3AEB893E706FB7611C7C4AA977ED25B |
| SHA-256 | B7636DF11E69A857937F28740F7367B26E09B8F083430F63781B8C5CBB9308FB |
| 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 |