25 lines
958 B
Markdown
25 lines
958 B
Markdown
|
# `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.
|