Repository navigation
v2.35.0 — RCEKit on PyPI
RCEKit is now on PyPI.
pipx install rcekit # or: pip install rcekit
rcekit --doctorPublished 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 --doctorInstalling 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 rcekitno longer has side effects. Logging was configured at module
scope, andlogging.FileHandleropens its file the moment it is constructed —
so merely importing the module wrotercekit.loginto whatever directory the
interpreter happened to be in. Handler setup moved intoconfigure_logging(),
called frommain(). Running the CLI still writesrcekit.logexactly as
before. -
The built-in corpus is no longer reported as a missing file. With nothing
butrcekit.pythere is notemplates/directory, the embedded corpus is the
corpus, and the run is now silent about it —--doctornames it
built-in (embedded in rcekit.py)and reports OK. Atemplates/directory that
exists without itspayloads.jsonstill prints the notice, because that one
is a real finding. -
main()takes an optionalargvand returns an explicitint, so the
console-script entry point is a plain zero-argument call. Every exit code is
unchanged. -
The log file handler now runs at
DEBUGwhile the console stays atINFO.
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