The hostname validation in VeNCRypt checks for "ip::port" which breaks the validation on two parts:
1. This is contrary to how other VNC and cert checks are performed, and also why should the server include the port number in the certificate?
2. This opens us up for a dns-poisoning attack.
Checking that the hostname in the certificate matches the hostname entered by the client is the only way that this should work and is also the way that for example Firefox does it.
Patch against win/vncviewer/CConn.cxx
Logged In: YES
user_id=2006887
Originator: YES
Attached path for the unix version aswell, not tested though!
File Added: CCon.patch
Patch against unix/wncviewer/CConn.cxx