Properly clean up client VeNCrypt handling

We would leak the security module below the top client VeNCrypt module,
meaning that those modules would not get a chance to shut down
gracefully.

diff --git a/common/rfb/CSecurityVeNCrypt.cxx b/common/rfb/CSecurityVeNCrypt.cxx
index a6b270e17277b298c95140733304e2d29f1a6809..c0fe3273f041e390d21ae57452e57d15bb6ec02e 100644 (file)
--- a/common/rfb/CSecurityVeNCrypt.cxx
+++ b/common/rfb/CSecurityVeNCrypt.cxx
@@ -56,6 +56,7 @@ CSecurityVeNCrypt::CSecurityVeNCrypt(CConnection* cc, SecurityClient* sec)
 CSecurityVeNCrypt::~CSecurityVeNCrypt()
 {
   delete[] availableTypes;
+  delete csecurity;
 }
 
 bool CSecurityVeNCrypt::processMsg()