| Key | Value |
|---|---|
| FileName | ./usr/lib/python2.7/dist-packages/websockify/__init__.py |
| FileSize | 53 |
| MD5 | 5494C296607DCFA9E17040D20FC75010 |
| SHA-1 | 6B9C67655E92290F7A2D8CD1357C432A08E5D924 |
| SHA-256 | DAB4C0885E8BFFE4B55363E4F88D14824A9F6024CFFCCB6AA6A13DCDBD25DD1A |
| SSDEEP | 3:1S1KGO06lDDo1KGO0A1IVQln:1CKGJ6lcKGJooQln |
| TLSH | T1419002D2413A148860FA834000101668363600D50F00D0DC00913A2846830610A00170 |
| tar:gname | root |
| tar:uname | root |
| hashlookup:parent-total | 27 |
| hashlookup:trust | 100 |
The searched file hash is included in 27 parent files which include package known and seen by metalookup. A sample is included below:
| Key | Value |
|---|---|
| FileSize | 37522 |
| MD5 | A6C473525C35A292B1C3A62DE2C42742 |
| PackageDescription | WebSockets 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. |
| PackageMaintainer | Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com> |
| PackageName | websockify |
| PackageSection | python |
| PackageVersion | 0.6.1+dfsg1-1 |
| SHA-1 | 25B37FBE5E9E96739AC29B095E617B96463D266A |
| SHA-256 | A7CB747C7E95B8D05F3B6A67D4CBC32BD007F9FF66EFC896EA94ACA0DC595B19 |
| Key | Value |
|---|---|
| MD5 | 6D008E943FA355DBB08DC9B358601D93 |
| PackageArch | noarch |
| PackageDescription | Python WSGI based adapter for the Websockets protocol |
| PackageMaintainer | Fedora Project |
| PackageName | python-websockify |
| PackageRelease | 1.fc22 |
| PackageVersion | 0.6.0 |
| SHA-1 | 264CE9B8511656DDC1A01C4DFC5E3669CEB3B3F6 |
| SHA-256 | 324287322121CC4B32D1943944CF1E17211E6FE7A888326611F0B98AF823093F |
| Key | Value |
|---|---|
| FileSize | 38104 |
| MD5 | 97497500A435289B5297D27B803525F4 |
| PackageDescription | WebSockets 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. |
| PackageMaintainer | PKG OpenStack <openstack-devel@lists.alioth.debian.org> |
| PackageName | websockify |
| PackageSection | python |
| PackageVersion | 0.6.0+dfsg1-1 |
| SHA-1 | 3B37080081E7E1C8C9AFF3E6E7EC48EA71A9DED4 |
| SHA-256 | BC7923BAB378AB3F34D8B7FB54009BB415A330A5E6A10FA6D5E915C4A811875E |
| Key | Value |
|---|---|
| FileName | http://mirror.math.princeton.edu/pub/blackarch/blackarch/os//x86_64//mosquito-39.fe54831-3-any.pkg.tar.xz |
| MD5 | 46303D1C924D147C5B58AC4CA3B9C53B |
| SHA-1 | 533C181A43F3B086202D8389F433CA75B3A9D62B |
| SHA-256 | ED28272EAF931D99497B3F3B87D09C49A9D0F3431C199C62DDAC90CF6D349D9B |
| SSDEEP | 393216:PmreBMK8smHPb2/wnk83VH6JhQg4BjJYiV:geWK8smv53V0/4B5 |
| TLSH | T167E6339BCF9D134F7F64700757F661242CB2B5CA9938942C5A29FB352B6D3C688C9C82 |
| Key | Value |
|---|---|
| FileSize | 35130 |
| MD5 | 0B43AC90B7E2307D0A955133B85372F2 |
| PackageDescription | WebSockets 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. |
| PackageMaintainer | Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com> |
| PackageName | websockify |
| PackageSection | python |
| PackageVersion | 0.5.1+dfsg1-3ubuntu0.14.04.1 |
| SHA-1 | 5DD09C39A266016F68554CE21A50750F9DCF4B97 |
| SHA-256 | 83DEDF5CE2F468FD8C73CFF27BA4FA7359B8C2D76DDAEDC73167C4EEAABBA54B |
| Key | Value |
|---|---|
| FileSize | 38484 |
| MD5 | E75115D77593C8E3E89678A042F60991 |
| PackageDescription | WebSockets 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. |
| PackageMaintainer | PKG OpenStack <openstack-devel@lists.alioth.debian.org> |
| PackageName | websockify |
| PackageSection | python |
| PackageVersion | 0.6.0+dfsg1-1 |
| SHA-1 | 5EEC2D9C8547824C06F893EED8FB768E2025B011 |
| SHA-256 | 456E1F514DC92C2EFBF7D46A15C50C1FE255BBF159E1BAC3F4C5AB12361E0263 |
| Key | Value |
|---|---|
| FileSize | 35028 |
| MD5 | 13B4C90D06132594CA6BD9F7713BB526 |
| PackageDescription | WebSockets 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. |
| PackageMaintainer | Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com> |
| PackageName | websockify |
| PackageSection | python |
| PackageVersion | 0.5.1+dfsg1-3 |
| SHA-1 | 66F093149ECEE489B29A32A1A3485CE6DC74FFBD |
| SHA-256 | A3DCEBB5C268893BBD2EACAFF1431C55050EE167A8AE408FCD80D3A732B077C9 |
| Key | Value |
|---|---|
| FileSize | 37872 |
| MD5 | A77ECBEA7A8DE81614656539C89453AD |
| PackageDescription | WebSockets 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. |
| PackageMaintainer | Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com> |
| PackageName | websockify |
| PackageSection | python |
| PackageVersion | 0.6.1+dfsg1-1ubuntu1 |
| SHA-1 | 7F463C60BDF4EB640277F3430D667F7ECDFFBC6E |
| SHA-256 | CF055FD44C401C15AC5977B3B016DB2B85FD3DA5B970E858A9A52C64FD06F50E |
| Key | Value |
|---|---|
| FileName | http://mirror.math.princeton.edu/pub/blackarch/blackarch/os//aarch64//mosquito-39.fe54831-3-any.pkg.tar.xz |
| MD5 | 5A2E87AE8C8E4E8D5CFDCD96F23B5616 |
| SHA-1 | 8216BA9BEE3ED1C825C59EDCFF19616A83E71A7A |
| SHA-256 | D1B98D40468B46B87B5170371A024FA295FAD53076A6B61F7954774B2D095C88 |
| SSDEEP | 393216:RgbQ4sxUTtLzE2PECTHMKXWPJW7+y8q8t7a:s3tLzEU/XWPJWMq8ta |
| TLSH | T1EEE633919702FDE5EC226DA09BCCF094D8F352C78D4BF16E2CD6606CA28976366F0E15 |
| Key | Value |
|---|---|
| FileSize | 35086 |
| MD5 | B1A0DA83885EDD1260670C6EA7981396 |
| PackageDescription | WebSockets 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. |
| PackageMaintainer | Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com> |
| PackageName | websockify |
| PackageSection | python |
| PackageVersion | 0.5.1+dfsg1-3ubuntu0.14.04.1 |
| SHA-1 | 887FE19ACA7BC89A1593D73FD8A697A7EA456488 |
| SHA-256 | 3B28EDF80D682AC3ACA495705B253B15663DE51A9B399CBC40454156F42622C4 |