The owner deleted their ledger and found GIRLS' FRONTLINE 2 "Not eligible: 0 successful hooked
session(s), two are needed" - for good. D33's rule was a catch-22 for every game it could meet
again: since beta.8 the library sweep blocks a game the moment it is added, a blocked game is
never hooked without a grant (CaptureSession sends it to Tier 2 before the resolver), so it could
never earn the two sessions, and a reset ledger lost the ones it had. Asked with that (2026-10-03),
the owner chose D38: a grant needs no session; the first two hooked sessions under it are a trial;
any end during the trial ends the exception for good.
Agent / Application:
- UserModeExceptionRules: TrialSessions = 2 replaces RequiredSessions; IsEligible(block, verdict,
trialFailed) - the guard's answer and the trial mark, no count; InTrial(successfulBefore).
- UserModeExceptionLapse.TrialFailed; UserModeExceptionLapsePolicy judges a session against the
grant in force: during its trial every D33 end, or a stored hooked session with no frames or an
abnormal exit, revokes it with trialFailed; a session too short to store, or never hooked, is
not judged. The recorder passes the row it stored (SessionForTrial).
- ISessionRepository.CountSuccessfulUnderGrantAsync (family + started >= grant) replaces
CountSuccessfulHookedAsync; ac_exception_sessions is now the trial's progress.
- AgentCommandHandler: TooFewSessions is gone; a game whose trial failed is refused before
anything is scanned (Refused TrialFailed, signal = unix ms). AntiCheatExceptionCommands drops
the session repository.
- The sweep answers a blocked entry whose executable cannot be read ("PreScanFailed", no bytes in
the key) instead of leaving it "Checking..." for ever.
Infrastructure: schema 0017 games.ac_exception_trial_failed_at; the revoke sets it once
(COALESCE), eligibility is never written eligible over it and a grant is refused over it, both in
SQL; Change executable does not name it; a twin merge keeps the earlier mark.
App: the disclosure is ac-exception-dialog/2 (Why names no count, a Trial paragraph); the card
says "trial: N of 2", a failed trial "none can be made again", a scan that found nothing "was not
found" (not "could not finish"); an eligible game's Anti-cheat card no longer says "cannot be
turned on" beside Make exception...; the Settings list shows only games it can act on, without
the duplicated count, and Refresh only while a row is checking. Strings en/vi/ja (ja safety text
English until reviewed).
Docs and legal: CLAUDE.md rule 2 amendment, 19_SAFETY, FR-2.8, 06_DATA_MODEL (0017), 07_IPC,
08_UI, 20_OPEN_QUESTIONS, LIMITATIONS, SECURITY, the accuracy block (README, Disclaimer),
Disclaimer 2.9 (2A), EULA 1.4, CHANGELOG.
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
5.1 KiB
Security policy
FrameLedger loads a component into game processes that the user has individually enabled, and it refuses to do so when it detects anti-cheat or anti-tamper software. Two kinds of report matter here, and they take different routes.
A vulnerability in FrameLedger
Anything that could let FrameLedger be used against the person running it or against a third party: a way to make the Agent inject into a process the user did not enable, a way past the anti-cheat guard, a way to make the hook read or write game memory it does not own, a way to make the App or Agent execute something from an untrusted source, a privacy leak (data leaving the machine, or the bug bundle carrying what the privacy policy says it does not).
Report it privately. Use GitHub's private vulnerability reporting on this repository when it is enabled (Security ▸ Report a vulnerability); otherwise e-mail contact@poli0981.dev. Please do not open a public issue for a vulnerability until a fix has shipped.
What helps: the version (Help ▸ About, or FrameLedger.exe --diag), the steps, and what you observed.
What to leave out: instructions for defeating any anti-cheat system — FrameLedger needs to know what
to refuse, never how to evade (docs/19_SAFETY_AND_ANTICHEAT.md).
This is a one-person project. The intent is to acknowledge a private report within a week and to say plainly what will happen next; that is an intent, not a contractual response time.
The guard has no override
For two pre-releases (0.1.0-beta.3 and beta.4) a user could overrule the anti-cheat guard for one game through a
disclosure. That switch was withdrawn on 2026-09-22 (docs/19_SAFETY_AND_ANTICHEAT.md §What a finding does to the game): a finding
now turns the game's hooking off. What IS a security report: any way to reach an injection past a refusal — a flag, a
setting, a crafted rules file, a pipe message, a database edit the Agent honours — or a finding about a game that
does not turn its hooking off.
Since 0.1.0-beta.9 one narrow exception exists (owner decision D33, docs/19_SAFETY_AND_ANTICHEAT.md §The user-mode
exception): per game, only for one anti-cheat family that is user-mode throughout, with the guard still running every
check. The grant is a record in your own database, like the consent stamp; what keeps it narrow is the guard, which
decides itself which family it may let through. So these are security reports too: the guard letting through a family
that has a driver, a service or a .sys in the floor or the rules; an exception applying to a game with a kernel
driver in its folder, on a title list, or with a second anti-cheat; the Agent writing a grant on a pipe message
without its own tolerant pre-scan; an exception that survives a new finding, a crash or safety stop under it, or a
changed executable; since 0.1.0-beta.11 (D38), an exception that survives a session during its two-session trial that
did not go well, and any grant written for a game whose earlier exception failed its trial; and the Overlay tolerating
a family the guard did not.
Running the agent as administrator
Since 0.1.0-beta.10 the capture agent can run as administrator — an option, off by default (owner decision D34,
docs/01_ARCHITECTURE.md ADR-9) — and Windows asks at every start of the agent. The residual risk is stated to the user
rather than solved: FrameLedger installs per user and unsigned, so a program running under the same account could replace
its files and be run as administrator when the user next accepts the prompt. What IS a security report: any way the
agent becomes administrator WITHOUT that prompt (a task, a service, an inherited token the option did not choose); a game
or any other program that an elevated agent starts with its own token instead of the desktop shell's; any privilege the
agent enables (none is — tools/chokepoint-check.ps1 forbids the enablers under src/); an elevated agent that runs for
another account than the one that asked; and a named object an elevated agent creates that the same user's unelevated
processes can no longer open, or that another user can.
A safety gap — a game with anti-cheat that FrameLedger fails to detect
This is treated with the same priority as a security report, and it takes the public route: open
an issue with the Safety gap form (.github/ISSUE_TEMPLATE/safety_gap.yml). Blocklist entries are
data (rules/detection-rules.json), so the fix is small — but the software has no rules-update path
yet, so a fix reaches installed copies only with the next release (README §Reporting a safety gap
says the same, and docs/20_OPEN_QUESTIONS.md §S20 carries the feed that would change it).
Scope notes
- Releases are not code-signed;
SHA256SUMS.txtis published beside every asset (docs/11_UPDATER.md§Unsigned releases). A report that an installer's hash does not match what the release lists is a security report. - The evasion techniques FrameLedger will never implement are listed in
docs/19_SAFETY_AND_ANTICHEAT.md. A pull request that makes FrameLedger harder for anti-cheat to see is declined on principle, not reviewed for quality.