aboutsummaryrefslogtreecommitdiffstats
path: root/docs
diff options
context:
space:
mode:
authortv <tv@krebsco.de>2026-11-18 11:17:06 +0000
committertv <tv@krebsco.de>2026-11-18 12:23:54 +0100
commitac66571a87cf36e769bb8308568808e3a0c2ce31 (patch)
tree4b8a4a09ef3d6db2a83d590458c000869b4cb17c /docs
parent2ac20de00d0535dcb2a0d327f73c0b61fbbe4749 (diff)
continuum-party: a key the ssh-agent holds, given itself
`--key` gives a public key itself, an `authorized_keys` line, as well as a file of them: of a file of several, the first signs, with a warning naming it, and another is given itself to sign with it. An agent that doesn't hold the key given signs nothing, and the client stops before it records or puts what it would have signed, saying which key it asked for.
Diffstat (limited to 'docs')
-rw-r--r--docs/configuration.md4
-rw-r--r--docs/guides/federation/keys.md17
2 files changed, 14 insertions, 7 deletions
diff --git a/docs/configuration.md b/docs/configuration.md
index d246082..989f268 100644
--- a/docs/configuration.md
+++ b/docs/configuration.md
@@ -256,4 +256,8 @@ record = "/home/tv/.config/continuum/tv.record"
continuum-party --config tv.toml write home/tv/motd '"hello"'
```
+`key` is an OpenSSH private key file, or a public key an ssh-agent holds: the key itself
+(`key = "ecdsa-sha2-nistp256 AAAA…"`), or a file of such lines, whose first signs
+([`guides/federation/keys.md`](guides/federation/keys.md), Keys in an ssh-agent).
+
`node` and `token` are secrets: never logged, however they are given.
diff --git a/docs/guides/federation/keys.md b/docs/guides/federation/keys.md
index 6448f9e..3dd2834 100644
--- a/docs/guides/federation/keys.md
+++ b/docs/guides/federation/keys.md
@@ -41,16 +41,19 @@ Secure Enclave or a phone, held by an agent there. Such a key is `ecdsa-sha2-nis
its type ending in `@openssh.com`) is neither: it signs otherwise than the federation
takes, and is no party's key.
-Give the client its public key, a `.pub` file, as `--key`: it asks the agent at
-`SSH_AUTH_SOCK` to sign, and writes the signature as `ssh-keygen -Y sign` does through
-that agent.
+Give the client its public key as `--key`, the key itself (an `authorized_keys` line) or
+a file holding it: it asks the agent at `SSH_AUTH_SOCK` to sign, and writes the signature
+as `ssh-keygen -Y sign` does through that agent. Of a file holding several keys (all
+`ssh-add -L` lists, say), the first signs, and the client warns: give another itself to
+sign with it. An agent that doesn't hold the key given signs nothing, and the client stops
+before it records or puts what it would have signed.
```sh
ssh-add -L # ecdsa-sha2-nistp256 AAAA… tv@phone
-ssh-add -L | grep tv@phone > phone.pub
-cut -d' ' -f1,2 phone.pub # the key as a version or a set names it
-continuum-party --node http://tv:secret@localhost:3000 --key phone.pub \
- --record tv.record write home/tv/motd '"from the phone"'
+ssh-add -L | grep tv@phone | cut -d' ' -f1,2 # the key as a version or a set names it
+continuum-party --node http://tv:secret@localhost:3000 \
+ --key "$(ssh-add -L | grep tv@phone)" --record tv.record \
+ write home/tv/motd '"from the phone"'
```
Of an ECDSA signature, `s` and the curve's order less `s` both check. The federation