That error comes from JSch, the TurboVNC Viewer's built-in SSH client.
I think it may be due to either a badly-formatted SSH known_hosts file
or possibly an incompatibility, such as OpenSSH writing a known_hosts
entry using an encryption algorithm that JSch doesn't support. I will
try to reproduce the problem and see if I can make the TurboVNC Viewer
handle it more gracefully.
On 1/28/26 9:26 PM, Richard Ems wrote:
Hi all,
For a customer I configured a new workstation with Rocky Linux 9.7 and latest
versions of VirtualGL and TurboVNC.
The users connect from MacOS laptops with TurboVNC 3.2.1.
Two users can connect without issues, one gets the error message below.
Any ideas what may be the issue?
Thanks,
Richard
PS: more info: all 3 users can connect to an older workstation without issues. The two users that can connect to the new workstation have ARM MACs. The one that cannot has a Intel MAC.
--
You received this message because you are subscribed to the Google Groups "TurboVNC
User Discussion/Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/turbovnc-users/30d7f341-d774-48d8-acca-75d394bff0ae%40virtualgl.org.