Skip to content

v2.35.0 — RCEKit on PyPI

Choose a tag to compare

@kabiri-labs kabiri-labs released this 20 Aug 16:00
· 171 commits to main since this release

RCEKit is now on PyPI.

pipx install rcekit     # or: pip install rcekit
rcekit --doctor

Published through PyPI Trusted Publishing from this release — no API token, no
repository secret.

It is still one file

The distribution is a single module, not a package tree. rcekit.py has not
moved and still runs alone:

curl -O https://raw.githubusercontent.com/kabiri-labs/rcekit/main/rcekit.py
python rcekit.py --doctor

Installing is a second supported shape, not a replacement for the first. Running
with nothing installed is the point on a jump box or an air-gapped host, and both
paths run the same code and report the same verdicts.

Changed

  • import rcekit no longer has side effects. Logging was configured at module
    scope, and logging.FileHandler opens its file the moment it is constructed —
    so merely importing the module wrote rcekit.log into whatever directory the
    interpreter happened to be in. Handler setup moved into configure_logging(),
    called from main(). Running the CLI still writes rcekit.log exactly as
    before.

  • The built-in corpus is no longer reported as a missing file. With nothing
    but rcekit.py there is no templates/ directory, the embedded corpus is the
    corpus, and the run is now silent about it — --doctor names it
    built-in (embedded in rcekit.py) and reports OK. A templates/ directory that
    exists without its payloads.json still prints the notice, because that one
    is a real finding.

  • main() takes an optional argv and returns an explicit int, so the
    console-script entry point is a plain zero-argument call. Every exit code is
    unchanged.

  • The log file handler now runs at DEBUG while the console stays at INFO.

Unchanged, and verified so

Nothing about detection changed. Measured against v2.34.1 on a repo checkout:
--doctor output identical, exit codes identical across
--version / --doctor / --detection-only, and 252 generated payloads from
both. 77 of those lines differ — and running v2.34.1 twice against itself differs
on exactly the same 77, because payloads carry per-run random canary tokens.

A corpus that is present but corrupt, and an explicit --template-file that is
missing or corrupt, both still refuse to run and exit non-zero.

The one thing an existing user can observe: in the single-file layout the
[i] Using the built-in payload corpus line no longer prints. The information is
still there — --doctor reports the source.

Full changelog: v2.34.1...v2.35.0