Remote code execution endpoint
Some nice to haves left to implement.
- Monospace font on the command output.
- Error handling.
- Tests.
Deploying a remote code execution endpoint
Drop into a shell and sing the magic incantation pip install rcee and rcee.
This will leave you haunted with an endpoint lingering on port 7999 by default.
From this point onward you're on your own and can perform any request you want.
It's also possible to use pipx for the installation.
1 maintainer
Metadata
1 maintainer
Release files for rcee 0.0.4
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 | Actions |
|---|---|---|---|---|
| rcee-0.0.4.tar.gz | 8.9 kB | Without provenance | Details for rcee-0.0.4.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| rcee-0.0.4-py3-none-any.whl | Python 3 | none | any | Details for rcee-0.0.4-py3-none-any.whl |
Total release size: 16.1 kB
Release files / rcee-0.0.4.tar.gz
| Download URL | rcee-0.0.4.tar.gz |
|---|---|
| Size | 8.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2bcb1e2417a8cb61ab164a624bc697461c633e3a3cb2dc7a65ff13dadf204644
|
|
BLAKE2b-256 checksum How to use checksums |
445c86bab5058d821510f6e3d465037f68227fa969b610dfb7c77e00e1029cde
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.11.8
|
Release files / rcee-0.0.4-py3-none-any.whl
| Download URL | rcee-0.0.4-py3-none-any.whl |
|---|---|
| Size | 7.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
efb1c17e599d808172bc3363fc2ef1293fdf9c6d98b724fe2c2085b8de4adfa6
|
|
BLAKE2b-256 checksum How to use checksums |
0d42f3ac0bb92b785d974d9c796e8c75a405578426a23c4e497469dee6ed4174
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.11.8
|
Security for rcee 0.0.4
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.
