Signed-off-by: Martin Koegler mkoeg...@auto.tuwien.ac.at
---
java/src/com/tigervnc/vncviewer/RfbProto.java | 16
1 files changed, 12 insertions(+), 4 deletions(-)
diff --git a/java/src/com/tigervnc/vncviewer/RfbProto.java
b/java/src/com/tigervnc/vncviewer/RfbProto.java
index
Signed-off-by: Martin Koegler mkoeg...@auto.tuwien.ac.at
---
java/src/com/tigervnc/vncviewer/RfbProto.java | 33 +-
java/src/com/tigervnc/vncviewer/VncViewer.java | 43 ++-
2 files changed, 58 insertions(+), 18 deletions(-)
diff --git
Signed-off-by: Martin Koegler mkoeg...@auto.tuwien.ac.at
---
common/rfb/ConnParams.cxx |2 +-
common/rfb/ConnParams.h|1 -
common/rfb/SConnection.cxx | 170
common/rfb/SConnection.h |9 ---
4 files changed, 1 insertions(+), 181
Signed-off-by: Martin Koegler mkoeg...@auto.tuwien.ac.at
---
java/src/com/tigervnc/vncviewer/Makefile|4 +-
java/src/com/tigervnc/vncviewer/RfbProto.java |8 ++
java/src/com/tigervnc/vncviewer/VncViewer.java | 15
java/src/com/tigervnc/vncviewer/X509Tunnel.java | 103
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
Signed-off-by: Martin Koegler mkoeg...@auto.tuwien.ac.at
---
java/src/com/tigervnc/vncviewer/Dialog.java | 80 ++
java/src/com/tigervnc/vncviewer/Makefile|6 +-
java/src/com/tigervnc/vncviewer/MessageBox.java | 82 +++
3 files changed,
Signed-off-by: Martin Koegler mkoeg...@auto.tuwien.ac.at
---
java/src/com/tigervnc/vncviewer/AuthPanel.java | 13 +++--
java/src/com/tigervnc/vncviewer/VncViewer.java | 31 +++-
2 files changed, 40 insertions(+), 4 deletions(-)
diff --git
Signed-off-by: Martin Koegler mkoeg...@auto.tuwien.ac.at
---
common/rfb/SConnection.cxx|2 +-
java/src/com/tigervnc/vncviewer/RfbProto.java |2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/common/rfb/SConnection.cxx b/common/rfb/SConnection.cxx
Signed-off-by: Martin Koegler mkoeg...@auto.tuwien.ac.at
---
java/src/com/tigervnc/vncviewer/Makefile |4 +-
java/src/com/tigervnc/vncviewer/RfbProto.java | 13 +++
java/src/com/tigervnc/vncviewer/TLSTunnel.java | 51
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
On Sun, Nov 07, 2010 at 12:52:54PM -0600, DRC wrote:
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
11 matches
Mail list logo