| Key | Value |
|---|---|
| FileName | ./usr/lib/python2.7/site-packages/hyper/ssl_compat.pyo |
| FileSize | 11833 |
| MD5 | FCA481B284D07B5C31543F04059A2146 |
| SHA-1 | 1788DE6C6400D10E15F85ABAFAE6E003411E34BA |
| SHA-256 | F4DA98E0FF0DAE7AEAF4372FBF66B9B31A51405F8C4C8123A89009FA72E0F3C8 |
| SSDEEP | 192:8BxvFSmwb97TkY2vMjNIMa7bKl/enX1jH+ZiWh9nmfxKuf/nS2r/6JKgS21:B7AZvg/fl63Pr/6JKgS21 |
| TLSH | T179322280F7AA896BF9624535F2F0021BDA74F17357097BD12678987618DC3A9C83EBC1 |
| 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 | ECABFF93DFCDDFDF289C6A665DC06610 |
| 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 | python2-hyper |
| PackageRelease | lp151.19.1 |
| PackageVersion | 0.7.0+git88.18b629b |
| SHA-1 | 3B93F9614955E2B4AD7A1F36330081EB8F571C86 |
| SHA-256 | C503B2737920AA89E6F7216D297DE9C1CFAA234A9A6A404C76FD1CFCB5A83D1F |
| Key | Value |
|---|---|
| MD5 | 1AE56BE7B7F62FA50893D84313CA5D27 |
| 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 | python2-hyper |
| PackageRelease | 4.1 |
| PackageVersion | 0.7.0+git88.18b629b |
| SHA-1 | BDCAFB81E1C704079ECCAD0CD2C282D1DAA0EECC |
| SHA-256 | 0096195336D3DE39F42FD742604FE82B8E601B2731E4610357C6EED0F64D4F9A |
| Key | Value |
|---|---|
| MD5 | 86F3769B098DD2D843F3B6416AAC0A6D |
| 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 | python2-hyper |
| PackageRelease | lp150.4.1 |
| PackageVersion | 0.7.0+git88.18b629b |
| SHA-1 | A7C51535642BE5001B4720BD62B05F384FB28380 |
| SHA-256 | A634E4E114C29759A50F0508CC86DFFC6869E02A7F69A5805CA7035DCD5A9015 |