Result for EFE3D0F4610C14F6F135D8DCD2D2CAB6251B4834

Query result

Key Value
FileName./usr/share/doc/python3-websockify/changelog.Debian.gz
FileSize1210
MD57A32493904C6CBA34B0CA236DC05B44D
SHA-1EFE3D0F4610C14F6F135D8DCD2D2CAB6251B4834
SHA-2569DE1C74D0496B9E97793E050A963C61636B478C98DA11699E60D87215F1DCC2E
SSDEEP24:XyyvaZAavb94ntwiO57mSnN83EQ3VbWYjYbWNKvt2TmeeHLXc:XyyMvbOtxO5ayiEQYA20KtpeKs
TLSHT19821DAF79A1BA8BDD45EE78E98F4315434017C50FC0F7FE5BA857107A90743C51A9280
hashlookup:parent-total2
hashlookup:trust60

Network graph view

Parents (Total: 2)

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
FileSize30140
MD527CA936ABE0D92894A4C2DB1FE1DF869
PackageDescriptionWebSockets support for any application/server - Python 3 websockify was formerly named wsproxy and was part of the noVNC project. . At the most basic level, websockify just translates WebSockets traffic to normal socket traffic. Websockify accepts the WebSockets handshake, parses it, and then begins forwarding traffic between the client and the target in both directions. . Websockify supports all versions of the WebSockets protocol (Hixie and HyBi). The older Hixie versions of the protocol only support UTF-8 text payloads. In order to transport binary data over UTF-8 an encoding must used to encapsulate the data within UTF-8. . With Hixie clients, Websockify uses base64 to encode all traffic to and from the client. This does not affect the data between websockify and the server. . With HyBi clients, websockify negotiates whether to base64 encode traffic to and from the client via the subprotocol header (Sec-WebSocket-Protocol). The valid subprotocol values are 'binary' and 'base64' and if the client sends both then the server (the Python implementation) will prefer 'binary'. The 'binary' subprotocol indicates that the data will be sent raw using binary WebSocket frames. Some HyBi clients (such as the Flash fallback and older Chrome and iOS versions) do not support binary data which is why the negotiation is necessary. . This package provides the Python 3 module.
PackageMaintainerUbuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageNamepython3-websockify
PackageSectionpython
PackageVersion0.8.0+dfsg1-9
SHA-11D7C867D1796646FE8F1F7CC06FD8E5D2DD9150A
SHA-256662E6F3518F3CA802EF9EAD38E67F4A65F58025DAF6CCC293BE162FA062758E6
Key Value
FileSize30136
MD5EBCB454D2229A2F086C32A5E5D46BE69
PackageDescriptionWebSockets support for any application/server - Python 3 websockify was formerly named wsproxy and was part of the noVNC project. . At the most basic level, websockify just translates WebSockets traffic to normal socket traffic. Websockify accepts the WebSockets handshake, parses it, and then begins forwarding traffic between the client and the target in both directions. . Websockify supports all versions of the WebSockets protocol (Hixie and HyBi). The older Hixie versions of the protocol only support UTF-8 text payloads. In order to transport binary data over UTF-8 an encoding must used to encapsulate the data within UTF-8. . With Hixie clients, Websockify uses base64 to encode all traffic to and from the client. This does not affect the data between websockify and the server. . With HyBi clients, websockify negotiates whether to base64 encode traffic to and from the client via the subprotocol header (Sec-WebSocket-Protocol). The valid subprotocol values are 'binary' and 'base64' and if the client sends both then the server (the Python implementation) will prefer 'binary'. The 'binary' subprotocol indicates that the data will be sent raw using binary WebSocket frames. Some HyBi clients (such as the Flash fallback and older Chrome and iOS versions) do not support binary data which is why the negotiation is necessary. . This package provides the Python 3 module.
PackageMaintainerUbuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageNamepython3-websockify
PackageSectionpython
PackageVersion0.8.0+dfsg1-9
SHA-14DA1117639606A414C31E1033302C855E575AD55
SHA-2567098F84F1C6CB56D746E2EED29C09FA315F662CD36A2D457669F960FC18D4AF9