07 – Harden Build and Deployment Trust Boundaries #238
Labels
No labels
area:authentication
area:flake-utilities
area:performance
area:tbd
host:chaos
host:electra
host:fleet
host:lyra
host:nova
host:vega
investigation
phase:cutover
phase:deploy
phase:mcp
phase:module
phase:packaging
phase:prep
phase:validation
priority:high
priority:medium
project:attic-postgres-lyra-rollout
project:auto-update-reliability
project:auto-update-remediation
project:declarative-purity-cleanup
project:external-review
project:fleet-boundary-cleanup
project:host-facts-refactor
project:lyra-nixos-deploy
project:lyra-service-stack-migration
project:nebula-mesh-network
project:nixos-build-deployment-pipeline
project:security-hardening
project:service-stack-migration
project:vega-sillytavern-cutover
project:wiki-rebuild
repo:numtide/flake-utils
repo:numtide/nix-auth
repo:numtide/nixos-passthru-cache
repo:numtide/nix-relay
service:auto-update
service:mem0
service:nix
service:sillytavern
service:slskd
service:synthseek
No milestone
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
nimmo/nixos-config#238
Loading…
Reference in a new issue
No description provided.
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?
Goal
Review and harden the remote build and deployment trust boundaries.
Scope
Audit credential separation, secret placement, access controls, recovery, and the effects of a compromised component. Preserve the approved development and recovery workflows.
Keep host-specific security findings, attack paths, and the detailed compromise analysis in private operational records. This public issue tracks the work without publishing those details.
Validation
Complete the access-control and recovery checks, record the detailed evidence privately, and post only a non-sensitive completion summary here.
nimmo referenced this issue2026-09-23 18:21:27 +01:00
nimmo referenced this issue2026-09-23 18:24:20 +01:00
nimmo referenced this issue2026-09-23 18:44:19 +01:00
The access-control, credential-lifecycle, recovery, and final authorised-key policy checks are complete. Detailed security findings remain in private operational records. The issue can close after MR !250 is merged; follow-on Forgejo authority and CI work is tracked separately.
MR approved, closing issue