SlowServers Admin wrote on 19.09.2026 21:16:
On Sat Sep 19, 2026 at 5:44 AM UTC, Thomas Kupper wrote:
The man page for sshd_config(5) lists the keywords and which keyword
accepts which token in the TOKEN section.
What are you trying to achieve?
The client already has that information and can pass it to the remote
session if it wants it available.
Hi Thomas,
Yes, it doesn't seem to be supported based on the man page. I wanted to
ask in case I was missing something. I don't mind attempting to add the
feature, myself.
I don't want the client to pass that information as I want the key to be
authenticated. I'd like for people with different keys to ssh say as
[email protected], and be presented with different data based on
their SSH key. Instead of having an account per user, I could have an
application which handles that automatically.
I don't want the user to be able to impersonate another key just by
sending the fingerprint with SendEnv, for example.
I think you want to have a look at AuthorizedKeysCommand and
AuthorizedKeysCommandUser in sshd_config(5).
You can set AuthorizedKeysCommand to a script which takes parameters,
like user name, user id, user home, key type, the user key itself and so
on. And let that script setup what you need (your mentioned application).
Disclaimer: I have only used it to log the user, key type and key
finterprint for testing purposes. And from that it seems to work only if
the users public key is _not_ in authorized_keys.
Have you had a look at login.conf(5) to help restrict a user?
Maybe someone with real-life experience can chime in.
Thank you,
-Slow Servers
