Result for 60B17A2D2C1C0F6EA2EFFCDAF037F92026EFC9F2

Query result

Key Value
FileName./usr/share/doc/python3-websockify/changelog.Debian.gz
FileSize1129
MD5738BC6368518C0BE12D9EE0EDADB5347
SHA-160B17A2D2C1C0F6EA2EFFCDAF037F92026EFC9F2
SHA-25640F7F7EF47F7314BC1A8EEC6CF92EDDCA62CC7513304805F302EE7A8B5854A24
SSDEEP24:X8p7bvhTpj8cG93YdG+u9/KmPmFUBIwy6Q4szm5zdvY5pUhfCtwJZjAu:XObhtjw5Ym/5mFlar5h7hfqOZjb
TLSHT1E821F91D54105EC2D0CC270DC8853E95FC071EA9DB11A126CF70BC3134230BC5796338
hashlookup:parent-total6
hashlookup:trust80

Network graph view

Parents (Total: 6)

The searched file hash is included in 6 parent files which include package known and seen by metalookup. A sample is included below:

Key Value
FileSize30052
MD58FF7B5DDF13ADAA331D8C88DAB32A3F0
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-10ubuntu2
SHA-1515473CFE1CD1AF5593F80906D8B4EDED856C1CA
SHA-2562FE6DC09E933A2B5123766FA9E586FD9C8F7DA91C94EC4CE80518EFEB1BB144B
Key Value
FileSize30052
MD51419A9C98B0996DF02A60E221B35E91C
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-10ubuntu2
SHA-1EB2AA37186F6EF47401106373E771BD60102D022
SHA-256E8E1D47A45E3D8CF38F4DF363DEB820E236658D3B0FE6B28C27F0A033B15D2D4
Key Value
FileSize30052
MD5CF437DB9A150412EB414B519184F4496
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-10ubuntu2
SHA-19DB595F32C5AB886C27EC502B43A32B9B943DD4D
SHA-256731B8C9B2B662EFB5A1340A07DB64C9871FAE461F4846D8E94CF8C746B670668
Key Value
FileSize30048
MD55A0C679FB7854A2A61C7ED537E1B130F
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-10ubuntu2
SHA-1DFB8005D190738CE5075BD2E69F068B1417B36E5
SHA-256FFADE8D21F9BA9F878F88CC1A9DFB867BB56D667BB7762EE52D1874C68CCBDE0
Key Value
FileSize30052
MD5BACF7EE03D7D96DC1EAB9BE1AF1E735A
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-10ubuntu2
SHA-10942F94BAE37B68459DEDD97C76FE440B40D8101
SHA-25662380043F3FC5A6E4811E5FC2DDA2593CD7090B5CBD5886CB999E2A6301F5A38
Key Value
FileSize30048
MD55EA7B9F71DC8896D100960B62F7B6391
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-10ubuntu2
SHA-15EEC8FC4429D49915552D3FDB371E32C0D865406
SHA-2566CD286B21B0F1EC2910B6AC130822C09CC1E9E33FF14BB7CF5A379FE4059FEC8