Use {C,S}Security instead of {C,S}SecurityStack objects in VeNCrypt routines.
Signed-off-by: Martin Koegler <mkoegler@auto.tuwien.ac.at>
git-svn-id: svn://svn.code.sf.net/p/tigervnc/code/trunk@4095 3789f03b-4d11-0410-bbf8-ca57d06f2519
diff --git a/common/rfb/SSecurityVeNCrypt.cxx b/common/rfb/SSecurityVeNCrypt.cxx
index 860e440..b8f9b57 100644
--- a/common/rfb/SSecurityVeNCrypt.cxx
+++ b/common/rfb/SSecurityVeNCrypt.cxx
@@ -62,7 +62,7 @@
SSecurityVeNCrypt::SSecurityVeNCrypt(void)
{
- ssecurityStack = NULL;
+ ssecurity = NULL;
haveSentVersion = false;
haveRecvdMajorVersion = false;
haveRecvdMinorVersion = false;
@@ -186,7 +186,7 @@
case secTypeX509None:
case secTypeX509Vnc:
case secTypeX509Plain:
- ssecurityStack = SSecurityVeNCrypt::getSSecurityStack(chosenType);
+ ssecurity = SSecurityVeNCrypt::getSSecurityStack(chosenType);
break;
case secTypeInvalid:
case secTypeVeNCrypt: /* This would cause looping */
@@ -197,7 +197,7 @@
}
/* continue processing the messages */
- return ssecurityStack->processMsg(sc);
+ return ssecurity->processMsg(sc);
}
SSecurityStack* SSecurityVeNCrypt::getSSecurityStack(int secType)