0.1.0: deterministic SSH keys, age identities with encryption, and child mnemonics from one mnemonic #9
Reference in New Issue
Block a user
Delete Branch "next"
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?
Milestone PR for https://git.eeqj.de/sneak/keyfunc/milestone/28, the 0.1.0 release.
nextmerges cleanly intomain; this description says what is on the branch and is kept current.Everything the README specifies is on the branch, each unit reviewed independently and landed on a passed review:
script/entrypoints and Makefile, Docker-only linting from a hash-pinnedDockerfile.lint, the Gitea workflow, and the mnemonic sources in the specified order with their refusals (issue 1).keyfunc ssh pubandpriv, with the README's two test vectors proven byte for byte and an index of 2147483648 or above refused before any derivation (issue 1).keyfunc ssh installandkeyfunc ssh to: the public line appended on a host only when absent, fed on standard input; the private key served from an in-process agent on a private socket and never written to disk (issue 2).keyfunc age pub,priv,encryptanddecrypt, the identity derived the waysecretderives it, the derived recipient always amongencrypt's recipients (issue 3).keyfunc mnemonic, child mnemonics of 12, 18 or 24 words from BIP-85's own mnemonic application, with the specification's test vectors as tests (issue 4).make checkis green on the head ofnext, run after the last landing. There is no licence file; that choice is yours. After merging, tag0.1.0onmain.Model: opus-5 (implementation and review); fable-5-1 (landing)
ssh install can't expect to run code on the host. it needs to download the authorized keys file, alter it, and re-upload it. (to a sidecar file alongside then an atomic rename!)