It seems that the ThinLinc client requires directly defining one specific private SSH key for every connection and to enter the key password every connection attempt.
SSH authentication using public keys is typically handled by ssh key agents, for example the OpenSSH auth agents in Linux or for example on WIndows the Pageant authentication agent that is part of the PuTTY suite, such that it is not required to continually enter in a key password or to have to to permanently define a specific key for a specific connection.
Is it possible to also use an SSH public key agent with the ThinLinc client?
Thanks for clearing that up.
If there is a list of very useful features to add to what is otherwise a great remote desktop solution: ssh key ageant support would make using the client much more convenient.
There has been some preliminary work done, but unfortunately nothing that has made it through into the final product yet. For reference, the relevant Bugzilla entry is here:
Hello, we are also hoping to see SSH agent support in the Thinlinc client. We would like to use it for authentication with keys created by the Trusted Platform Module (TPM) using the ssh-tpm-agent.
Thanks @stig, appreciate the insight. We’re currently finalizing the 4.20 release, after which planning will begin for the next one. If SSH agent support ends up on the roadmap as part of this process, I’ll make sure to update this thread.
