Result for 95A66DA57BC39FEDF7C5A3BE90BAACC904C344AC

Query result

Key Value
FileName./usr/lib/python2.7/dist-packages/websockify/websocketproxy.py
FileSize17667
MD5392012E9F9434ED8094FB7F8A91FF506
SHA-195A66DA57BC39FEDF7C5A3BE90BAACC904C344AC
SHA-256D640C7C6B48067557C2B6E1BA66F4B4388FCB3F3C3D0DFF89E44921336215B30
SSDEEP384:4SoO9YBV4GHttuxdBi6Xq9MPV6ptto/AEWW:RV+3/ux/i669YwVFEWW
TLSHT14C82B702691625EA63F78A955E56EB03270A15C36B0B103C7DBCA3C52F41531A2F7FBD
hashlookup:parent-total16
hashlookup:trust100

Network graph view

Parents (Total: 16)

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

Key Value
FileSize37522
MD5A6C473525C35A292B1C3A62DE2C42742
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.6.1+dfsg1-1
SHA-125B37FBE5E9E96739AC29B095E617B96463D266A
SHA-256A7CB747C7E95B8D05F3B6A67D4CBC32BD007F9FF66EFC896EA94ACA0DC595B19
Key Value
MD56D008E943FA355DBB08DC9B358601D93
PackageArchnoarch
PackageDescriptionPython WSGI based adapter for the Websockets protocol
PackageMaintainerFedora Project
PackageNamepython-websockify
PackageRelease1.fc22
PackageVersion0.6.0
SHA-1264CE9B8511656DDC1A01C4DFC5E3669CEB3B3F6
SHA-256324287322121CC4B32D1943944CF1E17211E6FE7A888326611F0B98AF823093F
Key Value
FileSize38104
MD597497500A435289B5297D27B803525F4
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.
PackageMaintainerPKG OpenStack <openstack-devel@lists.alioth.debian.org>
PackageNamewebsockify
PackageSectionpython
PackageVersion0.6.0+dfsg1-1
SHA-13B37080081E7E1C8C9AFF3E6E7EC48EA71A9DED4
SHA-256BC7923BAB378AB3F34D8B7FB54009BB415A330A5E6A10FA6D5E915C4A811875E
Key Value
FileSize38484
MD5E75115D77593C8E3E89678A042F60991
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.
PackageMaintainerPKG OpenStack <openstack-devel@lists.alioth.debian.org>
PackageNamewebsockify
PackageSectionpython
PackageVersion0.6.0+dfsg1-1
SHA-15EEC2D9C8547824C06F893EED8FB768E2025B011
SHA-256456E1F514DC92C2EFBF7D46A15C50C1FE255BBF159E1BAC3F4C5AB12361E0263
Key Value
FileSize37872
MD5A77ECBEA7A8DE81614656539C89453AD
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.6.1+dfsg1-1ubuntu1
SHA-17F463C60BDF4EB640277F3430D667F7ECDFFBC6E
SHA-256CF055FD44C401C15AC5977B3B016DB2B85FD3DA5B970E858A9A52C64FD06F50E
Key Value
MD52C665FF6A7B54DA19D6650187720C5E3
PackageArchnoarch
PackageDescriptionPython WSGI based adapter for the Websockets protocol
PackageMaintainerFedora Project
PackageNamepython-websockify
PackageRelease3.fc23
PackageVersion0.6.0
SHA-1897E39C5ACEA992C2E11E618D7EE10577C6B14ED
SHA-256D69175B1D7F839E375664D7CBDA19392BD48E0627C45E33D0670FD077C02B4E1
Key Value
MD599DAF24EEC0938D13C1C145EF50288F7
PackageArchnoarch
PackageDescriptionPython WSGI based adapter for the Websockets protocol
PackageMaintainerFedora Project
PackageNamepython-websockify
PackageRelease3.fc23
PackageVersion0.6.0
SHA-19D69E00876F3DAEFD9731C91098F7744667CEFBF
SHA-256CEED474A70E22F7E4B9AAD081838E8DB8DA63A529C01F7962636796B0288AF7B
Key Value
MD576DD66318AFB8969DE1A914A7A9207AC
PackageArchnoarch
PackageDescriptionPython WSGI based adapter for the Websockets protocol
PackageMaintainerFedora Project
PackageNamepython-websockify
PackageRelease3.fc23
PackageVersion0.6.0
SHA-1ADC73B7E210686954344226AD651481B2AED1707
SHA-256A87435DAA72DBB8D75442735DA2C178E4713F1C3C881C84CB900235D9C2CD2B4
Key Value
FileSize37978
MD58B42A1D51593FA05062F761157D0F9DA
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.6.1+dfsg1-1ubuntu1
SHA-1BD34E689B79DB6CD86420873E394A1268A05F1B9
SHA-2560352D53D6BB435603C36B5EC16F9202072CB868F6CE7B3F66E19BC52BEA8ED3B
Key Value
FileSize38326
MD58456929A924E8D76EA32DB234A6E468E
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.
PackageMaintainerPKG OpenStack <openstack-devel@lists.alioth.debian.org>
PackageNamewebsockify
PackageSectionpython
PackageVersion0.6.0+dfsg1-1
SHA-1DADF919C88A3C36A0978B2A74BA87095239D0AFE
SHA-256ADC8622F4A2C53816E9CB04F9CE0B93808C551E9B5A0994ACC21614ED3DA1F17