Skip to content
go-libfossil Check-in [a992dcb34f]
Login

Check-in [a992dcb34f]

Overview
Comment:Merge pull request #464 from danmestas/release/v0.15.0

chore(release): v0.15.0

Timelines: family | ancestors | descendants | both | main | trunk | v0.15.0
Files: files | file ages | folders
SHA3-256: a992dcb34f1fb83af98e69a0dd9284e386cc614b72eae283524c5001727577d7
User & Date: [email protected] on 2026-10-23 17:23:15.000
Other Links: branch diff | manifest | tags
Context
2026-10-23
20:13
Merge pull request #468 from danmestas/feat/signing

feat(signing): sign check-ins and horizon seeds with gpg or ssh check-in: 4a439c6de6 user: [email protected] tags: main, trunk

20:05
feat(signing): sign check-ins and horizon seeds with gpg or ssh

go-libfossil signed nothing and verified nothing, so a structural-horizon clone could not tell a seed its origin minted from one substituted on disk (draft-fossil-horizon-00 §5.2.4, HZ-5.2-5 and HZ-5.2-6), and a repository with fossil's clearsign setting on stored its check-ins unsigned.

Signing follows fossil's contract, the same one zit follows. With clearsign on (and the legacy omitsign off), every check-in a commit or branch creation stores is clear-signed by pgp-command: unset, gpg --clearsign -o, run as COMMAND OUTFILE INFILE; a command named ssh* runs as COMMAND INFILE and its detached signature is wrapped in fossil's SSH envelope. A signer that fails, or returns text that does not strip back to the manifest, abandons the commit. NoSign and --nosign store one check-in unsigned.

An origin with clearsign on signs each seed it mints. It signs only after the request is authorized, outside the request's transaction, keeps one signature per seed and command so the seed's name is stable, and re-signs a kept signature its own horizon-seed-key no longer verifies. Keeping is best effort, so a read-only mirror still serves.

A clone given its origin's key (CloneOpts.SeedKey, repo clone --seed-key, kept as horizon-seed-key) verifies every seed on clone, pull and rebuild, and falls back to the content horizon from one unsigned or signed by another key. An SSH key is verified in process: namespace fossilscm, the configured key, no SHA-1 ssh-rsa, and exactly fossil's envelope. An OpenPGP fingerprint is verified by gpg, which must report one good signature by that key over text byte-equal to what the parser reads, with nothing after the signature. A verifier that cannot run keeps the held seed and fails the sync instead of discarding it.

fossil 2.28 and zit read the signed check-ins; a check-in zit signs with the same SSH key verifies here; zit clones a signing origin and holds its seed. check-in: 612f2e7acc user: [email protected] tags: main, trunk

17:23
Merge pull request #464 from danmestas/release/v0.15.0

chore(release): v0.15.0 check-in: a992dcb34f user: [email protected] tags: main, trunk, v0.15.0

17:16
chore(release): v0.15.0 changelog leaf check-in: 3df0fc796c user: [email protected] tags: release/v0.15.0, trunk
17:16
Merge pull request #461 from danmestas/feat/horizon-cones

feat: horizon cones (draft-fossil-horizon-00) check-in: ac0bf85d72 user: [email protected] tags: main, trunk

Changes