Parents (Total: 13)

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

Key	Value
SHA-1	671BC04627C2FC07000550E27FF89D76B86809ED
snap-authority	canonical
snap-filename	wtnUl2mGUjjFg6QI4N7lLQYVmRZSiPDh_104.snap
snap-id	wtnUl2mGUjjFg6QI4N7lLQYVmRZSiPDh_104
snap-name	openstack-hypervisor
snap-publisher-id	canonical
snap-signkey	BWDEoaqyr25nF5SNCvEv2v7QnM9QsfCc0PBMYD_i2NGSQ32EF2d4D0hqUel3m8ul
snap-timestamp	2022-10-25T09:34:36.700100Z
source-url	https://api.snapcraft.io/api/v1/snaps/download/wtnUl2mGUjjFg6QI4N7lLQYVmRZSiPDh_104.snap

Key	Value
FileSize	44384
MD5	125EE50AC71C48F999B75392E4C2F177
PackageDescription	WebSockets 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.
PackageMaintainer	Debian OpenStack <team+openstack@tracker.debian.org>
PackageName	python3-websockify
PackageSection	python
PackageVersion	0.10.0+dfsg1-2
SHA-1	293ADC2F883716BD152C470C1DF281018282C825
SHA-256	F9EE6912B8440DBCBDED7E17DF45D7E785C7B92CBFF8E2B17C6DAF58E6A7C257

Key	Value
MD5	80CECA1B4568D12DA417F763D0AA8899
PackageArch	noarch
PackageDescription	WebSockets support for any application/server.
PackageMaintainer	umeabot <umeabot>
PackageName	python3-websockify
PackageRelease	2.mga9
PackageVersion	0.10.0
SHA-1	123F303BF6575F4C3653E356708C888749B082FF
SHA-256	047342699B29F2D14DECE77469F93D4163D39A6DB40DB0C0A221CEAAF8630E1B

Key	Value
FileSize	44384
MD5	A82C79E5489E205B9526D977AF4700DA
PackageDescription	WebSockets 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.
PackageMaintainer	Debian OpenStack <team+openstack@tracker.debian.org>
PackageName	python3-websockify
PackageSection	python
PackageVersion	0.10.0+dfsg1-2
SHA-1	4AC921B227B846805035B75DE7701304BD5F747D
SHA-256	33370BAC3518F915E0D43608F7C57433D20876FFA15AC250441735188EA61DAE

Key	Value
FileSize	44384
MD5	F0B8FEBCDF22DCA2684FB9AE02329BCE
PackageDescription	WebSockets 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.
PackageMaintainer	Debian OpenStack <team+openstack@tracker.debian.org>
PackageName	python3-websockify
PackageSection	python
PackageVersion	0.10.0+dfsg1-2
SHA-1	C740E3A8CC22DD74DCB2F49D0B6679B59EB20117
SHA-256	443ACB3E9C6D14B29CEC4D04C06EC7A3D4AFBCED6A06E9ACD8346B7C98203421

Key	Value
FileSize	44384
MD5	F82817E7D866F54C44DC485C830F9CE2
PackageDescription	WebSockets 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.
PackageMaintainer	Debian OpenStack <team+openstack@tracker.debian.org>
PackageName	python3-websockify
PackageSection	python
PackageVersion	0.10.0+dfsg1-2
SHA-1	F6157853AA665CC621794ABCA2F26CBE7852A32D
SHA-256	FDC8D1749E6A5DFAC99487CAC7C67A39215985ADFFDC1797C506D8793848AFE4

Key	Value
FileSize	44388
MD5	2870D077F259F843C79EDD83AFA6E2DB
PackageDescription	WebSockets 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.
PackageMaintainer	Debian OpenStack <team+openstack@tracker.debian.org>
PackageName	python3-websockify
PackageSection	python
PackageVersion	0.10.0+dfsg1-2
SHA-1	904717D179DF8C022667EBC006F2E361753D55BC
SHA-256	CB5D929BC33BDE8D9D33037B163F98451B318911ECF1DCFC97F715780B48F1FD

Key	Value
FileName	http://mirror.math.princeton.edu/pub/blackarch/blackarch/os//x86_64//websockify-888.dc34581-1-any.pkg.tar.zst
MD5	B4D2179F1B360ED4FBB34150025C4145
SHA-1	F4001B9E75680D85B53DA5F71F3876511A84D55B
SHA-256	BD67C027ED425375A91DD8AD199EDCF05AD1AA491F65C2A29226C15616979F5F
SSDEEP	1536:fEWdLmuB0mxRX/ukviZiiOlTulLYz9CHF0ipw5Pm3:VdiuB0mmCFlqCz8DKPm3
TLSH	T12A53027205DA646912DF8ECEE7089F2925451A374FF44EDEDEA255DFBDB380A18031A0

Key	Value
FileSize	44384
MD5	FB48706AC8EE98D9094D189D198756FF
PackageDescription	WebSockets 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.
PackageMaintainer	Debian OpenStack <team+openstack@tracker.debian.org>
PackageName	python3-websockify
PackageSection	python
PackageVersion	0.10.0+dfsg1-2
SHA-1	A39187E8AB007D24971AC1E6362B6011C3E65CC7
SHA-256	BAAFADD0F791E1AA6C5FA02D66777E8FE801D34584A44AB939F6F655255BD960

Key	Value
FileSize	44384
MD5	7925FAE529AEF7D4797F79EDC2EF8B4B
PackageDescription	WebSockets 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.
PackageMaintainer	Debian OpenStack <team+openstack@tracker.debian.org>
PackageName	python3-websockify
PackageSection	python
PackageVersion	0.10.0+dfsg1-2
SHA-1	5B3FB9FDC5CA4B593360EC9FBC4887B0A6BEE3CA
SHA-256	8CB7D5BE82AAB4698755AF4179F074AE89C9CDDBFFFC40DEE7E059D2ADC005B1

Key	Value
FileSize	44384
MD5	B809708C55427B2AC43CB660B433229F
PackageDescription	WebSockets 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.
PackageMaintainer	Debian OpenStack <team+openstack@tracker.debian.org>
PackageName	python3-websockify
PackageSection	python
PackageVersion	0.10.0+dfsg1-2
SHA-1	D662B60469155E7428C2A0D2D7CFCABC5709B969
SHA-256	4A667E15B011B9BA825E6C9D6A3FE14FE5E9867684631E27C8F6D5A0F19B648C

Key	Value
SHA-1	515B561E5D9E406FD50C5EFF30EA6E056772854C
snap-authority	canonical
snap-filename	wtnUl2mGUjjFg6QI4N7lLQYVmRZSiPDh_81.snap
snap-id	wtnUl2mGUjjFg6QI4N7lLQYVmRZSiPDh_81
snap-name	openstack-hypervisor
snap-publisher-id	canonical
snap-signkey	BWDEoaqyr25nF5SNCvEv2v7QnM9QsfCc0PBMYD_i2NGSQ32EF2d4D0hqUel3m8ul
snap-timestamp	2022-10-25T09:34:36.700100Z
source-url	https://api.snapcraft.io/api/v1/snaps/download/wtnUl2mGUjjFg6QI4N7lLQYVmRZSiPDh_81.snap

Key	Value
FileSize	44384
MD5	2D95142BD832C0EC6F9AF78286990978
PackageDescription	WebSockets 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.
PackageMaintainer	Debian OpenStack <team+openstack@tracker.debian.org>
PackageName	python3-websockify
PackageSection	python
PackageVersion	0.10.0+dfsg1-2
SHA-1	FA0A790360DDA5136DE5320E5D488DEBDF828337
SHA-256	E1052BC2CDE4973F4E2C76361A35C39426FFEF2A2ADD89DBBFD92BAE6083FC5D