Verified session is shown as 'Not trusted'

<!-- All bug reports must provide the following background information Text between <!-- and --​> marks will be invisible in the report. IF YOUR ISSUE IS CONSIDERED A SECURITY VULNERABILITY THEN PLEASE STOP AND DO NOT POST IT AS A GITHUB ISSUE! Please report the issue responsibly by disclosing in private by email to security@matrix.org instead. For more details, please see: https://www.matrix.org/security-disclosure-policy/ --> ### Background information <!-- Please include versions of all software when known e.g database versions, docker versions, client versions --> - **Dendrite version or git SHA**: /etc/dendrite # 0.13.7+14a6c10 - **SQLite3 or Postgres?**: postgres - **Running in Docker?**: yes - **`go version`**: - **Client used (if applicable)**: Any client ### Description - **What** is the problem: Some verified sessions shown as 'Not Trusted' to others if contact verified after session - **Who** is affected: Any who verify my contact after I've added new session - **How** is this bug manifesting: Your contact shown as not trusted to others when then verify you - **When** did this first appear: When I register new session with other device after contact verification session AG3_a329 is Verified. Marked as green and all seems nice. <img width="692" alt="Screenshot 2024-09-02 at 18 16 46" src="https://github.com/user-attachments/assets/4b14ccae-94a6-43f5-92c2-3a129abbbdf1"> session AG3_a329 shown as not trusted <img width="348" alt="Screenshot 2024-09-02 at 18 15 50" src="https://github.com/user-attachments/assets/87b12284-1fe9-4340-8c80-29c1650447cb"> Refreshing clients does not help. Problem is reproduces on app.element.io <!-- Examples of good descriptions: - What: "I cannot log in, getting HTTP 500 responses" - Who: "Clients on my server" - How: "Errors in the logs saying 500 internal server error" - When: "After upgrading to 0.3.0" - What: "Dendrite ran out of memory" - Who: "Server admin" - How: "Lots of logs about device change updates" - When: "After my server joined Matrix HQ" Examples of bad descriptions: - What: "Can't send messages" - This is bad because it isn't specfic enough. Which endpoint isn't working and what is the response code? Does the message send but en cryption fail? - Who: "Me" - Who are you? Running the server or a user on a Dendrite server? - How: "Can't send messages" - Same as "What". - When: "1 day ago" - It's impossible to know what changed 1 day ago without further input. --> ### Steps to reproduce <!-- Please try reproducing this bug before submitting it. Issues which cannot be reproduced risk being closed. --> - create test account on homeserver - create test account on matrix.org - verify each other - register new session in homesever - session of test user shown as 'Not trusted' on matrix.org <!-- Describe how what happens differs from what you expected. If you can identify any relevant log snippets from server logs, please include those (please be careful to remove any personal or private data). Please surround them with ``` (three backticks, on a line on their own), so that they are formatted legibly. Alternatively, please send logs to @kegan:matrix.org, @s7evink:matrix.org or @devonh:one.ems.host with a link to the respective Github issue, thanks! -->