Recent changes to patches

#5 Unable to connect with security types in config file

Martin Koegler — Sat, 13 Dec 2014 08:59:35 -0000

VeNCrypt is dead.

The project has been merged into http://tigervnc.org/

Unable to connect with security types in config file

eymre — Fri, 12 Dec 2014 23:15:10 -0000

Steps to reproduce:
1. Start VeNCrypt
2. Connect to a server
3. Options->Load/Save->Configuration File:Save, store password
4. Close VeNCrypt
5. Start VeNCrypt with command line >vencviewer.exe myconnection.vnc

Expected: Connection is made
Actual:
- Message box is displayed, click yes:
VeNCrypt Viewer : Question
No matching security types
Do you wish to attempt to reconnect to sca-lx-08:22?
Yes/No
- Same message is displayed again, click yes
- Program crashes:
VeNCrypt Viewer for Win32 has stopped working
A problem caused the program to stop working correctly. Please close the program.
[Close the program]

Workaround:
Comment out the PreferredTypes line in the config file

RealVNC scaling patch for vncviewer

Anonymous — Tue, 17 Nov 2009 10:16:39 -0000

Allows you to scale the viewer window instead of using scrollbars. Pretty similar to tightvnc scaling. Please merge!

Hostname validation checks ip address

Wed, 13 Feb 2008 13:51:20 -0000

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.

Segfault on shutdown

Anonymous — Tue, 12 Feb 2008 13:17:40 -0000

There is a segfault on application shutdown due to double freeing of two char pointers.

CA and CRL file mismatch when loading defaults (win32)

Tue, 12 Feb 2008 07:55:19 -0000

There is a problem in the Windows version of VeNCrypt when loading the defaults from the registry where the contents of x509ca overwrites the contents of x509crl which in turn will always make the CRL loading fail since they cannot load the same file.