On Sep 19, 2024, at 5:05 AM, Kimmo <kimmo.h...@gmail.com> wrote:
--
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 turbovnc-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/turbovnc-users/8dcc3bc9-180b-4a2a-8ea5-2e8afa8562acn%40googlegroups.com.
On Sep 20, 2024, at 5:07 AM, Kimmo <kimmo.h...@gmail.com> wrote:
I've loaded the .ppk file to Pageant and the SSH connection works with Putty and Windows OpenSSH but I get the password inquiry in TurboVNC (without any TurboVNC parameters).
To view this discussion on the web visit https://groups.google.com/d/msgid/turbovnc-users/4de5ed19-76f8-4042-98e4-aa8390b96132n%40googlegroups.com.
I reproduced the issue, and it is
definitely due to the use of an Ed25519 key. I guess ssh-agent
communicates the key in such a way that the key type doesn't
matter, but it does matter with Pageant. Ed25519 support is a
high priority for TurboVNC 3.2.
DRC
To view this discussion on the web visit https://groups.google.com/d/msgid/turbovnc-users/fab713cc-b53b-4cdd-ba6a-dfebf4facad9n%40googlegroups.com.
Ignore my previous remark. I forgot that, if you want to use Ed25519 keys via ssh-agent or Pageant with the current version of TurboVNC, you have to add
PubKeyAcceptedAlgorithms +ssh-ed25519
to ~/.ssh/config (%USERPROFILE%\.ssh\config on Windows.)
That is because the SSH client doesn't explicitly support the signature scheme, so you have to tell it that it is OK to use that scheme (which it is, because the SSH agent supports it.)
I am still working on explicit Ed25519
support, which will make it unnecessary to modify the OpenSSH
config file.
DRC
Ed25519 support has just been pushed to
the dev branch as well, so the latest 3.2 Evolving builds now
have it (https://turbovnc.org/DeveloperInfo/PreReleases). I
haven't thoroughly tested the feature yet, so let me know if you
run into any problems.
DRC