How to Install and Uninstall websockify Package on Kali Linux
Last updated: December 23,2024
1. Install "websockify" package
Please follow the guidance below to install websockify on Kali Linux
$
sudo apt update
Copied
$
sudo apt install
websockify
Copied
2. Uninstall "websockify" package
This is a short guide on how to uninstall websockify on Kali Linux:
$
sudo apt remove
websockify
Copied
$
sudo apt autoclean && sudo apt autoremove
Copied
3. Information about the websockify package on Kali Linux
Package: websockify
Version: 0.10.0+dfsg1-5
Installed-Size: 70
Maintainer: Debian OpenStack
Architecture: amd64
Depends: python3-jwcrypto, python3-numpy, python3-websockify (>= 0.10.0+dfsg1-5), python3 (<< 3.12), python3 (>= 3.11~), libc6 (>= 2.34)
Size: 22564
SHA256: 2dd6c4f0451950ee9fd23a30cdd048225fda6cc6a2d697005739d29931329ea2
SHA1: 957d45ecb41248ff1729f34a140adac40d5eac82
MD5sum: ecb975e1a604f03dccf19d317e41e37a
Description: 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.
Description-md5:
Homepage: https://pypi.python.org/pypi/websockify
Section: python
Priority: optional
Filename: pool/main/w/websockify/websockify_0.10.0+dfsg1-5_amd64.deb
Version: 0.10.0+dfsg1-5
Installed-Size: 70
Maintainer: Debian OpenStack
Architecture: amd64
Depends: python3-jwcrypto, python3-numpy, python3-websockify (>= 0.10.0+dfsg1-5), python3 (<< 3.12), python3 (>= 3.11~), libc6 (>= 2.34)
Size: 22564
SHA256: 2dd6c4f0451950ee9fd23a30cdd048225fda6cc6a2d697005739d29931329ea2
SHA1: 957d45ecb41248ff1729f34a140adac40d5eac82
MD5sum: ecb975e1a604f03dccf19d317e41e37a
Description: 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.
Description-md5:
Homepage: https://pypi.python.org/pypi/websockify
Section: python
Priority: optional
Filename: pool/main/w/websockify/websockify_0.10.0+dfsg1-5_amd64.deb