Key | Value |
---|---|
FileName | ./usr/lib/python3.10/site-packages/hyper/common/__pycache__/connection.cpython-310.pyc |
FileSize | 5377 |
MD5 | B6CEED2F8691121BBD37609ECF2EA581 |
SHA-1 | 0D25FD00EB91664C938AB414C0721DE372155496 |
SHA-256 | BAAB37CEE2E5A317974618287B5A8DFF33C92375476FEF6F809D67B180A699E2 |
SSDEEP | 96:PA2WNTq2weBlw1MurxPoA1KKBRL0TzGAKKoL6cOD+:2NbwS4KKBRL0nql6C |
TLSH | T122B1A88EA1457262FB57F174211BC7508339462B238C250079AC96ED6F7FAE4E4A3AC9 |
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 | 3721DBB009D682D11321543A388FBA68 |
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 | python310-hyper |
PackageRelease | 22.1 |
PackageVersion | 0.7.0+git89.b77e758 |
SHA-1 | D0CE28693B655A6F347079CEAF94ED8227D5ACF1 |
SHA-256 | 06C28CCAE91D9A5E206CB3ECE02316FD64B5F04CD55965522950AC60E86D96F6 |
Key | Value |
---|---|
MD5 | 9CA3A84844BA6CB920EEB0E3BC2FCC0C |
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 | python310-hyper |
PackageRelease | 22.1 |
PackageVersion | 0.7.0+git89.b77e758 |
SHA-1 | D5BF05AFDCFB182FBCAA9E63630E79CB80B9CBB6 |
SHA-256 | 70EE56AC121ED00425D8341EF94355C696DF65B629B2B4E74EDD7D1806A4F1B4 |
Key | Value |
---|---|
MD5 | DF7CC9D68A0AA662173AF5344AC0ADF3 |
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 | python310-hyper |
PackageRelease | 22.1 |
PackageVersion | 0.7.0+git89.b77e758 |
SHA-1 | FDDCA6E0F05E5C0C7F111D46E5D8C3D6566037CE |
SHA-256 | D40E5C4050925101A7BFD4242246C0B634196266C96FF57C0E0D7FA5F0F542B5 |