publish-repo: Rückprüfung ohne pkg-Datenbank #28
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/repo-verify"
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?
Der erste Publish-Lauf nach #27 hat das Repo vollständig hochgeladen und ist erst bei der Rückprüfung abgebrochen:
pkg updatemit eigenerPKG_DBDIRläuft nicht als normaler User, und der Runner läuft nicht als root.Neue Prüfung (nur curl, tar, openssl)
packagesite.yaml, mit abschließendem NUL-Byte.Getestet
Gegen das vom fehlgeschlagenen Lauf veröffentlichte echte Repo
testing(anonym, nur lesend;tarundpkglokal durch Stubs ersetzt):mdns-bridged 0.1.0.s72,os-mdns-bridge 1.0.s72)shellcheck sauber. Den Lauf auf dem Runner selbst zeigt der Push auf master nach dem Merge.
🤖 Generated with Claude Code
https://claude.ai/code/session_01Vh6img4RYU1F52VUwGJcrp
The first publish run uploaded the repository completely, then failed in the read-back: `pkg update` with a private PKG_DBDIR refuses to work for a non-root user ("wrong user or group ownership (expected 0/0 versus actual 806/0)"), and the runner is not root. Verification now needs only curl, tar and openssl: - every file downloaded anonymously (as a firewall does) matches the repository built and signed here (SHA-256) - the catalogue signature verifies against the committed public key (pkg's pubkey format: RSA/SHA-256 over the hex SHA-256 of packagesite.yaml, trailing NUL) - the catalogue lists exactly the built packages and versions Tested against the repository published by the failed run (anonymous, read-only): passes; another public key, a wrong version and a changed file are each rejected. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Vh6img4RYU1F52VUwGJcrp