Commit Graph
960 Commits
Author SHA1 Message Date
protonmatter 134562c3d9 Drop the unused database import and align the password constants. 2026-11-17 22:54:16 +01:00
protonmatter 7cac9c240b Retry the password version on login when startup could not read it. 2026-11-17 22:54:16 +01:00
protonmatter ebc54b8751 Bind sessions to a password version so revocation cannot tie inside one second.
The hash and version commit together, a failed read rejects tokens, and the reset script tells the operator to restart.
2026-11-17 22:54:16 +01:00
protonmatter 26a7bbec37 Reject sessions issued before a password change.
A failed password read no longer mints a setup token, and filling the login limiter no longer drops an active lockout.
2026-11-17 22:54:16 +01:00
BaaRai 8ae53f74cf Merge pull request #306 from Protonmatter/protonmatter/mitm-passthrough-ttl
Expire MITM passthrough after one minute
2026-11-17 22:14:58 +01:00
BaaRai 03ac1c7d47 Merge pull request #300 from Protonmatter/protonmatter/shutdown-outbox
Drain task goroutines on shutdown and replay unsaved activities
2026-11-17 22:08:25 +01:00
protonmatter 287cbb685c Treat an expired passthrough mark as intercepted again, and say what the window costs.
Replay was still honoring a stale bypass, and a host whose interception always fails now loses one request per minute instead of one per process.
2026-11-17 15:58:24 -05:00
protonmatter a1c6103cbf Stop admitting work before the drain and replay each outbox row once.
The listener closes before Wait, and a shutdown refuses new task operations. Wait also stays until detached runs finish. The activity insert and the outbox delete commit together, and a row that keeps failing is dropped after five attempts so it cannot block the rest.
2026-11-17 15:41:56 -05:00
BaaRai 56d11bb51c Merge pull request #290 from Coff0xc/fix/rsi-lesson-retract
fix(db): retract lesson evidence when a disposition reverses
2026-11-17 20:30:19 +01:00
Coff0xc c73fec7471 fix(db): look up caution lessons by cue
The caution action carries the vulnclass, not the finding summary.
2026-11-17 19:13:32 +00:00
Coff0xc 0fb4ed145d fix(db): retract every retest when a finding is reversed
The negative path only dropped the latest retest. Operator-retired
lessons with evidence also came back on the next extract.
2026-11-17 19:13:31 +00:00
Coff0xc c0ce7a9494 fix(db): retract lesson evidence when a disposition reverses
Re-extract after flipping a finding to false_positive left the old
positive lesson in place.
2026-11-17 19:13:19 +00:00
BaaRai 758bc416dd Merge pull request #307 from BaaRai/chore/contributing-pr-cap
docs: cap contributors at 7 open pull requests, and have the bot say so
2026-11-17 20:11:38 +01:00
BaaRai 28363ec3e5 docs: document the 7 open pull request cap 2026-11-17 20:06:36 +01:00
BaaRai d4c1a5cca1 Merge pull request #298 from BaaRai/feat-bulk-finding-status
feat(findings): bulk status update from the findings table
2026-11-17 19:58:49 +01:00
BaaRai 72f3b0c3af Merge pull request #287 from Coff0xc/fix/rsi-lesson-correctness
fix(db): scope RSI lessons from task_scope and stop splitting UTF-8
2026-11-17 19:58:45 +01:00
Coff0xc a2b26f5416 fix(db): skip RSI lesson extract on multi-company tasks
NULL company_id leaked those lessons to every later task.
2026-11-17 18:08:49 +00:00
protonmatter 0234025d28 Drain task goroutines on shutdown and replay activities that could not be stored.
The outbox migration is 0006 because 0005 is already traffic rewrite rules. A shutdown cancel leaves an in-flight intent claim running, so the next start can reset it to open instead of recording the interrupt as done or blocked.
2026-11-17 13:05:23 -05:00
protonmatter 08eb4ec244 Expire a MITM passthrough mark after one minute.
A host that cannot be intercepted is tunneled until the mark expires, then interception is tried again.
2026-11-17 13:04:37 -05:00
Coff0xc cc0082cfda fix(db): scope RSI lessons from task_scope and stop splitting UTF-8
Lessons were scoped on tasks.company_id, which create never writes.
Generic rows also sorted first on Postgres.
2026-11-17 18:03:10 +00:00
BaaRai 75efc29323 feat(findings): bulk status update from the findings table 2026-11-17 17:52:09 +01:00
BaaRai 6337341602 Merge pull request #295 from BaaRai/feat-keenable-wiring
feat(web_search): wire the opt-in Keenable backend
2026-11-17 17:39:38 +01:00
BaaRai b452b13989 feat(web_search): wire the opt-in Keenable backend 2026-11-17 17:22:35 +01:00
BaaRai 0ec264ddeb Merge pull request #294 from BaaRai/bump-norma-v0.4.11
chore(deps): bump Norma to v0.4.11
2026-11-17 17:22:24 +01:00
BaaRai 9ad28841a6 chore(deps): bump Norma to v0.4.11 2026-11-17 17:09:22 +01:00
BaaRai ea59a8aea5 Merge pull request #252 from renaesop/codex/upload-500mib
fix: support 512 MiB task and chat attachments
2026-11-17 16:22:43 +01:00
BaaRai a4d61da200 Merge pull request #279 from cyberd4ch/ci/stable-toolchain-check
ci: run the suite on the latest Go release as an advisory job
2026-11-17 15:47:22 +01:00
BaaRai 3992eb700b Merge pull request #284 from cocodedk/fix/llm-key-autofill-model-search
web(llm): keep password managers out of the API key field; add model search
2026-11-17 15:47:18 +01:00
BaaRai 7a160a154b Merge pull request #288 from Coff0xc/fix/rsi-lesson-envelope
fix(agent): frame RSI lessons in the data envelope
2026-11-17 15:47:14 +01:00
BaaRai c14626ecee Merge pull request #289 from Coff0xc/fix/finding-disposition-node
fix(db): mirror finding triage onto the exploration node
2026-11-17 15:45:54 +01:00
BaaRai f33e3d14f2 Merge pull request #286 from Coff0xc/fix/llmpool-window-tokens
fix(server): use the real context window for llmpool and sidequestion
2026-11-17 15:45:50 +01:00
BaaRai 2d21da1a7d Merge pull request #278 from cyberd4ch/fix/decode-fixture-toolchain-independent
test: make the gzip fixture compressible on every toolchain
2026-11-17 15:45:34 +01:00
Coff0xc 90947ec5e3 fix(db): mirror finding triage onto the exploration node
false_positive only updated the findings row. Agents still saw
confirmed on the exploration node.
2026-11-17 12:56:23 +00:00
Coff0xc 59cd4385ec fix(agent): frame RSI lessons in the data envelope
Lesson text was dumped straight into the system prompt. Same nonce
envelope as the other derived fields now.
2026-11-17 12:56:19 +00:00
Coff0xc 14b93cecab fix(server): use the real context window for llmpool and sidequestion
8K/16K profiles were treated as 32K because WindowTokens came from
CompactionWindow(). They 400 and don't fail over.
2026-11-17 12:56:13 +00:00
Babak Bandpey c8e41e437b web(llm): keep password managers out of the API key field; add model search
The profile drawer's API Key input is a masked field with no autocomplete
hint, so browsers and password managers treat it as this site's login
password: they fill it when the drawer opens and Save then persists the
wrong secret over the key already stored in the profile. Mark the field
new-password and add the 1Password/Bitwarden ignore hints, matching the
setup page's convention.

The loaded model list can hold several hundred entries (OpenRouter: 470),
which is unusable without filtering. Add a search input above the list
with a case-insensitive substring match, a "no model matches" state, and
reset it whenever the list is reloaded or the popover closes.
2026-11-17 10:21:10 +01:00
dach-a fa33d4dac0 test: assert compression by size, not by looking for a word
The plaintext-substring guard encoded one encoder's output shape: it only held
while a small input compressed to fewer bytes than it started with, and Go
1.27 stores instead. Comparing sizes states the same invariant without
assuming how flate picks between stored and compressed blocks: a stored block
is larger than its input by construction, so "output is under half the input"
is true for any working encoder on a repetitive body and false for a body that
was never compressed.

Checked against the old 60-byte fixture on go1.27.4: it fails with "fixture is
not compressed: 60 bytes in, 85 bytes out", so the guard still catches the
case it was written for.
2026-11-17 03:49:25 +00:00
dach-a 909243fd37 ci: run the suite on the latest Go release as an advisory job
The go job tests only the toolchain go.mod pins, so a newer Go can break the
suite without a repository change: Go 1.27's compress/flate started emitting a
stored block for a 60-byte input, and TestDecodeEvidenceBodyGzipQuoteFound
failed on its own "fixture is not compressed" guard (#276).

go-stable runs the same build, vet and -p 1 test commands against whatever
release is current, with the same postgres service. It is continue-on-error
because a toolchain release is not a change to this repository and should not
block an unrelated merge on the day it lands; the log still carries the
failure, and dropping that line makes it a required check once the pinned
floor moves.
2026-11-17 03:40:00 +00:00
dach-a 25816c7fd6 test: make the gzip fixture compressible on every toolchain
TestDecodeEvidenceBodyGzipQuoteFound built its body from the 60-byte
decodeHTML constant and guarded with "the stream must not contain admin".
That assumes the encoder always deflates, and Go 1.27's flate does not: for
this input it emits a stored block, the stream is 85 bytes, and the raw bytes
are the plaintext the guard rejects. The test then fails on the encoder's
choice rather than on the decode it is meant to cover.

Repeat the body so it has something to compress, and assert the decoded
output equals it, so the guard measures the round trip instead of one
encoder's block selection. The quote and the body's content are unchanged,
and the sibling truncated/deflate tests already use repeated input.
2026-11-17 03:31:36 +00:00
Chubboy Ren 99a0d27f88 fix: enforce 512 MiB uploads across client and proxy 2026-11-17 02:03:57 +00:00
Chubboy Ren d41a5232ab Merge remote-tracking branch 'upstream/main' into codex/upload-500mib 2026-11-17 01:55:45 +00:00
BaaRai 278de8b2e0 Merge pull request #268 from liuxiaobo0920/fix/report-finding-quality
feat(report): surface finding proof strength in the report and the export
2026-11-17 02:09:01 +01:00
BaaRai 4e4e25f74a Merge pull request #275 from BaaRai/chore/repo-hygiene
chore: stop ignoring docs/
2026-11-17 01:50:41 +01:00
Xiaobo a0adc209ad feat(report): surface finding proof strength in the report and the export
The task report and the findings export asserted every finding with no
qualification: nothing said how far exploitation actually reached (PoE level),
whether the claim was machine-verified (verification status and note), whether
counterevidence was recorded, or whether any traffic was bound. The web UI
badges all of it (VERIFICATION_META, the detail page), so the report — the
artifact a client actually reads — was the last surface still asserting bare
claims.

Render it from one place:

- report/quality.go (new): two constructors and two pure renderers, no I/O, no
  DB handle, so the block is unit-tested without a database.
- Both surfaces call the same helpers, which is the point: the task report and
  the per-finding export cannot drift apart the way duplicated formatting does.
- Missing is explicit: a finding node with no standalone row prints
  "not assessed (no finding record)" instead of an invented zero — the honest
  gap the existing coverage work (#207) also insists on.
- Labels match the shipped UI wording (Verification, Confidence rationale,
  Counterevidence) and states are humanised ("Not assessed", "False positive"),
  with an unrecognised value printed verbatim so a new state cannot silently
  vanish from a report.
- Bound-traffic count appears once per document: as a Proof bullet in the task
  report (it has no traffic section), and in the export only when nothing is
  bound — otherwise the traffic section already states it.
- The detailed report is capped at 8 KiB in the task report only, rune-safe, with
  the cap derived into the truncation message; the export is the canonical
  per-finding document and is never silently shortened.
- The export keeps its document structure: the single-finding document gets
  "## Detailed Report" (a section like its siblings), the multi-finding summary
  gets a bold label.

Read paths only: no change to the write side of poe_level or verification_status,
no schema change (all five columns already exist), no API/DTO change (the widened
FindingMeta stays internal to the report path, and the findings list keeps
selecting only what it renders). One extra task-scoped query on GET /api/report,
because findings bodies stay off the list path.

docs/vulnerability-traffic-evidence.md §Export describes the new Markdown.
2026-11-17 08:40:37 +08:00
BaaRai 9f827577ff chore: stop ignoring docs/
The entry contradicted the four documentation files that are tracked, and any
tool that honours .gitignore concluded that docs/ does not exist. The triage
bot did exactly that on issue #271 and told a contributor the directory was
missing.

Removing it changes nothing for the tracked files and makes a genuinely
untracked file under docs/ visible in git status, which is the point.
2026-11-17 01:38:10 +01:00
BaaRai f9a35194b2 Merge pull request #266 from BaaRai/feat/traffic-replay-tab
feat(web): Replay tab in the traffic detail
2026-11-17 01:21:32 +01:00
BaaRai 515ff301f5 Merge pull request #274 from BaaRai/fix/triage-bot-context
fix(ci): give the triage bot a directory map instead of a truncated file list
2026-11-17 01:17:35 +01:00
BaaRai 524d1f70be fix(ci): give the triage bot a directory map instead of a truncated file list
repo_context() printed the first 120 tracked paths alphabetically, which
stopped at config/ on an 846-file tree, so the model never saw docs/ or
scripts/ and told a contributor on issue #271 that neither directory exists.

The summary now lists the root files, every top-level directory with its file
count, the second level, and the workflow, migration, docs and script paths.
Both prompts also state that the summary is not a listing, so a path missing
from it is never reported as a path that does not exist.

scripts/test-bot-context.sh guards the invariant in the shell CI job: every
top-level directory must appear in the summary. It fails against the previous
version, which is the point.
2026-11-17 01:07:07 +01:00
BaaRai 7cb8e9a3f4 Merge pull request #273 from BaaRai/feat/traffic-rewrite-p33a
feat(traffic): store, validate and compile capture-proxy rewrite rules
2026-11-17 01:04:13 +01:00
BaaRai e678c4e71d ci: run the rewrite-rule engine under the race detector
./traffic/rewrite joins the go test -race list of the go job.
2026-11-17 00:12:09 +01:00