mirror of
https://github.com/simplex-chat/simplex-chat.git
synced 2026-05-25 22:54:29 +00:00
deploy: 45b7d09f83
This commit is contained in:
@@ -72,8 +72,8 @@
|
||||
<p>Please report the cases when messages are not delivered – delivery receipts should help with that.</p>
|
||||
<h4 id="messages-failed-to-decrypt-problem-solved" tabindex="-1">Messages failed to decrypt? Problem solved!</h4>
|
||||
<p>Previously, a growing number of users had the issue when after restoring the chat database from backup, messages from some contacts failed to decrypt and were showing an error in the app.</p>
|
||||
<p>This happens due to double ratchet protocol protecting the integrity of end-to-end encryption after the compromise - <a href="https://simplex.chat/blog/docs/GLOSSARY.html#post-compromise-security">post-compromise security</a>. The protocol logic does not allow to use the old version of the database to decrypt the message.</p>
|
||||
<p>v5.2 added the extension to the messaging protocol allowing to negotiate the new ratchet keys in such cases - both with the contacts and the group members. This requires a user action, and it resets the security code verification status for this contact or member – you need to verify it again to have the additional protection from <a href="https://simplex.chat/blog/docs/GLOSSARY.html#man-in-the-middle-attack">man-in-the-middle attacks</a>.</p>
|
||||
<p>This happens due to double ratchet protocol protecting the integrity of end-to-end encryption after the compromise - <a href="https://simplex.chat/blog/docs/glossary.html#post-compromise-security">post-compromise security</a>. The protocol logic does not allow to use the old version of the database to decrypt the message.</p>
|
||||
<p>v5.2 added the extension to the messaging protocol allowing to negotiate the new ratchet keys in such cases - both with the contacts and the group members. This requires a user action, and it resets the security code verification status for this contact or member – you need to verify it again to have the additional protection from <a href="https://simplex.chat/blog/docs/glossary.html#man-in-the-middle-attack">man-in-the-middle attacks</a>.</p>
|
||||
<p>The negotiation of the new ratchet keys still happens via the end-to-end encrypted messages, as the protocol has two layers of end-to-end encryption, so it cannot be compromised by the messaging relays.</p>
|
||||
<p>You may still lose connection if you or your contact changed the receiving address after you made the backup, so make sure to make a new backup after any receiving address changes.</p>
|
||||
<h4 id="reconnect-the-servers" tabindex="-1">Reconnect the servers</h4>
|
||||
@@ -181,7 +181,7 @@
|
||||
<h2 id="customize-and-share-color-themes" tabindex="-1">Customize and share color themes</h2>
|
||||
<img src="https://simplex.chat/blog/images/20230523-theme.png" width="288" />
|
||||
<p>Android app now allows choosing between three color themes - Light, Dark and SimpleX (a dark blue theme). You can customize any theme by setting 9 different colors used in the app, including titles, menus, accent colors and colors for sent and received messages.</p>
|
||||
<p>You can share your theme with other users by exporting it to a file and sending to them. You can also <a href="https://simplex.chat/blog/docs/THEMES.html">contribute your favorite themes</a> to our GitHub repository.</p>
|
||||
<p>You can share your theme with other users by exporting it to a file and sending to them. You can also <a href="https://simplex.chat/blog/docs/themes.html">contribute your favorite themes</a> to our GitHub repository.</p>
|
||||
<h2 id="self-destruct-passcode" tabindex="-1">Self-destruct passcode</h2>
|
||||
<img src="https://simplex.chat/blog/images/20230523-self-destruct.png" width="288" />
|
||||
<p>This is something many of you asked before - when asked to enter the app passcode under duress, to be able to enter a special self-destruct code that would remove the app data. This feature is offered in many security tools, and now you can configure it in SimpleX Chat as well.</p>
|
||||
|
||||
Reference in New Issue
Block a user