Research & Field Notes
Technical investigations, security observations, experiments, and engineering notes from the JediSecX lab. This page summarizes what the linked public repositories document; project claims remain subject to testing and review.
Repository evidence
The summaries below are drawn from each repository’s current README. The linked repositories are the source of truth for code, changes, dependencies, and release status.
MAC5000 — Modular Experimental Platform (Rev. C)
Documented: Rev. C separates the early Searle/rotor experimental path from the liquid-metal magnetohydrodynamic (MHD) path, with a conventional electromagnetic reference listed as future work. The README identifies the MHD module as the primary current focus and includes a preliminary parameter sweep and supporting design documents.
Important limitation: the README says magnetic-field drive power is still unquantified and that 500 kW is a target, not a prediction. The Searle/rotor path is explicitly treated as a testable hypothesis; no anomalous energy production is assumed.
IP Scanner for Exploited PDFs + Temporary Firewall
Documented: the Python scanner searches PDF bytes for IP addresses and ranges, then probes recovered targets for commonly exposed ports using sockets and threading. A separate temporary firewall script can add tagged iptables rules based on scan results and remove its own rules with its flush option.
Requirements and limits: the README specifies Python 3.8+, with Linux and iptables needed for the firewall module; elevated privileges are required for firewall changes. The README also notes that results depend on the PDF containing recoverable addresses and on the configured known offsets. Use only on files and systems you are authorized to analyze.
PDF Exploit Scanner + Patcher (08xf)
Documented: the README describes three defensive components: a static scanner for high-risk PDF indicators, a structural patcher intended to remove risky keys and actions while retaining text and images, and a full sanitizer that rasterizes pages and rebuilds a visual-only PDF.
Trade-off to note: the README says the full sanitizer loses selectable text. It lists Python packages and Poppler utilities as dependencies and frames the toolkit for defensive research. Treat sanitization as a risk-reduction step, not a guarantee that every possible threat has been eliminated.
How we document findings
- Question: State what is being investigated and why it matters.
- Method: Describe the environment, inputs, steps, and version details.
- Evidence: Separate observations and measurements from interpretation.
- Limitations: Record uncertainty, edge cases, and what the test does not establish.
- Reproduction: Link source, tests, and supporting materials when available.
Lab principle: claims should be testable, uncertainty should be visible, and evidence should survive scrutiny. These summaries reflect README documentation; they do not independently establish successful builds, benchmark results, or hardware performance.