Repository navigation
Ship v0.1.225: package and runtime security admission, authenticated CVE feeds and signed releases - #1057
Open
PyRo1121 wants to merge 275 commits into
Open
Ship v0.1.225: package and runtime security admission, authenticated CVE feeds and signed releases#1057PyRo1121 wants to merge 275 commits into
PyRo1121 wants to merge 275 commits into
Conversation
Use the exact bounded log invocation and a full 40-hex commit identifier throughout the shared historical Git fixture. Retain attended rejection and accepted intentional build failure, and exercise nine finite command-contract controls. Actual hosted native history test reproduced the stale contract. Corrected controls, attended unit test, all-target Clippy and the previously failing native case pass; independent fixture and guest-controller review approved. The disposable guest preserved its package database and prepared backings and shut down cleanly.
Use official database schema dispatch with compatible typed fallback. Refuse cache cleanup when a configured directory cannot be inspected, and create package staging, scoped keyrings, rollback checkouts and metadata generations with private permissions. Cover native handle ownership and restrictive-umask behavior. Prove narrow extracted-function and direct callback coverage correspondence while refusing unsupported macro and attribute contexts; preserve counters and thresholds.
Keep publication and lifecycle descriptors together through blocking workers so cleanup cannot remove active metadata or replace its coordination inode. Derive metadata paths from an explicit build root and retain missing and disabled metadata fast paths. Reject unsuitable package-base and publication lock inodes with effective-user ownership checks and private creation modes. Preserve the lifecycle opener's existing ownership policy. Verify cleanup exclusion, cancellation, cross-process coordination and private fixture isolation.
Support user-owned Omarchy data checkouts while enforcing trusted system helpers and native AUR updates. Preserve consistent Arch package metadata and add a verified Cloudflare Arch advisory snapshot client with defended ingestion storage. Add guest update coverage scenarios and strict retained-execution comparison proofs. Rust library tests, feature Clippy checks, guest CLI scenarios and advisory-service tests pass. Source-correspondence coverage gaps and historical CVE bootstrap remain incomplete.
Move the isolated Arch advisory fixture to the fixed Cloudflare snapshot endpoint. Preserve TLS refusal, exact payload hashes and native version checks; reject stale, future and ill-typed snapshot evidence. The exact previously failing hosted binary pair passes the migrated fixture in disposable KVM. Add real Omarchy process, migration and terminal-input failure tests, and include advisory service verification in mandatory CI. Bind qualified macro coverage evidence to visible imports and extern-crate aliases without changing thresholds or compiler-copy matching. Coverage gaps remain explicit.
…oundaries Derive one trusted Omarchy runtime for coordinator children, stages, cleanup and migration preflight. Preserve optional helper failures and confirmation skips while rejecting foreign helpers before execution. Skip advisory I/O only for empty Review inventories, retaining native inventory rechecks and admission requirements. Accept bounded large CVE records without changing encoded request, feed or archive limits. Update the Arch evidence oracle for explicit Possible findings and Unknown coverage. Validation: 2,392 library tests, 55 Omarchy tests, three Clippy configurations, normal bins, seven protected Omarchy guest scenarios, empty-offline/admission guest controls, 39 service tests, full local CVE parsing and docs checks. Hosted CI and coverage comparison remain separate gates.
Replace package-helper handoffs with fixed elevated native operations, preserve system-scoped transaction ownership, and use configured signing trust for native queries and workers. Reject malformed repository signing metadata and unapproved key imports, constrain overwrite paths to the Omarchy subtree, and remove the pacman subprocess from Doctor's offline database check. Also fix distinct-version cache retention, reject lossy/NUL ALPM paths, and update the two Quinn lockfile entries implicated by the current security audit. Verified 2,402 library tests with 13 ignored, three all-target Clippy feature configurations, CLI/daemon builds, documentation audit, and a real signed guest update plus six signature, lock, metadata and overwrite controls. CI fixture migration, strict coverage comparison and optimized installation remain pending.
Bind retained policy environment inputs and incremental Rust fixtures to their observed compiler regions. Exercise changed inherited policy refusal and use one native boundary to reject absolute AUR symlinks.
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
Resolve pacman auto from the running kernel for both transaction and mirror selection. Refuse missing removal targets, validate Omarchy platform keyring configuration before repository refresh, and retain exact evidence for both Arch AUR outage outcomes.
Check private archive prompts and preinstalled Omarchy migrations with the existing coverage fixtures. Preserve exact retained-source proofs while avoiding repeated alignment and unnecessary indexing.
…idation Keep native ordering for optional epoch and release compatibility, preserve shared-library relations, and use one install-eligible repository selector for Omarchy metadata and transaction admission. Refs #1022
Preserve the operation and completion failures, make the repository admission fixture independent of the host AUR inventory, and patch Quinn in the fuzz lockfile.
Report an incomplete process scan and avoid suggesting lock removal from process-name visibility alone. Refs #1007
Use the same install-repository refusal in Omarchy history and transaction preparation. Exercise the native search path with a local AUR catalog and persist a stable legacy mock inventory fixture.
This branch has not been deployed
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.
Package and runtime installation now reviews exact versions before activation, shows CVE identifiers and source URLs, and requires an explicit foreground terminal decision for disclosed risk or incomplete advisory coverage.
--yes, EOF and unattended execution cannot grant that consent.Tasks resolve their final executable after project and task environment overlays, bind it to the selected reviewed runtime and pin its execution. Python virtualenvs retain their invocation identity through Unix argv[0] while executing the reviewed base interpreter. Managed npm retains the shared package review through materialization, signature audit, optional script execution and publication. Transitive package bans and changed advisory evidence invalidate the transaction. Explicitly accepted Unknown coverage remains Unknown and cannot supply cached clean authority.
Runtime feeds preserve genuinely fresh verified evidence during competing refreshes. Published GitHub disclosures with no applicability entries remain possible findings with explicit coverage gaps. Both corrections are deployed. Arch advisory unavailability requires explicit consent, with separate native cases for findings, unavailable evidence and a valid snapshot containing unrelated packages.
Ten public installer tests use isolated fixed-public HTTPS routes and the unchanged production downloader. Swift uses genuine publisher-signed inputs and must refuse staged content changed after review. Tests retain TLS, checksum, pinned-signature, policy and publication boundaries. Docker and benchmark installation fixtures exercise attended consent while proving unattended refusal. Benchmark timing includes consent overhead; native state checks and performance thresholds remain intact. Fedora update assertions normalize terminal styling while retaining required header, mode and completion evidence.
Local validation passes 150 advisory service tests with 1,573 assertions, TypeScript, 45 workflow controls, 80 native CLI controls, 64 fixture controls, 16 runtime-consent preflight tests, 12 independently verified native-driver controls, formatting and diff checks. Independent source reviews cover the critical production groups and corrections. Genuine Python probes preserve virtualenv prefix and local imports after entry replacement while refusing to execute the replacement. A previously admitted release binary completed a scoped Go 1.27.1 install after showing 28 CVEs and receiving one exact foreground-terminal acceptance; installed-content verification matched.
An authenticated CI-built CLI also verified Cargo argument forwarding through an owned synthetic reviewed-runtime fixture in Arch WSL, while refusing its unreviewed counterpart. Two npm policy controls additionally run through the isolated root-to-ordinary-user coverage path with exact identity receipts.
Candidate commit
4a029cc89a80a146fec745a4676f08fa07ac5707.The exact optimized
omgandomgdpair passed 48 Omarchy scenarios and three standard Arch read-only checks in the owned Arch KVM guest. The full update used signed private repositories, native ALPM transactions, two exact-digest foreground consent prompts, and controlled Omarchy lifecycle helpers. Both known migrations completed with preinstalled packages and no repeated install. The guest verified boot after an AUR outage. Standard Arch reported the same outage and preserved the installed foreign package. The guest's real package database remained intact.Missing removal targets fail the full transaction. Pacman
Architecture = autouses the running kernel machine for libalpm and mirror URLs, including the tested Linuxi686personality. Explicit architecture order is preserved. Arch validates the platform keyring list before refreshing repository databases. Archive-only ALPM preparation refuses repository targets, and the acknowledgement lists exactly the private archives with their hashes and the full prepared batch digest.The advisory Worker bounds and validates cache origins and SHA-256 keys while preserving same-origin query separation. The Worker passed 151 tests, TypeScript, and Wrangler dry-run packaging. The binary batch passed 2,727 enabled Arch library tests, all-targets Clippy, 692 unprivileged fixture and comparator tests, and the root exporter check in QEMU.
OMG SHA-256
13b888930f99a865ad846727a134ea3ffcb1e3ebe6cf44b9c1711eaa22ee80b8. omgd SHA-256abdfc0cb381d54d20fa07a29554c32e6eda29492e6d38e1ad2d6c9cbfa2c85a4.The preceding instrumented report hit all 5,528 counted lines in the Omarchy update module and first refused a newly mapped advisory transport fixture error. This batch adds deterministic evidence for that error and additional Arch boundaries. The comparator also handles partial asynchronous completion counts and can traverse all 174 shared files in the archived report within its existing work limit. The complete exact-base coverage comparison, including remaining AUR and runtime attribution, is still required.
Coverage run for this commit · CI run for this commit
The previous candidate completed genuine Swift signing-key decoding, pinned signature verification and SDK extraction. It rejected modified staged contents at the expected integrity check. The fixture then counted the persistent install lock among staging leftovers. The updated control distinguishes the regular version lock from actual staging directories and symlinks.
The original coverage comparator reports complete npm coverage in the preceding instrumented output. Its remaining runtime-security line belongs to a test server that deliberately wrote after closing its write side. The updated test retains the success, rejected status, truncated response and oversized response cases and requires the specific size-limit error. The comparator and thresholds are unchanged.
Exact Arch package info now uses the configured repository handle directly. The query retains database epoch checks, repository priority and usage, signature validation, and full Rust catalog validation. This removes an unused native local catalog scan. The preceding matched artifact was 78.190 ms slower for
info firefoxagainst a 50 ms limit. The new artifact still needs measurement.The macOS fixture explicitly binds its virtual environment to the owned interpreter and exercises rejection of a different base. The production interpreter validation remains intact. The batch also fixes the borrowed-slice lint error. Hosted Swift, full coverage, macOS and measured performance are required before merge.
Release remains blocked until this exact patch passes its checks, trusted-main publisher verification certifies the imported archive, and exact-main acceptance succeeds. The six signed release archives, SBOM/provenance, R2 publication and Windows/WSL vulnerable npm refusal test have not yet been delivered.
Public feeds cannot establish the absence of undisclosed zero-days. Unknown coverage remains a warning requiring an explicit risk decision.
Closes #1003.
Closes #1029.
Closes #1026.
Closes #1030.