security handbook: say the repo limit in operator terms
This commit is contained in:
parent
1edeb5c55d
commit
c9604a6708
1 changed files with 10 additions and 9 deletions
|
|
@ -129,15 +129,16 @@ checkpoints**, not about sandboxing the agent from its own tools:
|
|||
settings nor merge its own PR. It's **not** set up for external VCS (GitHub
|
||||
etc.), though — there, operator-merge is process + accepted risk, not a
|
||||
technical control.
|
||||
- **Repo creation is a per-agent setting, default 0** — the _repositories_ badge
|
||||
in an agent's card sets how many repos that agent's forge account may create
|
||||
(`max_repos` in its permissions record, Forgejo's `max_repo_creation`, 0 to
|
||||
100). The operator must raise it for that agent before it may create any. Agents never create organizations: the
|
||||
controller turns that off on every agent account. A repo an agent creates is
|
||||
its own, so the operator-merge gate doesn't cover it, and the agent can add a
|
||||
CI workflow to it. CI workflows run unsandboxed on the CI runner, which is
|
||||
arbitrary code on the runner host. Allow repo creation only for agents you
|
||||
would trust with that.
|
||||
- **Repo creation is a per-agent setting, default 0** — an agent's card has a
|
||||
_repositories_ limit on its permissions panel: how many repos that agent may
|
||||
create. The default is 0, so the operator must raise it for an agent before
|
||||
that agent may create any. Agents never create organizations. A repo an agent
|
||||
creates is its own, so the operator-merge gate doesn't cover it, and the
|
||||
agent can add a CI workflow to it. CI workflows run unsandboxed on the CI
|
||||
runner, which is arbitrary code on the runner host. Allow repo creation only
|
||||
for agents you would trust with that. The record field and the forge setting
|
||||
behind the limit are in the [permissions
|
||||
conventions](../../5-project/process/conventions.md#permissions).
|
||||
- **Operator sign-off** — config changes are config PRs an operator merges
|
||||
on the forge (see
|
||||
[`persistence.md`](persistence.md#config-changes)), and
|
||||
|
|
|
|||
Loading…
Reference in a new issue