4 ms·
Nice! That’s two problems in one : we had to find a synchronization mechanism, and, sensitive data are spread out on several machines I was confused by the im
by j_s 12y ago
Nice!
That’s two problems in one : we had to find a synchronization mechanism, and, sensitive data are spread out on several machines
I was confused by the implication that public keys are sensitive data. I guess the list of usernames and commands could be?
- _Soulou 12y agoHi j_s, By sensitive data, we meant part of the identity of all our users (there is quite often user@host at the end of the public keys sent by our users), and the second point is linked to the internal commands. In the `command="ssh-handler" ssh-rsa....` the command doesn't receive the SSH public key as argument, so we would have to provide additional information like: `command="ssh-handler <user_id|username|key_id>" ssh-rsa....` So yes, if we have a way to avoid having a copy of that on all our servers able to authenticate users, we take it!