Add public ssh keys ...

... to allow other people to give
me access to their systems

.ssh/README.md

@@ -0,0 +1,25 @@
+# `ssh`-related Files
+
+This folder contains
+    my [public SSH keys](./authorized_keys_webartifex),
+    to be enabled locally with [`ssh-setup`](../.local/bin/ssh-setup).
+
+
+## How the keys are managed
+
+The keys are tracked as `authorized_keys_webartifex`
+    and deliberately *not* as `~/.ssh/authorized_keys`:
+
+- The file is sparse-excluded and never checked out into `~/`
+- [`ssh-setup`](../.local/bin/ssh-setup) reads it
+  straight out of the local repository (i.e., `HEAD`)
+  and appends any missing keys to the untracked `~/.ssh/authorized_keys`
+- Keys added locally on a machine are never touched:
+  neither `dotfiles pull` nor a re-run of `ssh-setup` removes them
+- Because the two paths differ,
+  the machine-local file never shows up in `dotfiles status`
+  and cannot be overwritten by any `dotfiles` operation
+
+So, run `dotfiles pull` and then `ssh-setup`
+    to bring a trusted machine up to date with the latest keys,
+    giving me access to it.

.ssh/authorized_keys_webartifex

@@ -0,0 +1,6 @@
+ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIOhhfx063dGoaE62cbdyGL3kp1AIovWFojQGNdqUpxr8 laplace
+ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIMRDaWrT2hH7BOV4Zv1ctVGqwfeqkssnHklRXBmng6Wr lazarus
+ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIN0GVKtgpgzpdf7E6e2vCytDSa2zPSgZ+8fAKCOotugH peter
+ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIDq2JDk3pX79p7ampZhVQxIZg4qaUBkTPIQSbK0XeKoc wilddog
+ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIGGNCrFt/gUbBHVqhthBuRmdDH6yS30+GGcCnARSzg+q wolfram
+ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIKfaK5LUp7ghZLfl7urwQx+l+m/Vm7iksz8deGx4L5sD workstation2