feat: add production configuration contracts - #3
Open
high-cde wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Sintesi
Questa PR introduce le configurazioni P0 autonome e verificabili individuate nell'audit di production-readiness. Le modifiche rendono più espliciti i contratti di rootfs, hardening, supply chain, operabilità e governance CI, senza dichiarare risolte le capacità che richiedono consumer o chiavi operative.
Modifiche incluse
os-release,fstab, hostname, resolver, account protetti e policymdevsecuretty, shell consentite,sysctle policy modprobeCODEOWNERS, Dependabot, SBOM, security scan e contratto di configurazioneVerifiche eseguite
./tools/zdos-selftest.sh --all;git diff --check.Fuori perimetro
Installer BIOS/UEFI, Secure Boot completo, repository di aggiornamento firmato, rollback A/B, autenticazione web pubblica e backend di backup restano attività successive. Ciascuna richiede un consumer operativo, chiavi o segreti gestiti fuori dal repository e test dedicati.
Checklist