This release is a pre-release and may not be stable for production use.
scapy-unroot
Daemon and tooling to enable using scapy without root permissions.
Installation
scapy_unroot can be installed by just running
pip install
The requirements also installed by this are listed in
requirements.txt.
Usage
The scapy-unroot daemon
The daemon to allow usage of scapy without root permissions requires root itself. You can start it with the following command:
sudo scapy-unroot scapy
The provided argument scapy should be a permission group, users who are
allowed to use scapy without root permissions should be in.
By default, all files related to scapy_unroot are managed in the directory
/var/run/scapy-unroot. You can change that directory using the -r /
--run-dir argument:
sudo scapy-unroot --run-dir /tmp scapy
The UNIX domain socket to communicate with the daemon will be created under the
name server-socket in that directory.
Network interfaces that users of scapy_unroot should not be able to send over
or sniff on can be blacklisted using the -b / --interface-blacklist
argument. Multiple interfaces can be provided:
sudo scapy-unroot scapy --interface-blacklist wlan0 eth0 lo
To run the daemon in background, use the -d / --daemonize parameter:
sudo scapy-unroot -d scapy
To get more information on the arguments of the scapy-unroot daemon, run
sudo scapy-unroot -h
All arguments described above can be combined.
Configuring scapy to communicate with the daemon
Before sending or sniffing with scapy, just do
from scapy_unroot import configure_sockets
configure_sockets()
You can provide a different server address by the server_addr argument. The
default is /var/run/scapy_unroot/server-socket.
You can also configure the timeout for waiting for a reply from the server using the connection_timeout argument.
Metadata
Release files for scapy-unroot 0.3.0b4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| scapy_unroot-0.3.0b4.tar.gz | 8.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| scapy_unroot-0.3.0b4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 39.3 kB
Release files / scapy_unroot-0.3.0b4.tar.gz
| Download URL | scapy_unroot-0.3.0b4.tar.gz |
|---|---|
| Size | 8.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9dc80bbf7f441380a6ddb16e903cf06db24ca858d6eea868c10629d0d8d5f3e6
|
|
BLAKE2b-256 checksum How to use checksums |
363bf007bf6daa7b40a51a09ad6254e38f7ef9ef498309c91eb6bdc7afcf983b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.23.0 setuptools/46.1.3 requests-toolbelt/0.9.1 tqdm/4.45.0 CPython/3.8.2
|
Release files / scapy_unroot-0.3.0b4-py3-none-any.whl
| Download URL | scapy_unroot-0.3.0b4-py3-none-any.whl |
|---|---|
| Size | 30.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
424c891e16af5befcfc8c6862e2b059dd580fca49c05ff2339637e8465f95309
|
|
BLAKE2b-256 checksum How to use checksums |
f883d32454b18507f82b9a63d6f8af54d91daa4f9715f835b49e35e173104438
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.23.0 setuptools/46.1.3 requests-toolbelt/0.9.1 tqdm/4.45.0 CPython/3.8.2
|
Security for scapy-unroot 0.3.0b4
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.