Skip to content

Commit bb396b8

Browse files
committed
Document sshd.trusted_cas
slackhq/nebula#1098
1 parent 30bca7b commit bb396b8

File tree

1 file changed

+9
-0
lines changed

1 file changed

+9
-0
lines changed

docs/config/sshd.mdx

+9
Original file line numberDiff line numberDiff line change
@@ -22,6 +22,8 @@ sshd:
2222
- user: steeeeve
2323
keys:
2424
- '[ssh public key string]'
25+
trusted_cas:
26+
- '[ssh ca public key string]'
2527
```
2628
2729
See also the [Debugging with Nebula SSH commands](/docs/guides/debug-ssh-commands/) guide.
@@ -70,3 +72,10 @@ You can generate a host key using the `ssh-keygen` command line utility.
7072
7173
These options are how you create `users` for the debug ssh daemon. Password authentication for the ssh debug console is
7274
NOT supported.
75+
76+
# sshd.trusted_cas
77+
78+
As an alternative to (or in addition to) `authorized_users`, you may define a list of trusted SSH CA public keys. Any
79+
SSH certificate signed by a trusted CA will be granted access to the SSH debug server. If an SSH certificate contains
80+
at least one principal, then the username provided when connecting to the server must match at least one principal. If
81+
no principals are defined in the certificate, any username can be used.

0 commit comments

Comments
 (0)