From 852110debd39e0b05bf897c93dbaa8f7dece3282 Mon Sep 17 00:00:00 2001 From: Joshua Goins Date: Sat, 19 Aug 2023 16:09:09 -0400 Subject: [PATCH] Make it clear that the session is broken when the keys are lost If you use your private keys (like when deleting the quotient database) your session is broken as you have differing keys on the server. While it is possible to work your way out of it, it's better to warn users to bite the bullet and log in again. --- src/qml/VerificationCanceled.qml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/qml/VerificationCanceled.qml b/src/qml/VerificationCanceled.qml index 32bbcae24..14c7be31f 100644 --- a/src/qml/VerificationCanceled.qml +++ b/src/qml/VerificationCanceled.qml @@ -40,7 +40,7 @@ Message { case KeyVerificationSession.KEY_MISMATCH: return i18n("The session verification was canceled because the keys are incorrect."); case KeyVerificationSession.REMOTE_KEY_MISMATCH: - return i18n("The remote party canceled the session verification because the keys are incorrect."); + return i18n("The remote party canceled the session verification because the keys are incorrect.\n\n**Please log out and log back in, your session is broken/corrupt.**"); case KeyVerificationSession.USER_MISMATCH: return i18n("The session verification was canceled because it verifies an unexpected user."); case KeyVerificationSession.REMOTE_USER_MISMATCH: