fef68a84c9
initialize_yubikey (guide steps 1-4): gnupg install fallback (apt-get/dnf/pacman), card check, public-key fetch from the card's URL field, idempotent gpg-agent SSH config merge, GNUPGHOME chmod 700; --dry-run, --gnupg-home. send_pubkey (guide steps 5-6): resolve the SSH public key from four sources (--yubikey via gpg-agent ssh socket, --url, --fingerprint via store chain local keyring -> keys.openpgp.org -> keyserver.ubuntu.com with fingerprint checking, --pubkey literal), prove possession of the private half with a random challenge signature (ssh-keygen -Y sign -U / verify) before anything is stored, then append idempotently to the target's authorized_keys (dedup by key material, comments ignored). --no-verify opts out explicitly; --dry-run resolves only. 51 tests (flow via injected runner: no hardware, network, or interactive terminal); steps 1-6 of the wiki guide (yubikey-ssh-guide.md) are now one command each. Generated by Mistral Vibe. Co-Authored-By: Mistral Vibe <vibe@mistral.ai>
5.5 KiB
5.5 KiB
Changelog
Notable changes are listed here. Release numbers match
pyproject.toml. Newest entries are first.
Format follows Keep a Changelog and Semantic Versioning.
[Unreleased]
- Nothing yet.
[0.6.0] - 2026-11-18
Added in 0.6.0
gpgtools send_pubkey(guide steps 5-6): resolves an SSH public key from one of four sources —--yubikey(gpg-agent ssh socket),--url(armored OpenPGP key, converted withgpg --export-ssh-keyin a throwaway GNUPGHOME),--fingerprint(store chain: local keyring, keys.openpgp.org VKS, keyserver.ubuntu.com, each fingerprint-checked), or--pubkey(literal line, format-validated). Before anything is stored, proof of possession: a random challenge is signed by the private half through the agent (ssh-keygen -Y sign -U; PIN prompts reach the user) and verified against the candidate line (ssh-keygen -Y verify). Only then is the line appended to the target'sauthorized_keys— idempotent (grep before append), perms enforced.--no-verifyskips the check explicitly;--dry-runresolves and prints without side effects. 22 new tests.
[0.5.0] - 2026-11-18
Added in 0.5.0
gpgtools(Python, categorygpg): YubiKey GPG/SSH helpers.daedalus gpgtools initialize_yubikeyruns the fresh-machine flow (steps 1-4 of the wiki guide): installs gnupg when missing (apt-get, dnf, pacman), checks the card, fetches the public key from the card's URL field withgpg --fetch-keys, and writes the gpg-agent SSH config (enable-ssh-support, cache TTLs) with the GNUPGHOME directory at mode 700.--dry-runprints the plan; steps 5-7 (derive and deploy the SSH key per host) are server-specific and intentionally out of scope.
[0.4.0] - 2026-11-18
Added in 0.4.0
bash/daedalus_common.sh: the shared interface for bash scripts (SPEC item 6.10) — a script sources its sibling helper, defineshelp()(usage) andmain(), and ends withdaedalus_bash_dispatch "$@", which routeshelp/-h/--helptohelp()and everything else tomain()unchanged.- Bash script completion (SPEC item 3.13.5.2):
daedalus <name> <TAB>completes--help,-h, andhelpfor scripts implementing the interface; no script runs on TAB. Scripts without the interface get the shell default. bash/hello_bash.sh: sample bash script (categorytest) through the shared interface, the bash twin ofhello, with tests.bash/tests/: the interface tests — helper behavior through a sample script and enforcement of the interface for every registered.shscript.
[0.3.0] - 2026-11-18
Added in 0.3.0
- Shell completion via argcomplete
(new dependency):
daedalus hel<TAB>completeshello, category labels complete together with the scripts they filter (daedalus test h<TAB>), options complete after-, and--path <name>completes script names. Activate witheval "$(register-python-argcomplete daedalus)"(INSTALL.md). - Script arguments complete from the script's own parser (SPEC item
3.13.5.1): once the script name is typed, daedalus delegates the rest
of the line to the script —
daedalus hello -<TAB>offers hello's-h/--help, never daedalus's options. A Python script opts in withargcomplete.autocomplete(parser)(SPEC item 6.9). daedalus/completions.py: the candidate functions argcomplete calls.
Changed in 0.3.0
- The CLI argument handling now uses
argparse(daedalus.cli.build_parser):-h/--helpprints the argparse rendering, and parser-level errors keep the argparse messages (exit code 2 stays). Options are parsed anywhere before the script words; everything after the script name still goes to the script (SPEC item 3.1 unchanged). - SPEC item 1.5 policy: reuse a popular, tested, trusted third-party package when it exists instead of writing our own; argcomplete is the first such dependency (SPEC item 9.6).
[0.2.0] - 2026-11-18
Added in 0.2.0
hello: sample Python script (categorytest) that prints a hello line and the daedalus version; first registered script, with tests and an installed package entry (daedalus.hello).
[0.1.0] - 2026-11-18
Added in 0.1.0
- Categories:
Script.categories(defaultgeneral),daedalus <category>listing (AND when several) anddaedalus <category>… <name>runs; script names and category labels never collide. - New listing format:
Daedalus Version:line,script/type/categoriestable, descriptions wrapped to the terminal width and indented, colors viaNO_COLOR/FORCE_COLOR. daedalus/run_python_script.py:.pyscripts run through a child entry that sets upsys.path, logging,sys.argv, and exit codes.daedalus.daedalus_logging: file logging to~/.daedalus/debug.logplus a colored stderr console handler (DAEDALUS_LOGLEVEL,DAEDALUS_NO_LOGGING).- Library imports: shared code imports as
daedalus.<folder>; the checkout registerspython/src/<folder>as packages on import and the child getsREPO_ROOTonPYTHONPATH. - Exact error messages for every usage failure, with close matches after a category prefix.
Changed in 0.1.0
SPEC.mdrewritten with stable item numbers (SPEC item 3.7.1), in lockstep with the upstream scriptman specification.
[0.0.0] - 2026-11-11
Added in 0.0.0
- Empty template: CLI, CI, packaging, and script-integration guide with no registered scripts.