Result for 0801D44D0FCC16D07C61AA8035CAEECA9F7CD761

Query result

Key Value
CRC3210DA65B4
FileNamecopyright
FileSize20755
MD56160A1836EE265EAF568A8D919FAC637
OpSystemCode{'MfgCode': '1006', 'OpSystemCode': '362', 'OpSystemName': 'TBD', 'OpSystemVersion': 'none'}
ProductCode{'ApplicationType': 'Operating System', 'Language': 'English', 'MfgCode': '534', 'OpSystemCode': '599', 'ProductCode': '163573', 'ProductName': 'Netrunner', 'ProductVersion': '17.01'}
SHA-10801D44D0FCC16D07C61AA8035CAEECA9F7CD761
SHA-25631080D3DEA56489894C3599BF05542375EEED748C742CF6CC0DA0E357688BB88
SSDEEP384:HMIitKjGkrSBtGeHPKjGrFU6ym01J18IW6294+1wevzetFqpynVYtpopfYz1qckB:tdGkheHQGri66JGI5bFDnVQpoWgckB
SpecialCode
TLSHT1BC9276BE374813731AC202A67F4764DBF31AA03D767A50A4A09DC11C239BD7943B76E9
dbnsrl_modern_rds
insert-timestamp1646980714.0718374
sourceNSRL
hashlookup:parent-total31
hashlookup:trust100

Network graph view

Parents (Total: 31)

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

Key Value
FileSize31854
MD5C3741666DCDD47B85419207955F7FF84
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.
PackageMaintainerPKG OpenStack <openstack-devel@lists.alioth.debian.org>
PackageNamepython3-websockify
PackageSectionpython
PackageVersion0.8.0+dfsg1-7+deb9u1
SHA-100B59044FE7291A69C5AAA7D9BBCB380E199EF85
SHA-256FD59ACC7C2D3F5635D0B688E4A4FAFACD50859F796B6B5FB465CEFBA19EB691E
Key Value
FileSize24122
MD50BA565F58823E72B46D71634117E3C80
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.8.0+dfsg1-7+deb9u1
SHA-10E444D4A6D2D75C2E0D284538325327E7E51D36F
SHA-256737FFEAB9225EF2D08B4F2351282C7C3112A035DD66A2E01F498D7B2E0D4E331
Key Value
FileSize31838
MD52AE223F1B54D31EA6DACD95234D203F7
PackageDescriptionWebSockets support for any application/server - Python 2 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 2 module.
PackageMaintainerPKG OpenStack <openstack-devel@lists.alioth.debian.org>
PackageNamepython-websockify
PackageSectionpython
PackageVersion0.8.0+dfsg1-7+deb9u1
SHA-11D12FDB21A85349EBBB622B47DA7FD20CE309433
SHA-256C0874E46488B8D9024B6CB73F2925A7D9C404781BCB828262711DCB7EF27FF44
Key Value
FileSize29028
MD5DBF32D0A8D42373FBE64A284A5B42F8D
PackageDescriptionWebSockets support for any application/server - shared files 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 common files for Python 2 and 3 modules.
PackageMaintainerPKG OpenStack <openstack-devel@lists.alioth.debian.org>
PackageNamewebsockify-common
PackageSectionpython
PackageVersion0.8.0+dfsg1-7+deb9u1
SHA-122CBDC28E8103F8A808B04EE11509A24A958F7C1
SHA-256E29B5FA1D01FC97E5873E1F18ACC328349B6DC59A0A80FFE057D2B3B554D1B48
Key Value
FileSize24630
MD550D0EED5638A9932356AC31CF23F3E60
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.8.0+dfsg1-7+deb9u1
SHA-1258404F025365C9839D3268C56569A704B4445E5
SHA-2563223ADF471097C6F68FB6B689C7E4EBB724692F1B2C7325A9DEAB49F6F4B2FB5
Key Value
FileSize31838
MD53DD31EC83C91A765F841118F5742DD0A
PackageDescriptionWebSockets support for any application/server - Python 2 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 2 module.
PackageMaintainerPKG OpenStack <openstack-devel@lists.alioth.debian.org>
PackageNamepython-websockify
PackageSectionpython
PackageVersion0.8.0+dfsg1-7+deb9u1
SHA-12E8416FC1FA63E2390C9354F0E0A26C4C648CD81
SHA-2560325B1F6FFA143165B2B3A90B01746FB91FD9F36F9DBD59738F89295C1360210
Key Value
FileSize31856
MD505B6F70461BAEEDA273334398AB4C322
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.
PackageMaintainerPKG OpenStack <openstack-devel@lists.alioth.debian.org>
PackageNamepython3-websockify
PackageSectionpython
PackageVersion0.8.0+dfsg1-7+deb9u1
SHA-1309B698B8F3D914AECA10166AC34EB46B1D95ADC
SHA-256A170C3272DF5EBC7BB8179B14F70E9418C96ACC52552A5C26C65CFDD6747FB3C
Key Value
FileSize24086
MD58DC66C7189A1D54BF48773CB5891D813
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.8.0+dfsg1-7+deb9u1
SHA-132F20852735AFCAB53EA2CEAB4C1160941CC785F
SHA-2563D40CD371EFF27189184A215DA81294FC7612F08106DD841A46E3FE6B717E26E
Key Value
FileSize31852
MD5DBD06CE5B9FB011E13E20724BA72723F
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.
PackageMaintainerPKG OpenStack <openstack-devel@lists.alioth.debian.org>
PackageNamepython3-websockify
PackageSectionpython
PackageVersion0.8.0+dfsg1-7+deb9u1
SHA-13332DEB374FCB38B5C404201880AA9B84CA99655
SHA-256F3C7DA60969B8B85BF961CFA1CC0B8F4956A07AD2EE26A277FDA9A23EDD39F81
Key Value
FileSize31854
MD5AE08971CF170E76B06E25B48C3386070
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.
PackageMaintainerPKG OpenStack <openstack-devel@lists.alioth.debian.org>
PackageNamepython3-websockify
PackageSectionpython
PackageVersion0.8.0+dfsg1-7+deb9u1
SHA-1337221C35665F0FE780AA5948233174ECE912902
SHA-256CF6AB2B011F1DFB9276F0341C20989204BFBC35582A797F31F5761FB1B3E3BD7