aboutsummaryrefslogtreecommitdiffstats
path: root/common/rfb/SSecurityRSAAES.cxx
diff options
context:
space:
mode:
authorPierre Ossman <ossman@cendio.se>2024-12-17 12:18:09 +0100
committerPierre Ossman <ossman@cendio.se>2024-12-17 12:19:55 +0100
commit2b803c94ed0cd126af13b752ddc038e320565dbd (patch)
treed039cd535ccb7d9fc4f50b745a6e3a57462a391b /common/rfb/SSecurityRSAAES.cxx
parent24a89098ffa13b33bc5bb712530e1e19ee948823 (diff)
downloadtigervnc-2b803c94ed0cd126af13b752ddc038e320565dbd.tar.gz
tigervnc-2b803c94ed0cd126af13b752ddc038e320565dbd.zip
Fix bad restore point handling in RSA-AES handler
A set restore point needs to be used or cleared. Release builds will let this slide, but debug builds will kill the connection.
Diffstat (limited to 'common/rfb/SSecurityRSAAES.cxx')
-rw-r--r--common/rfb/SSecurityRSAAES.cxx2
1 files changed, 1 insertions, 1 deletions
diff --git a/common/rfb/SSecurityRSAAES.cxx b/common/rfb/SSecurityRSAAES.cxx
index 46b66ca9..39b286de 100644
--- a/common/rfb/SSecurityRSAAES.cxx
+++ b/common/rfb/SSecurityRSAAES.cxx
@@ -540,9 +540,9 @@ void SSecurityRSAAES::writeSubtype()
bool SSecurityRSAAES::readCredentials()
{
- rais->setRestorePoint();
if (!rais->hasData(1))
return false;
+ rais->setRestorePoint();
uint8_t lenUsername = rais->readU8();
if (!rais->hasDataOrRestore(lenUsername + 1))
return false;