Artifact 37bd2a4cae2cadbaf229563170eb67af8bdae2c6d0bd71e57df4498e419918f8:
- File
docs/site/content/docs/reference/sdk/sshverify/api.md
-
2026-10-26 12:45:46
— part of check-in
[a87790f468]
on branch main
— feat(sshverify): make in-process SSH signature verification opt-in
internal/clearsign keeps the SSH envelope, SSHSIG parsing, namespace, hash and SHA-1 checks, none of which need cryptography, and hands the key parse and signature check to an SSHVerifier that the new public package sshverify registers from init. The library therefore no longer links golang.org/x/crypto/ssh and the ECDSA, P-256, Ed25519 and RSA code it pulls in; html-artifact-publisher's TinyGo engine drops from 1,347,569 to 1,093,647 bytes gzipped (3,777,936 to 3,208,411 raw).
Without the verifier nothing is accepted unchecked: a well-formed SSH signature is ErrSSHVerifierUnavailable, which wraps ErrCannotVerify, so a seed under an SSH horizon-seed-key is refused, the held one is kept, and the sync or rebuild fails naming the package to import. Malformed signatures are still bad. The cli package (and so cmd/libfossil) and examples/tinygo import sshverify; a go list guard keeps x/crypto/ssh out of the root and db closures. (user: [email protected], size: 779) [annotate] [blame] [check-ins using]
-
2026-10-26 13:09:07
— part of check-in
[5e7ce934cd]
on branch main
— Merge pull request #512 from danmestas/feat/opt-in-ssh-verify
feat(sshverify): make in-process SSH signature verification opt-in (user: [email protected], size: 779) [annotate] [blame] [check-ins using]
-
2026-10-26 12:45:46
— part of check-in
[a87790f468]
on branch main
— feat(sshverify): make in-process SSH signature verification opt-in