Result for 05C0888606589557AE7C0558BD2B95CC534E0594

Query result

Key Value
FileName./usr/share/doc/websockify/README.md.gz
FileSize2619
MD588616B6B2A6806E281FCCA95F116CCAC
SHA-105C0888606589557AE7C0558BD2B95CC534E0594
SHA-25683D51A680B44732C5F578BDF3F9F06E51C298D07E5C67ECA83F1C7DD8C1D599C
SSDEEP48:X2SMNj35//MkutDfYMRIuPQpRWAXhasNOu3HbYcqMmft7D2DirGSyCYWwq:mSMhp//YpVaRrhXNH3bY1Ms4SyCYWZ
TLSHT1DE513B85066D0BF3C39394B45D35AA8AA206D32006E5D2D78B21351C3EFA1DA9A6333A
hashlookup:parent-total4
hashlookup:trust70

Network graph view

Parents (Total: 4)

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

Key Value
FileSize35130
MD50B43AC90B7E2307D0A955133B85372F2
PackageDescriptionWebSockets support for any application/server 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.
PackageMaintainerUbuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageNamewebsockify
PackageSectionpython
PackageVersion0.5.1+dfsg1-3ubuntu0.14.04.1
SHA-15DD09C39A266016F68554CE21A50750F9DCF4B97
SHA-25683DEDF5CE2F468FD8C73CFF27BA4FA7359B8C2D76DDAEDC73167C4EEAABBA54B
Key Value
FileSize35028
MD513B4C90D06132594CA6BD9F7713BB526
PackageDescriptionWebSockets support for any application/server 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.
PackageMaintainerUbuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageNamewebsockify
PackageSectionpython
PackageVersion0.5.1+dfsg1-3
SHA-166F093149ECEE489B29A32A1A3485CE6DC74FFBD
SHA-256A3DCEBB5C268893BBD2EACAFF1431C55050EE167A8AE408FCD80D3A732B077C9
Key Value
FileSize35060
MD5CB5DBD4C65C11CEC215EA92E59E8F26C
PackageDescriptionWebSockets support for any application/server 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.
PackageMaintainerUbuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageNamewebsockify
PackageSectionpython
PackageVersion0.5.1+dfsg1-3
SHA-1A3C4AC23F55D6754165AB8926A2811F59E6544D6
SHA-256659D61ACE9BBE6C71A455B6B04730F49E0F52B72E05646B5B943BCF4937EA54D
Key Value
FileSize35086
MD5B1A0DA83885EDD1260670C6EA7981396
PackageDescriptionWebSockets support for any application/server 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.
PackageMaintainerUbuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageNamewebsockify
PackageSectionpython
PackageVersion0.5.1+dfsg1-3ubuntu0.14.04.1
SHA-1887FE19ACA7BC89A1593D73FD8A697A7EA456488
SHA-2563B28EDF80D682AC3ACA495705B253B15663DE51A9B399CBC40454156F42622C4