diff options
| author | tv <tv@krebsco.de> | 2026-11-09 15:38:41 +0000 |
|---|---|---|
| committer | tv <tv@krebsco.de> | 2026-11-09 18:20:59 +0100 |
| commit | e59be7214b1fc1998f76a34f7e4429ee4259494c (patch) | |
| tree | 9754fa4d80f5afce3cbf6d8225b986f99bf402c3 /docs/access.md | |
| parent | 2b7aaf12fc0fa288560072766ad6d8d39e5e37ed (diff) | |
access: a key's comment 256 bytes at most
Review 4, 1250's note: a key's comment was kept as given, unbounded but by the request
limit (2 MiB), in protocol data every node holds and the dashboard shows. It says whose
and where the key is: at most 256 bytes now (`sshsig::MAX_COMMENT`), a longer one
refused with the key.
Diffstat (limited to 'docs/access.md')
| -rw-r--r-- | docs/access.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/access.md b/docs/access.md index 402f1ab..94ca195 100644 --- a/docs/access.md +++ b/docs/access.md @@ -33,7 +33,7 @@ password hashes: every member reads the document). doesn't read is left out, and anything but `false` disables. * **`keys`**: the user's SSH keys, each by a name of its choosing, as an `authorized_keys` line has it (`"laptop": "ssh-ed25519 AAAA… alice@laptop"`; Ed25519 - only; the comment is kept and checks nothing): what it signs values with (Values signed by their users, below) and logs in with. A user + only; the comment, 256 bytes at most, is kept and checks nothing): what it signs values with (Values signed by their users, below) and logs in with. A user manages its own, whatever else it may do: `GET /auth/keys`, `PUT /auth/keys/<name>` with the line, `DELETE /auth/keys/<name>`; under a strict policy, by signing its entry with only its keys changed (`continuum-signed key-add laptop |
