sshkeys: Trust certificates issued by the CA
Now that we have an internal SSH certificate authority, instead of explicitly listing all M×N keys for each user and client machine, we can list only the CA certificate in the SSH authorized keys file for the *core* user. This will allow any user who presents a valid, signed SSH certificate for the *core* principal to log in.master
parent
88f165363d
commit
859deb0664
|
@ -4,5 +4,4 @@ passwd:
|
|||
users:
|
||||
- name: core
|
||||
ssh_authorized_keys:
|
||||
- sk-ssh-ed25519@openssh.com AAAAGnNrLXNzaC1lZDI1NTE5QG9wZW5zc2guY29tAAAAINZCN2cxMDwedJ1Ke23Z3CZRcOYjqW8fFqsooRus7RK0AAAABHNzaDo= dustin@rosalina.pyrocufflink.blue
|
||||
- sk-ssh-ed25519@openssh.com AAAAGnNrLXNzaC1lZDI1NTE5QG9wZW5zc2guY29tAAAAIAB6xTCSNz+AcQCWcyVKs84tThXN4wpLgCo2Lc48L6EsAAAABHNzaDo= dustin@luma.pyrocufflink.blue
|
||||
- cert-authority ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAAABBBImIoTTmhynCVy/vJ/Q2bWydzqVsvwhGvDgBbklw0eDt8UEbbP9HHPhxiMDtiAhbvRTg5BhYVAlR1MgdooT5dwQ=
|
||||
|
|
Loading…
Reference in New Issue