Parents (Total: 114)

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

Key	Value
FileName	https://ftp.lysator.liu.se/pub/OpenBSD/6.3/packages//arm//websockify-0.8.0.tgz
MD5	C8440AC4B3A2A3FFB87400381A04B5E5
SHA-1	00A5877ACE7AFE303CDE03B542FF6CE91C062A3F
SHA-256	51C0705035A341DA09CC9FA6DF83ADDC42938829DCF3DF216F267B7E651F6D43
SSDEEP	6144:nDGyahyf2BsjsbwyAO5TxBjAeYrSTuSJC:DDaMftWwA7+WTuSJC
TLSH	T17134234BE87660F5DAAA632947AA2D8067FD5C4C9B37CB7047A580E6DCE0C41C5C2D8B

Key	Value
FileSize	31854
MD5	C3741666DCDD47B85419207955F7FF84
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	PKG OpenStack <openstack-devel@lists.alioth.debian.org>
PackageName	python3-websockify
PackageSection	python
PackageVersion	0.8.0+dfsg1-7+deb9u1
SHA-1	00B59044FE7291A69C5AAA7D9BBCB380E199EF85
SHA-256	FD59ACC7C2D3F5635D0B688E4A4FAFACD50859F796B6B5FB465CEFBA19EB691E

Key	Value
FileName	https://ftp.lysator.liu.se/pub/OpenBSD/6.5/packages//arm//websockify-0.8.0.tgz
MD5	44DF1BD52948016776018643F30EE40A
SHA-1	04A212D1747D20BB50B487F4722446CC563513C4
SHA-256	94C927B4BD45E82453E925DBEBC0744069F27BF7A88FA16173D26C403D3EEECF
SSDEEP	3072:MAhA3p4QJ2WBtwpTlCgKJ6KjuwoltariCO53xAiDKQ3BOvYSZAeEKEJHuk2tuTpX:MAhDQzMlUsbwIAO5vxBuAeYRyuTn5
TLSH	T1E534235BACB284EEC64266751F7F3998309FCC4CEBBF90B4420282D78D51E21C792A5D

Key	Value
FileName	https://ftp.lysator.liu.se/pub/OpenBSD/6.1/packages//i386//websockify-0.8.0.tgz
MD5	8F6CF61E6867F4B075B30F38338F770D
SHA-1	074333CCC63C26BFF12E46B606CD0A5531E7B41E
SHA-256	1D0B001EF9C9EAC6FC9706ACED1BE24AE13F6AD3D50C36648D28432B22DA4C5E
SSDEEP	3072:KHYrbXjA62Y0UeEAJ6KjuwWltariCO53xASDKQ3BOvYhUID65jAL0IVcarH5Y:KH2f29U7AsbwqAO5DxBhdWApVcarZY
TLSH	T1FD341346A86363C59263AD4107FFE16A08FC98D8AB3728F0436742737DF5C16D4D2CAA

Key	Value
FileSize	32028
MD5	F8128856DCCECA01E1C95301FA31554E
PackageDescription	WebSockets 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.
PackageMaintainer	Debian OpenStack <openstack-devel@lists.alioth.debian.org>
PackageName	python-websockify
PackageSection	python
PackageVersion	0.8.0+dfsg1-10
SHA-1	07EC0CF334E9E1D2F559E5FE88D3F041FF37E916
SHA-256	AFF60A057C7A3DFBCBFEB1DB334E4AB8C67FC50EF172FE63AA07B870DAF0F93D

Key	Value
FileSize	30052
MD5	BACF7EE03D7D96DC1EAB9BE1AF1E735A
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	Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageName	python3-websockify
PackageSection	python
PackageVersion	0.8.0+dfsg1-10ubuntu2
SHA-1	0942F94BAE37B68459DEDD97C76FE440B40D8101
SHA-256	62380043F3FC5A6E4811E5FC2DDA2593CD7090B5CBD5886CB999E2A6301F5A38

Key	Value
MD5	2FD27204DACA32DED7F758F5F9576A66
PackageArch	noarch
PackageDescription	WebSockets support for any application/server.
PackageMaintainer	wally <wally>
PackageName	python-websockify
PackageRelease	1.mga7
PackageVersion	0.8.0
SHA-1	0E8CEC602332DE9526E414FD0C8A2E12DE97FACE
SHA-256	50E42D1148603C5DF84902F56E97B55EE1C847F0F832D70742B7285087DBF370

Key	Value
FileName	https://ftp.lysator.liu.se/pub/OpenBSD/6.3/packages//amd64//websockify-0.8.0.tgz
MD5	65C4630AB2C2922B5B6181C09BEA2D0A
SHA-1	0F13CC3CD16673211590B13E39595809D01820EB
SHA-256	13638FB454CF32633E406888B7857A02BCE75985015698666814798D48353AA1
SSDEEP	6144:KhNA/rbPDT8XvXavFXesbw6AO5XxBRdvfyGjQjZMX:KhNSf36vq9XBws5Z+jeX
TLSH	T13D3423D8E4637E7BDB42507A43BF7A6D4AF9D46D9F3338A0542A42D19435C03A4C1F8A

Key	Value
FileName	https://ftp.lysator.liu.se/pub/OpenBSD/6.5/packages//amd64//websockify-0.8.0.tgz
MD5	3B7A4835C1D8FE6833AF8C3AA5CA16C6
SHA-1	148DE4F540045D1DDF701F9EF1B9AB02826AA04E
SHA-256	890B7B3912A51C12F7EE5F1562DE62D5A5C127F9128B6B35E2EAE395ED455C7C
SSDEEP	3072:PMPeA+iJ6KjuwQltariCO53xAaDKQ3BOvYKG0LJHRSfDFU2zBaWFgZYFx:UnFsbwgAO5vxBKG0VAJU2a4giv
TLSH	T1C63423D348B6328EC0F1A99D03DF1469B4DC3C6ADB3768F0D35D42B7A697802E891E16

Key	Value
FileSize	32108
MD5	6DE9F5A4AFF92DD4D5E99AF669B41ACF
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 <openstack-devel@lists.alioth.debian.org>
PackageName	python3-websockify
PackageSection	python
PackageVersion	0.8.0+dfsg1-10
SHA-1	15F49C84E46B3608C39F85E88822ED14F736D057
SHA-256	8F46C39BA1DFE8A033E3F30B17FAE96B0B922770268EABC6DB71A8E91C31A649