Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
faq:matrix:known_issue_decrypting_previous_messages [2024/06/05 08:20] – fixing heading level onionfaq:matrix:known_issue_decrypting_previous_messages [2024/06/05 08:22] (current) – remove fediverse tag, typo fix in one of the titles, minor addition onion
Line 1: Line 1:
-{{tag>faq matrix fediverse}}+{{tag>faq matrix }}
 ====== Known issue decrypting previous messages ====== ====== Known issue decrypting previous messages ======
 There's a big known known issue where when signing into a new session, cross-signing does not work, you cannot verify the session in any way (not even with the security key) and/or access the Secure Backup. This seems to be caused by a bug in the current (as of writing) Element web interface as well as some third party clients, which actually causes the client not to be able to use the Secure Storage which is used for both for the Secure Backup as the Cross Signing key.  There's a big known known issue where when signing into a new session, cross-signing does not work, you cannot verify the session in any way (not even with the security key) and/or access the Secure Backup. This seems to be caused by a bug in the current (as of writing) Element web interface as well as some third party clients, which actually causes the client not to be able to use the Secure Storage which is used for both for the Secure Backup as the Cross Signing key. 
Line 42: Line 42:
   * "Never send encrypted messages to unverified sessions in this room from this session" for a specific room.   * "Never send encrypted messages to unverified sessions in this room from this session" for a specific room.
  
-If this is the case, due to the cause of the issue, you most likely will only see ''%%unable to decrypt%%'' when they send a message either one on one or in an encrypted room. The temporary workaround is the same as below.+If this is the case, due to the cause of the issue, you most likely will only see ''%%unable to decrypt%%'' when they send a message either one on one or in an encrypted room. The temporary workaround is the same as below, or for them temporarily disable the relevant setting(s).
  
-===== Talking to people when decrypting is not working broken =====+===== Talking to people when decryption is not working  =====
 The only way to talk to people while this is broken and retain history, is in an unencrypted room.  Create a new room, make sure to leave it fully unencrypted in the settings, then invite the person or persons you'd like to talk too.  The only way to talk to people while this is broken and retain history, is in an unencrypted room.  Create a new room, make sure to leave it fully unencrypted in the settings, then invite the person or persons you'd like to talk too.