dohertj2/mxaccessgw
1
0
Fork 0
Code Issues 43 Pull Requests 1 Actions Packages Projects Releases Wiki Activity

Reset the Gitea instance runner registration token (TST-32 / R21-X2) #181

New Issue
Open
opened 2026-11-06 15:24:59 -05:00 by dohertj2 · 0 comments
dohertj2 commented 2026-11-06 15:24:59 -05:00
Owner
Copy Link
Copy Source

Both Gitea act_runners on 10.100.0.35 share one instance-scope registration token that was world-readable for about five months and is still live (a probe registered and then deleted a runner with it). Gitea 1.26.4 exposes no CLI/API rotation, so the reset must be done in the admin web UI ("Reset registration token"); existing runners keep their identity.

Source: archreview/2026-10-21/remediation/00-tracking.md R21-X2; archreview/2026-08-19/remediation/00-tracking.md TST-32; archreview/2026-07-12/remediation/90-candidate-findings-next-cycle.md (Operator actions, TST-30 follow-up); docs/runbooks/TST-30-second-ci-runner.md.
No repo change; operator action on the Gitea admin page.

Both Gitea act_runners on `10.100.0.35` share one instance-scope registration token that was world-readable for about five months and is still live (a probe registered and then deleted a runner with it). Gitea 1.26.4 exposes no CLI/API rotation, so the reset must be done in the admin web UI ("Reset registration token"); existing runners keep their identity. Source: `archreview/2026-10-21/remediation/00-tracking.md` R21-X2; `archreview/2026-08-19/remediation/00-tracking.md` TST-32; `archreview/2026-07-12/remediation/90-candidate-findings-next-cycle.md` (Operator actions, TST-30 follow-up); `docs/runbooks/TST-30-second-ci-runner.md`. No repo change; operator action on the Gitea admin page.
dohertj2 added the type:infrapriority:p2blockedmigrated labels 2026-11-06 15:24:59 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area:auth
Authentication and authorization
 area:client-dotnet
.NET client library
 area:client-go
Go client library
 area:client-java
Java client library
 area:client-python
Python client library
 area:client-rust
Rust client library
 area:contracts
Protocol and generated contract work
 area:dashboard
Blazor dashboard work
 area:docs
Documentation
 area:gateway
Gateway server work
 area:tests
Automated and live tests
 area:worker
MXAccess worker process work
 blocked
Blocked by dependency
 cross-repo
Needs coordinated change in another family repo (wire contract etc.)
 migrated
Migrated from a markdown backlog (2026-11 standardization)
 priority:p0
Must-have / blocking
 priority:p1
High priority
 priority:p2
Normal priority
 priority:p3
Low priority / nice to have
 type:bug
Defect in shipped behaviour
 type:debt
Technical debt / hygiene
 type:deploy-gate
Rollout/deploy/migration step not yet done on an environment
 type:docs
Documentation work
 type:feature
Feature implementation
 type:followup
Follow-up deferred from a plan, PR or gate
 type:infra
Infrastructure and scaffolding
 type:review-finding
Unfixed finding from an architecture/code review
 type:test
Test work
No Label blocked migrated priority:p2 type:infra
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
dohertj2 (dohertj2)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: dohertj2/mxaccessgw#181
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?