TurboVNC 1.0 uses the Tight security type to implement its auth extensions, and it relies upon the ability to advertise capabilities to the client using that mechanism. Whether or not the Tight security type actually does anything in our implementation, I think it is important to be able to advertise capabilities using that method.
On 11/7/10 10:50 AM, Martin Koegler wrote: > This patchset updates the java code so that it can support all VeNCrypt > security > types. > > On thing I noticed, is that the tigervnc server and java client (but not the > unix/win client) > support the TightVNC security type. > > This security type is selected by default, if it is supported by server and > client. It only supports > None+VncAuth as security types. Therefore such a combination can not use any > VeNCrypt security types. > Instead it allows to first select a tunnel type and then an authentification > type. The second feature > is, that it allows the server to send capabilites to the client. > > As my encryption patches as Tightvnc tunneling types were not well received > and the Tightvnc security > type is not used in the C code, I took the aproach to disable the TightVNC > security type (patch 8). > > patch 9+10 rip the support out of the code (optional). > > If somebody thinks, that the tightvnc security type should stay, we need to > determine, how > VeNCrypt should be added to the tightvnc protocol. > > Please note, that this does not affect the Tightvnc encoding. > > patch 1-7 update the java code to support all VeNCrypt security types: > * patch 1 adds constants > * patch 2 implements the chooser > * patch 3 updates the authentification panel, so that it can ask for username > or password > * patch 4 implements the plain security type > * patch 5 adds a message box implementation > * patch 6 implements the TLS* security types > * patch 7 implements the X509* security types > > There is room for lots of improvements (eg. X509 has no mean to get a > certificate to check against => > every certificate is flagged as untrusted), if others want to spend their > time. > > After adding these patches, everything feature from VeNCrypt, I'm aware of, > has been ported to > tigervnc. A new release of tigervnc with precompiled, GNUTLS enabled windows > binaries and the > VeNCrypt project can be declared as superseded. > > Regards, > Maritn Kögler > > Martin Koegler (10): > 1. Add VeNCrypt security types > 2. Implement VeNCrypt chooser > 3. Support asking for a user name > 4. Implement Plain Security type > 5. Add simple Message Box implementation > 6. Implment TLS security type > 7. Implement X509 Security types > 8. Disable TightVNC security type > 9. Remove TightVNC security type from server > 10. Remove Tightvnc Security type from java client > > common/rfb/ConnParams.cxx | 2 +- > common/rfb/ConnParams.h | 1 - > common/rfb/SConnection.cxx | 170 --------------- > common/rfb/SConnection.h | 9 - > java/src/com/tigervnc/vncviewer/AuthPanel.java | 13 +- > java/src/com/tigervnc/vncviewer/Dialog.java | 80 +++++++ > java/src/com/tigervnc/vncviewer/Makefile | 6 +- > java/src/com/tigervnc/vncviewer/MessageBox.java | 82 +++++++ > java/src/com/tigervnc/vncviewer/RfbProto.java | 227 > +++++++------------- > java/src/com/tigervnc/vncviewer/TLSTunnel.java | 51 +++++ > java/src/com/tigervnc/vncviewer/TLSTunnelBase.java | 86 ++++++++ > java/src/com/tigervnc/vncviewer/VncViewer.java | 120 ++++++++--- > java/src/com/tigervnc/vncviewer/X509Tunnel.java | 103 +++++++++ > 13 files changed, 588 insertions(+), 362 deletions(-) > create mode 100644 java/src/com/tigervnc/vncviewer/Dialog.java > create mode 100644 java/src/com/tigervnc/vncviewer/MessageBox.java > create mode 100644 java/src/com/tigervnc/vncviewer/TLSTunnel.java > create mode 100644 java/src/com/tigervnc/vncviewer/TLSTunnelBase.java > create mode 100644 java/src/com/tigervnc/vncviewer/X509Tunnel.java > > > > > > ------------------------------------------------------------------------------ > The Next 800 Companies to Lead America's Growth: New Video Whitepaper > David G. Thomson, author of the best-selling book "Blueprint to a > Billion" shares his insights and actions to help propel your > business during the next growth cycle. Listen Now! > http://p.sf.net/sfu/SAP-dev2dev > > > > _______________________________________________ > Tigervnc-devel mailing list > Tigervnc-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/tigervnc-devel ------------------------------------------------------------------------------ The Next 800 Companies to Lead America's Growth: New Video Whitepaper David G. Thomson, author of the best-selling book "Blueprint to a Billion" shares his insights and actions to help propel your business during the next growth cycle. Listen Now! http://p.sf.net/sfu/SAP-dev2dev _______________________________________________ Tigervnc-devel mailing list Tigervnc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tigervnc-devel
