Artifact [d11831c0e8]

Artifact d11831c0e80a94ce6dcd4b5cf5ef59ef045077a097c4301fc9d41f56c1d3c728:

• File internal/clearsign/exec_js.go — part of check-in [a87790f468] at 2026-10-26 12:45:46 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: 617) [annotate] [blame] [check-ins using] [more...]

//go:build js

package clearsign

import (
	"context"
	"errors"
	"fmt"
)

// errNoProcesses: js/wasm runs no external signer or gpg. SSH signatures
// still verify, in process, when package sshverify is linked.
var errNoProcesses = errors.New("external signing commands are unavailable on js/wasm")

func runClearsign(context.Context, string, []byte) ([]byte, error) { return nil, errNoProcesses }

func runDetached(context.Context, string, []byte) ([]byte, error) { return nil, errNoProcesses }

func verifyPGP(context.Context, string, []byte) error {
	return fmt.Errorf("%w: %w", ErrCannotVerify, errNoProcesses)
}