Security and Linux developers
Trace the desktop interface, restricted system helper, per-action authorization, audit path, and recovery lockout.
LSMF Community Preview
Inspect Linux hardening changes before they reach your system
LSMF is an experimental, community-first framework for people evaluating explicit, reviewable, and recoverable Linux hardening workflows—not a promise of one-click safety.
Built for careful evaluation
For people who inspect before they trust
LSMF is opening early so its boundaries, recovery model, documentation, packaging, and claims can be challenged—not so untested users will install it on important systems.
Disposable-VM evaluators
Reproduce bounded checks, report the exact image and artifact, and keep observations within the evidence.
Potential contributors
Strengthen tests, documentation, accessibility, packaging, and recovery behavior while keeping every limitation visible.
Operating principles
Caution built into the workflow
Bounded privilege
The Qt desktop stays unprivileged. Privileged requests cross a typed, fixed, default-deny helper boundary with per-action authorization.
Recoverable changes
The project emphasizes backup-first mutation, exact rollback, durable recovery, bounded output, and protected audit records.
Evidence before claims
Source checks, package inspection, and isolated VM evidence are distinct. Mocks or successful process launches do not replace VM evidence.
Privilege architecture
An ordinary-user interface with a narrow system boundary
Qt is the only graphical interface; the application has no browser or HTTP control surface. A source checkout does not install, register, enable, or start the privileged helper.
Unprivileged QtReview and request
Typed helper boundaryDefault deny and authorize per action
Evidence ledger
Specific results, kept in their proper scope
Four Bash module scripts cover Secure Shell (SSH), firewall, network, and kernel hardening. The exact current candidate combines them with an unprivileged desktop interface and a narrow system helper.
- 226 / 226Python tests passed (CI, 2026-09-09)
- 9 / 9Shell tests passed
- PassedSource, dependency, privacy, claim, headless Qt, and .deb package checks
- RecordedDisconnect, concurrency, crash-recovery, reboot, and Polkit prompt-matrix scenarios passed on a disposable Ubuntu clone
Important status
Know the limits before evaluating LSMF
- LSMF is not production-ready.
- Workstation or production installation is not approved.
- Live hardening and rollback belong only in explicitly disposable systems.
- Any running request — audit, verification, apply, or rollback — can be cancelled from the desktop; cancellation is delivered on the helper's own connection.
- Debian, Linux Mint, and other distributions are not currently supported.
- A changed binary requires its own applicable verification.
Transparency is part of the product
Start with evidence, limitations, and source
The public repository ships the code, claim matrix, VM evidence records, security policy, AI-assistance disclosure, licensing notices, and known limitations together.
Reviewing source and automated checks can inform an evaluation, but neither establishes production safety. Live testing belongs only in explicitly disposable systems.
ReviewTrace a security boundary and report concrete, reproducible concerns.
ReproduceRepeat the documented disposable-VM evidence with exact image and artifact details.
ImproveStrengthen tests, documentation, accessibility, packaging, or recovery behavior.
Repository status: Public at github.com/jessMyself/LSMF. Source is MIT-licensed; see the repository security policy before reporting an issue.