diff options
author | Lennart Poettering <lennart@poettering.net> | 2024-09-06 14:39:15 +0200 |
---|---|---|
committer | Yu Watanabe <watanabe.yu+github@gmail.com> | 2024-09-06 16:02:29 +0200 |
commit | 7a3a49386cc49d3971531ea24efb84232c05cc86 (patch) | |
tree | 9a5433db879feadecd7b7b8baf8621c6b6471825 /NEWS | |
parent | Merge pull request #34291 from poettering/utmpx-all-the-way (diff) | |
download | systemd-7a3a49386cc49d3971531ea24efb84232c05cc86.tar.xz systemd-7a3a49386cc49d3971531ea24efb84232c05cc86.zip |
NEWS: extend the userdb sshd_config NEWS entry a bit
Diffstat (limited to 'NEWS')
-rw-r--r-- | NEWS | 15 |
1 files changed, 13 insertions, 2 deletions
@@ -530,9 +530,20 @@ CHANGES WITH 256: SSH Integration: - * An sshd config drop-in to allow ssh keys acquired via userdbctl (for + * An sshd_config drop-in to allow ssh keys acquired via userdbctl (for example expose by homed accounts) to be used for authorization of - incoming SSH connections. + incoming SSH connections. This uses the AuthorizedKeysCommand stanza + of sshd_config. Note that sshd only allows a single command to be + configured this way, hence this drop-in might conflict with other + uses of the logic. It is possible to chainload another, similar tool + of another subystem via the --chain switch of userdbctl, to support + both in parallel. See the "INTEGRATION WITH SSH" section in + userdbctl(1) for details on this. Our recommendation how to combine + other subsystem's use of the SSH authroized keys logic with systemd's + userbctl functionality however is to implement the APIs described + here: https://systemd.io/USER_GROUP_API – in that case this newly + added sshd_config integration would just work and do the right thing + for all backends. * A small new unit generator "systemd-ssh-generator" has been added. It checks if the sshd binary is installed. If so, it binds it via |