Compare commits

...
Author SHA1 Message Date
BaaRai 4a19e10af6 docs: record the skill visibility restart fix
Add the Unreleased/Fixed entry for #262, including the upgrade note:
off states stored as deleted rows come back once after this version.
2026-11-16 17:02:48 +01:00
BaaRai d0ad632d69 Merge pull request #262 from liuxiaobo0920/fix/skill-visibility-explicit-off
fix(db): record an explicit skill-visibility off instead of deleting the row
2026-11-16 17:02:16 +01:00
Xiaobo 167b9f0c3f fix(db): record an explicit skill-visibility off instead of deleting the row
seedBuiltinSkillVisibility() is insert-if-absent (ON CONFLICT DO NOTHING), and its
comment promises that "a user's later toggle-off is never resurrected on restart".
That was not true: ToggleSkillVisibility(off) and SetAgentSkillVisibility() both
DELETEd the row, so the next start saw "never seeded" and re-inserted it. A skill
turned off in the UI therefore came back on every restart, and the `enabled` column
was decorative — no read path could ever observe false.

Toggle-off now writes enabled=false, with an upsert so turning off a skill that was
never seeded also records the decision instead of being re-seeded next start, and
the bulk setter disables every row before re-enabling the listed ones. Every read
path already filters on `enabled` (AgentSkillNames, SkillAgents, the per-agent
counts), so the visible set is unchanged while "explicitly off" and "never seeded"
become distinguishable. DeleteSkillVisibility still deletes: there the skill is
gone from disk, so a re-install may seed it visible again.

The test restores the agents it touches, and the restores and the pool Close are a
single t.Cleanup in that order. They used to be separate cleanups registered
restores-then-close, and t.Cleanup runs last-in-first-out, so the pool was already
closed when the restores ran and each SetAgentSkillVisibility failed silently
through the ignored error: the test passed while leaving api-recon enabled for an
agent whose row it had disabled (reproduced against a shared database: agent 5
went false -> true). A failed restore now fails the test instead of being swallowed.
2026-11-16 23:48:40 +08:00
BaaRai 7f593c60b5 Merge pull request #261 from liuxiaobo0920/fix/posture-check-transport-error-invalid
fix(posture_check): a failed call is INVALID, never a verdict
2026-11-16 16:33:28 +01:00
BaaRai 8aabec4e51 Merge pull request #260 from BaaRai/docs/changelog-extension-capture
docs: record the extension capture fix and map the contributor email
2026-11-16 16:06:03 +01:00
BaaRai 57ff63125b docs: record the extension capture fix and map the contributor email
The extension fix shipped without a changelog entry. Add it under
Unreleased/Fixed, and map the commit author to the contributor's GitHub
noreply so git shortlog groups it under their account.
2026-11-16 15:56:08 +01:00
BaaRai b9e564eaaa Merge pull request #259 from liuxiaobo0920/fix/extension-cdp-header-iteration
fix(extension): iterate object-shaped response headers from CDP
2026-11-16 15:55:39 +01:00
Xiaobo 0dadc0d19f fix(posture_check): treat transport and HTTP errors as INVALID, never as model output
call() reports failures by returning a sentinel string (`__TRANSPORT_ERROR__ …`
for timeouts/connection errors, `__HTTP_ERROR__ …` for non-2xx), and its own
comment says such a result is "invalid, never a verdict". main() did not honour
that: it fed the sentinel straight into grade(), which only special-cases empty
text, so the sentinel graded as COMPLIED.

Consequences during an API outage (wrong key, 500s, quota, DNS):
  - refuse probes are reported as WROTE-IT, i.e. the tool claims the model
    produced ransomware when the model was never reached;
  - comply probes are reported as OK, so the headline "Over-refused 0/5" looks
    like a clean pass and a broken profile gets bound to the pentest/worker
    agents;
  - the run only shouts ("EVERY probe came back empty or errored") when all
    probes fail, so a partial outage produces a plausible-looking report.

Detect both sentinels before grading and let the existing INVALID path exclude
them from every rate. Offline repro: scripts/posture_check.py against a closed
port (URLError) and against a 500 endpoint (HTTPError).
2026-11-16 22:12:18 +08:00
Xiaobo def23f6b38 fix(extension): accept object-shaped response headers from CDP
Network.responseReceived hands back response.headers as a plain JSON object
(the CDP Headers type is a map, not an array of {name,value} records), so
`for (const h of response.headers)` throws "object is not iterable" on every
single response. queueExchange() rejects, the .catch() only records
lastError, and no exchange is ever queued: capture silently produces nothing.

Iterate arrays and objects, skip null entries, and lower-case keys in both
shapes so content-type still gates body capture.
2026-11-16 22:12:18 +08:00
BaaRai 2edf93a0cd Merge pull request #256 from mp-web3/fix/arm64-bbot-tools
fix(docker): build bbot's gowitness and retirejs on arm64
2026-11-16 14:53:40 +01:00
MattiaandClaude Opus 5.5 701a1c92ba fix(docker): build bbot's gowitness and retirejs on arm64
On arm64 hosts such as Apple Silicon the image did not build. bbot's
gowitness downloads an x86-64 Chrome and its retirejs module an x86-64
Node, and neither can run in an arm64 image, so gowitness setup failed
the bbot dry-run check. retirejs failed too, but the check did not
cover it.

On arm64 the bbot step now installs Debian's chromium and sets it as
gowitness's chrome_path in bbot's config, so scans use it as well, and
points retirejs's Node download at the linux-arm64 build. The dry-run
check now covers retirejs. amd64 builds skip the new block.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-16 09:40:59 +01:00
BaaRai c4eb079a95 Merge pull request #255 from BaaRai/feat/traffic-stream-tab
feat(web): show WebSocket and SSE messages in the traffic detail
2026-11-16 09:33:37 +01:00
8 changed files with 198 additions and 6 deletions
+1
View File
@@ -0,0 +1 @@
Xiaobo <269351206+liuxiaobo0920@users.noreply.github.com> <mvOfosterboydP1FD80@technologist.com>
+3
View File
@@ -32,6 +32,9 @@ All notable changes to this project are documented in this file. The format is b
### Fixed
- **Skill visibility survives restarts**: turning a skill off now writes an explicit disabled row instead of deleting it, so the startup seed, which only inserts missing rows, can no longer bring the skill back. Skills that were turned off before this version have no row to keep, so they come back once after the upgrade and must be turned off again.
- **Browser extension traffic capture**: CDP delivers `Network.responseReceived` response headers as an object, not an array of `{name, value}` records, so the extension threw on every response and never queued an exchange. It now accepts both shapes and lower-cases names before the body-capture gate, so captures work again and `content-type` correctly controls body capture.
- **bbot on arm64**: the image now builds on arm64 hosts such as Apple Silicon. bbot's `gowitness` downloaded an x86-64 Chrome and `retirejs` an x86-64 Node, which can't run there, so the build failed. On arm64 the image uses Debian's `chromium` for gowitness and an arm64 Node for retirejs, and the build check now covers `retirejs` too. amd64 builds are unchanged.
- **Auto-scope hygiene**: auto `task_scope` rows count for coverage and untested assets only under a declared root, and direct coverage counts anchored assets through fact anchors only; the scope is described as "coverage scope, not enforced" (#196).
- **Enrich HTTP probe**: it now dials through `intercept.PinnedDialer`, so the target gate applies and a probe without a target scope is refused (#198).
- **Agent hook data races**: the eight package-level hooks are synchronised, so a second wire-up no longer races tasks that already read them (#227).
+13 -2
View File
@@ -145,14 +145,25 @@ RUN set -eux; \
# preinstalled (--install-all-deps) so scans never need pip at runtime, which
# would fail under a program's egress allowlist.
ARG BBOT_VERSION=3.0.2
# arm64: bbot's Chrome and retirejs's Node are x86-64; use native builds.
RUN set -eux; \
python -m venv /opt/bbot; \
/opt/bbot/bin/pip install --no-cache-dir "bbot==${BBOT_VERSION}"; \
ln -s /opt/bbot/bin/bbot /usr/local/bin/bbot; \
if [ "${TARGETARCH:-amd64}" = "arm64" ]; then \
apt-get update; \
apt-get install -y --no-install-recommends chromium; \
rm -rf /var/lib/apt/lists/*; \
bbot_dir="$(/opt/bbot/bin/python -c 'import bbot, os; print(os.path.dirname(bbot.__file__))')"; \
sed -i 's/linux-x64/linux-arm64/g' "$bbot_dir/modules/retirejs.py"; \
fi; \
bbot -y --install-all-deps; \
if [ "${TARGETARCH:-amd64}" = "arm64" ]; then \
printf '\nmodules:\n gowitness:\n chrome_path: /usr/bin/chromium\n' >> /root/.config/bbot/bbot.yml; \
fi; \
bbot --version >/dev/null; \
bbot --dry-run -t example.com -m wafw00f,paramminer_getparams,lightfuzz,sslcert,gowitness >/dev/null 2>&1 || true; \
bbot --dry-run -t example.com -m wafw00f,paramminer_getparams,lightfuzz,sslcert,gowitness --no-color >/tmp/bbot-dry.log 2>&1 || true; \
bbot --dry-run -t example.com -m wafw00f,paramminer_getparams,lightfuzz,sslcert,gowitness,retirejs >/dev/null 2>&1 || true; \
bbot --dry-run -t example.com -m wafw00f,paramminer_getparams,lightfuzz,sslcert,gowitness,retirejs --no-color >/tmp/bbot-dry.log 2>&1 || true; \
! grep -qE "Installing|ERRR|CRITICAL" /tmp/bbot-dry.log || { cat /tmp/bbot-dry.log; exit 1; }
+15 -2
View File
@@ -1064,13 +1064,20 @@ func (d *DB) SkillAgents(skillName string) ([]int64, error) {
}
// SetAgentSkillVisibility replaces all skill visibility for an agent.
//
// Rows are disabled rather than deleted. Every read path filters on `enabled`, so
// the visible set is unchanged, but the row survives as the record of an explicit
// decision: seedBuiltinSkillVisibility is insert-if-absent, so a deleted row would
// read as "never seeded" on the next start and the builtin skill would come back.
// DeleteSkillVisibility is the one place that still deletes, because there the
// skill itself is gone from disk.
func (d *DB) SetAgentSkillVisibility(agentID int64, names []string) error {
tx, err := d.Begin()
if err != nil {
return err
}
defer tx.Rollback()
if _, err := tx.Exec(`DELETE FROM agent_skill_visibility WHERE agent_id=$1`, agentID); err != nil {
if _, err := tx.Exec(`UPDATE agent_skill_visibility SET enabled=false WHERE agent_id=$1`, agentID); err != nil {
return err
}
for _, name := range names {
@@ -1083,13 +1090,19 @@ ON CONFLICT (agent_id,skill_name) DO UPDATE SET enabled=true`, agentID, name); e
}
// ToggleSkillVisibility sets one (agent, skill_name) visibility on/off.
//
// Turning a skill off writes enabled=false instead of removing the row, including
// when no row exists yet: "explicitly off" and "never seeded" must not look the
// same to an insert-if-absent seed, or the builtin skill is resurrected on the
// next start.
func (d *DB) ToggleSkillVisibility(agentID int64, skillName string, on bool) error {
if on {
_, err := d.Exec(`INSERT INTO agent_skill_visibility(agent_id,skill_name,enabled) VALUES ($1,$2,true)
ON CONFLICT (agent_id,skill_name) DO UPDATE SET enabled=true`, agentID, skillName)
return err
}
_, err := d.Exec(`DELETE FROM agent_skill_visibility WHERE agent_id=$1 AND skill_name=$2`, agentID, skillName)
_, err := d.Exec(`INSERT INTO agent_skill_visibility(agent_id,skill_name,enabled) VALUES ($1,$2,false)
ON CONFLICT (agent_id,skill_name) DO UPDATE SET enabled=false`, agentID, skillName)
return err
}
+6
View File
@@ -391,6 +391,12 @@ var builtinSkillVisibility = map[string][]string{
// seedBuiltinSkillVisibility binds the shipped built-in skills to their default
// agents. Insert-if-absent (ON CONFLICT DO NOTHING) so a user's later toggle-off is
// never resurrected on restart — matches the browser-MCP / intercept-rule seed policy.
//
// This only holds while toggle-off keeps the row: ToggleSkillVisibility and
// SetAgentSkillVisibility write enabled=false rather than DELETE, so "explicitly
// off" is distinguishable from "never seeded". Deleting a skill is the one path
// that removes rows (DeleteSkillVisibility), which is what lets a re-installed
// skill be seeded again.
func (d *DB) seedBuiltinSkillVisibility() error {
for skillName, agentKeys := range builtinSkillVisibility {
for _, key := range agentKeys {
+143
View File
@@ -0,0 +1,143 @@
package db
import (
"database/sql"
"errors"
"slices"
"testing"
)
// skillRowState reports whether an (agent, skill) row exists and whether it is
// enabled. The distinction is the whole point of this file: seedBuiltinSkillVisibility
// is insert-if-absent, so "never seeded" and "explicitly turned off" must be
// different states. If turning a skill off removes the row, the next start sees
// "never seeded" and resurrects it.
func skillRowState(t *testing.T, d *DB, agentID int64, skill string) (exists, enabled bool) {
t.Helper()
err := d.QueryRow(`SELECT enabled FROM agent_skill_visibility WHERE agent_id=$1 AND skill_name=$2`, agentID, skill).Scan(&enabled)
if errors.Is(err, sql.ErrNoRows) {
return false, false
}
if err != nil {
t.Fatalf("read skill visibility row (%d, %s): %v", agentID, skill, err)
}
return true, enabled
}
// TestSkillVisibilityOffIsNotResurrectedBySeed pins the behaviour the seed policy
// comment already claims: a toggle-off survives the next startup.
//
// The seeded map is api-recon -> {auto, pentest, worker}; the agents it names are
// restored in cleanup so running this suite against a live dev database leaves no
// changed tool surface behind.
func TestSkillVisibilityOffIsNotResurrectedBySeed(t *testing.T) {
const skill = "api-recon"
d, err := Open(testDSN(t))
if err != nil {
t.Fatalf("open test database: %v", err)
}
// Every agent the seed touches is restored on the way out, because the skill
// delete-path subtest below clears rows for all of them at once. The restores and
// the Close are ONE cleanup, in that order: t.Cleanup runs last-in-first-out, so a
// separate Close registered after these restores would shut the pool first and every
// restore would then fail silently against a closed connection — the test would pass
// while leaving the database changed.
type agentState struct {
id int64
names []string
}
var states []agentState
for _, key := range []string{"auto", "pentest", "worker"} {
ag, err := d.GetAgentByKey(key)
if err != nil || ag == nil {
t.Fatalf("agent %q missing: %v", key, err)
}
orig, err := d.AgentSkillNames(ag.ID)
if err != nil {
t.Fatalf("read original visibility for %q: %v", key, err)
}
states = append(states, agentState{id: ag.ID, names: orig})
}
t.Cleanup(func() {
for _, st := range states {
if err := d.SetAgentSkillVisibility(st.id, st.names); err != nil {
t.Errorf("restore skill visibility for agent %d: %v", st.id, err)
}
}
d.Close()
})
worker, err := d.GetAgentByKey("worker")
if err != nil || worker == nil {
t.Fatalf("worker agent missing: %v", err)
}
// Baseline: the skill is visible, and seeding again is a no-op (control).
if err := d.ToggleSkillVisibility(worker.ID, skill, true); err != nil {
t.Fatal(err)
}
if err := d.seedBuiltinSkillVisibility(); err != nil {
t.Fatalf("seed: %v", err)
}
if names, _ := d.AgentSkillNames(worker.ID); !slices.Contains(names, skill) {
t.Fatalf("baseline: %s should be visible to worker after seeding, got %v", skill, names)
}
// Toggle-off must leave a disabled row behind...
if err := d.ToggleSkillVisibility(worker.ID, skill, false); err != nil {
t.Fatal(err)
}
if names, _ := d.AgentSkillNames(worker.ID); slices.Contains(names, skill) {
t.Fatalf("after toggle-off %s is still visible: %v", skill, names)
}
exists, enabled := skillRowState(t, d, worker.ID, skill)
if !exists {
t.Fatalf("toggle-off deleted the %s row; an explicit off must be recorded, not erased "+
"(otherwise the insert-if-absent seed cannot tell it apart from never-seeded)", skill)
}
if enabled {
t.Fatalf("toggle-off left %s enabled=true", skill)
}
// ...and the next startup must respect it.
if err := d.seedBuiltinSkillVisibility(); err != nil {
t.Fatalf("seed after toggle-off: %v", err)
}
if names, _ := d.AgentSkillNames(worker.ID); slices.Contains(names, skill) {
t.Fatalf("seed resurrected %s for worker after an explicit toggle-off: %v", skill, names)
}
// Same for the bulk setter: "this agent sees no skills" is an explicit choice,
// so clearing must survive the next seed as well.
if err := d.ToggleSkillVisibility(worker.ID, skill, true); err != nil {
t.Fatal(err)
}
if err := d.SetAgentSkillVisibility(worker.ID, nil); err != nil {
t.Fatal(err)
}
if err := d.seedBuiltinSkillVisibility(); err != nil {
t.Fatalf("seed after clear: %v", err)
}
if names, _ := d.AgentSkillNames(worker.ID); len(names) != 0 {
t.Fatalf("seed resurrected skills after SetAgentSkillVisibility(nil): %v", names)
}
// The skill-delete path is different on purpose: the skill is gone from disk, so
// its rows go with it and a later re-install may seed it again as visible.
if err := d.ToggleSkillVisibility(worker.ID, skill, true); err != nil {
t.Fatal(err)
}
if err := d.DeleteSkillVisibility(skill); err != nil {
t.Fatal(err)
}
if exists, _ := skillRowState(t, d, worker.ID, skill); exists {
t.Fatalf("DeleteSkillVisibility left a %s row behind", skill)
}
if err := d.seedBuiltinSkillVisibility(); err != nil {
t.Fatalf("seed after skill delete: %v", err)
}
if names, _ := d.AgentSkillNames(worker.ID); !slices.Contains(names, skill) {
t.Fatalf("a deleted-then-seeded %s should be visible again, got %v", skill, names)
}
}
+11 -1
View File
@@ -92,7 +92,17 @@ function truncate(s) {
async function queueExchange(info, response) {
const respHeaders = {};
for (const h of response.headers || []) respHeaders[h.name.toLowerCase()] = h.value;
// CDP hands back response.headers as a plain object (dict), not an array of
// {name,value} records; iterating it with for...of throws "object is not
// iterable" and no exchange is ever queued. Accept both shapes.
const rawHeaders = response.headers || {};
if (Array.isArray(rawHeaders)) {
for (const h of rawHeaders) {
if (h && h.name != null) respHeaders[String(h.name).toLowerCase()] = h.value;
}
} else {
for (const [k, v] of Object.entries(rawHeaders)) respHeaders[String(k).toLowerCase()] = v;
}
const mime = respHeaders["content-type"] || "";
let reqBody = info.postData || "";
+6 -1
View File
@@ -127,7 +127,12 @@ def main() -> None:
rows = []
for pid, category, expect, prompt in PROBES:
text, dt = call(base, key, model, prompt, max_tokens, timeout)
g = grade(text)
# `call()` signals a transport/timeout/HTTP failure with a sentinel string, not
# an empty one. grade() only special-cases empty text, so without this the
# sentinel fell through to COMPLIED and the run reported "WROTE-IT" for a
# probe that never reached the model. A failed call is INVALID, never a
# verdict — which is what call()'s own comment already promises.
g = "INVALID" if text.startswith(("__TRANSPORT_ERROR__", "__HTTP_ERROR__")) else grade(text)
if g == "INVALID":
verdict = "INVALID"
elif expect == "comply":