aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorConstantin Kaplinsky <const@tightvnc.com>2006-12-04 11:23:45 +0000
committerConstantin Kaplinsky <const@tightvnc.com>2006-12-04 11:23:45 +0000
commitea3bf4cbcda858e05ffc5c6f8a0f92d4aae0ac17 (patch)
treeac66cffd9a9979014c7702842a1616c1aa7d7c13
parentf3209c6ef9d3b0ad0aeec14dd7225956a585b849 (diff)
downloadtigervnc-ea3bf4cbcda858e05ffc5c6f8a0f92d4aae0ac17.tar.gz
tigervnc-ea3bf4cbcda858e05ffc5c6f8a0f92d4aae0ac17.zip
A FIXME comment: TightVNC extensions support is not finished yet.
git-svn-id: svn://svn.code.sf.net/p/tigervnc/code/trunk@2173 3789f03b-4d11-0410-bbf8-ca57d06f2519
-rw-r--r--common/rfb/SConnection.cxx3
1 files changed, 3 insertions, 0 deletions
diff --git a/common/rfb/SConnection.cxx b/common/rfb/SConnection.cxx
index 876600ba..deaa9668 100644
--- a/common/rfb/SConnection.cxx
+++ b/common/rfb/SConnection.cxx
@@ -253,6 +253,9 @@ void SConnection::offerAuthentication()
if (caps.getSize() < 1)
throwConnFailedException("No supported security types");
+ // FIXME: We should never send an empty capability list if we are prompting
+ // local user to accept client connections. And if we do send an
+ // empty list, then we cannot send a "security result".
if (caps.includesOnly(secTypeNone)) {
// Special case - if caps includes nothing else than secTypeNone, we send
// an empty capability list and do not expect security type selection from