#8 Unknown VeNCrypt authentication scheme from VNC server: 2

[Djuro Drljaca]

I hope this is the correct place to report bugs...

I have problems connecting VNC clients that use LibVNCServer v0.9.9 (krdc and remmina) to a TightVNC server ("tightvnc v1.3.10" that is using "TigerVNC implementation of Xvnc: xorg-x11-Xvnc v7.6"). I can connect with a tightvnc client (vncviewer), but not with VNC clients that are using LibVNCServer...

Here is the debug output from krdc:

krdc(19087)/krdc (VNC backend) VncClientThread::run: --------------------- trying init ---------------------
krdc(19087)/krdc (VNC backend) VncClientThread::outputHandler: "VNC server supports protocol version 3.8 (viewer 3.8)"
krdc(19087)/krdc (VNC backend) VncClientThread::outputHandler: "We have 2 security types to read"
krdc(19087)/krdc (VNC backend) VncClientThread::outputHandler: "0) Received security type 19"
krdc(19087)/krdc (VNC backend) VncClientThread::outputHandler: "Selecting security type 19 (0/2 in the list)"
krdc(19087)/krdc (VNC backend) VncClientThread::outputHandler: "1) Received security type 2"
krdc(19087)/krdc (VNC backend) VncClientThread::outputHandler: "Selected Security Scheme 19"
krdc(19087)/krdc (VNC backend) VncClientThread::outputHandler: "OpenSSL initialized."
krdc(19087)/krdc (VNC backend) VncClientThread::outputHandler: "Got VeNCrypt version 0.2 from server."
krdc(19087)/krdc (VNC backend) VncClientThread::outputHandler: "We have 1 security types to read"
krdc(19087)/krdc (VNC backend) VncClientThread::outputHandler: "0) Received security type 2"
krdc(19087)/krdc (VNC backend) VncClientThread::outputHandler: "Unknown VeNCrypt authentication scheme from VNC server: 2"

I already openned a bug report for krdc, but since it appears that the problem is in the library I also oppened it here.

If it helps you can also take a look in krdc bug report: https://bugs.kde.org/show_bug.cgi?id=320650

If you need any additional information then please contact me and I will try to help.

[Djuro Drljaca]

It might also help that I have "VncAuth" security type enabled on the server ... I think.

[Johannes Schindelin]

Yeah, I fear the problem is that the VeNCrypt scheme 2 is simply not supported by libvncclient, but I have no resources to look further into the issue, sorry.

Maybe you want to move the discussion onto the mailing list? Christian and I seem not to have time to look through the issue tracker more than thrice a decade...

[Djuro Drljaca]

Hello,

this is no longer a problem ... I got it working with "vncviewer" and it
works good enough for my needs. It would still be better if I could get it
to work with krdc, but I can understand that it might not be easy to solve
(I am also a SW developer :) )

Thank you for your answer anyway.

Regards,
Djuro Drljaca

On Sun, Mar 30, 2014 at 8:39 PM, Johannes Schindelin dscho@users.sf.netwrote:

Yeah, I fear the problem is that the VeNCrypt scheme 2 is simply not
supported by libvncclient, but I have no resources to look further into the
issue, sorry.

Maybe you want to move the discussion onto the mailing list? Christian and
I seem not to have time to look through the issue tracker more than thrice
a decade...

---

• [support-requests:#8]
  http://sourceforge.net/p/libvncserver/support-requests/8/ Unknown
  VeNCrypt authentication scheme from VNC server: 2*

Status: open
Group: v1.0_(example)
Created: Mon Jun 03, 2013 06:11 PM UTC by Djuro Drljaca
Last Updated: Mon Jun 03, 2013 06:49 PM UTC
Owner: nobody

I hope this is the correct place to report bugs...

I have problems connecting VNC clients that use LibVNCServer v0.9.9 (krdc
and remmina) to a TightVNC server ("tightvnc v1.3.10" that is using
"TigerVNC implementation of Xvnc: xorg-x11-Xvnc v7.6"). I can connect with
a tightvnc client (vncviewer), but not with VNC clients that are using
LibVNCServer...

Here is the debug output from krdc:

krdc(19087)/krdc (VNC backend) VncClientThread::run: ---------------------
trying init ---------------------
krdc(19087)/krdc (VNC backend) VncClientThread::outputHandler: "VNC server
supports protocol version 3.8 (viewer 3.8)"
krdc(19087)/krdc (VNC backend) VncClientThread::outputHandler: "We have 2
security types to read"
krdc(19087)/krdc (VNC backend) VncClientThread::outputHandler: "0)
Received security type 19"
krdc(19087)/krdc (VNC backend) VncClientThread::outputHandler: "Selecting
security type 19 (0/2 in the list)"
krdc(19087)/krdc (VNC backend) VncClientThread::outputHandler: "1)
Received security type 2"
krdc(19087)/krdc (VNC backend) VncClientThread::outputHandler: "Selected
Security Scheme 19"
krdc(19087)/krdc (VNC backend) VncClientThread::outputHandler: "OpenSSL
initialized."
krdc(19087)/krdc (VNC backend) VncClientThread::outputHandler: "Got
VeNCrypt version 0.2 from server."
krdc(19087)/krdc (VNC backend) VncClientThread::outputHandler: "We have 1
security types to read"
krdc(19087)/krdc (VNC backend) VncClientThread::outputHandler: "0)
Received security type 2"
krdc(19087)/krdc (VNC backend) VncClientThread::outputHandler: "Unknown
VeNCrypt authentication scheme from VNC server: 2"

I already openned a bug report for krdc, but since it appears that the
problem is in the library I also oppened it here.

If it helps you can also take a look in krdc bug report:
https://bugs.kde.org/show_bug.cgi?id=320650

If you need any additional information then please contact me and I will
try to help.

---

Sent from sourceforge.net because you indicated interest in
https://sourceforge.net/p/libvncserver/support-requests/8/

To unsubscribe from further messages, please visit
https://sourceforge.net/auth/subscriptions/

[Johannes Schindelin]

Well, since you are a software developer, you will appreciate the fact that LibVNCServer is Open Source.

In that light, I will close the issue and invite you to open a pull request to https://github.com/LibVNC/libvncserver.