feat: keel-pve 0.1.0, signed Keel templates on a Proxmox VE host #1
No reviewers
Labels
No labels
accessibility
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Keel-Linux/keel-pve!1
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feat/keel-pve"
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?
First code of
keel-pve, the Proxmox VE host package of handbookdocs/proxmox-distribution.md(point 2).What it does
keel-pve update: fetchesaplinfo.dat.gzand.ascfromreleases.keellinux.org/pve, verifies withsqv --keyring /usr/share/keyrings/keel-archive-keyring.gpg <asc> <dat>(the same callPVE::APLInfomakes with its own keyring), parses every record with pveam's rules, then stores both under/var/lib/keel-pve/. A refused update keeps the previous index.keel-pve available: lists the stored index, re-verified first.keel-pve download STORAGE TEMPLATE: package name (newest version) or file name; destination frompvesm status --content vztmplandpvesm path STORAGE:vztmpl/<file>, never guessed and never created; download into amktemp -ddirectory made there (no fixed temp name, no symlink written through), sha512 against the signed index, rename only on a match. Locations must be https; curl has connect and transfer time limits.keel-pve list: Keel volumes in every vztmpl storage./etc/apt/preferences.d/keel-pve(conffile): the Keel archive gives the host only keel-pve and keel-archive-keyring, everything else -1.keel-pve-update.timer, daily, shipped disabled. No pve-manager file is touched; purge removes/var/lib/keel-pveonly..tar.zst on PVE 9
Accepted. Checked today against current sources: pve-storage
Storage.pmVZTMPL_EXT_RE_1includestar.zst(andPlugin.pmlists/parses vztmpl volumes with it); pve-containerLXC/Create.pmmaps.zsttotar --zstd.Signature
The live index is signed by the archive key's current signing subkey
0304 1024 F4B2 C0C2 F42D DDEA 0490 6EAB 7751 3310(primaryAD09 64BE ... 3180), sokeel-archive-keyring (>= 0.1.1)is the trust root; verified with sqv against the live files.Test plan
..Locations, stalled transfers, lock wait, apt policy of the pin), fakepvesm, local index signed by a throwaway key, real sqv and curl overfile://; kcov 100 percent, gate 95dpkg-buildpackageandlintian --pedantic --fail-on error,warningclean locallypvesm: update, available, download of keel-web 19.0-3 (sha512 matched,zstd -tOK), listupdate;available;download local keel-web(7 s, sha512 matched, re-run says already present); unknown storage refused;listalso found a Keel template on cephfs;pveam list local,pvesm listand the API the web UI's template selector calls (/nodes/<node>/storage/local/content?content=vztmpl) all showlocal:vztmpl/debian-13-keel-web_19.0-3_amd64.tar.zst, formattzst;keel-pve-update.serviceruns under its hardening; purge left nothing; pve-manager'strustedkeys.gpgandAPLInfo.pmunchangedpct createhas no dry-run, and no container could be created on that host) and opening the web UI dialog itselftests / coverage,package / changelog,build / trixie