FreeBSD Bugzilla – Bug 182474
net/tightvnc vncviewer can't handle null authentication
Last modified: 2014-08-11 18:35:07 UTC
vncviewer rejects empty passwords and therefore can't be used with
VNC sessions that don't require authentication. Specifically,
VBoxHeadless with the default null authentication still triggers
vncviewer to request a password but vncviewer rejects an empty
See also PR ports/182471
Fix: The following patch allows empty passwords to be entered.
$ vncviewer server:6213
Connected to RFB server, using protocol version 3.8
Performing standard VNC authentication
Reading password failed
Over to maintainer (via the GNATS Auto Assign Tool)
Reassign to the heap
I'm not so comfortable to apply such a adhoc patch.
Anyway, I will look how other vnc viewers treat empty password.
`whois vmeta.jp | nkf -w`
This should have been set to feedback some time ago.
Reassign to maintainer
Strange, Koichiro IWAO is usually responsive.
Moving this to patch-ready. Maintainer approval no longer needed due to multiple timeouts. Assuming this patch is still valid..
(In reply to meta from comment #3)
> I'm not so comfortable to apply such a adhoc patch.
> Anyway, I will look how other vnc viewers treat empty password.
> `whois vmeta.jp | nkf -w`
> meta <firstname.lastname@example.org>
Okay, so I see he did respond but never came up with a better patch, then didn't respond to the more recent ping.
A commit references this bug:
Date: Mon Aug 11 18:33:10 UTC 2014
New revision: 364635
net/tightvnc: allow null authentication
Submitted by: email@example.com
Approved by: firstname.lastname@example.org (maintainer timeout)
The implications for this are still open for discussion, but the need
to allow vncviewer to connect to VBox is demostrated. If it needs to be
reverted, pointy hat to me.