From 9eba6b5c9e97ea25b7d762181b62cd235dea8365 Mon Sep 17 00:00:00 2001 From: Johannes Marbach Date: Wed, 28 May 2025 12:05:15 +0200 Subject: [PATCH] Update content/client-server-api/modules/end_to_end_encryption.md Co-authored-by: Richard van der Hoff <1389908+richvdh@users.noreply.github.com> --- content/client-server-api/modules/end_to_end_encryption.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/client-server-api/modules/end_to_end_encryption.md b/content/client-server-api/modules/end_to_end_encryption.md index 50d673b3..2729f512 100644 --- a/content/client-server-api/modules/end_to_end_encryption.md +++ b/content/client-server-api/modules/end_to_end_encryption.md @@ -1567,7 +1567,7 @@ Ownership of the Curve25519 key is then established in one of two ways: 1. Via [cross-signing](#cross-signing). For this to be sufficient, the device keys structure must be signed by the sender's self-signing key, and that self-signing key must itself have been validated (either via - [explicit verification](#device-verification) or a TOFU mechanism). + [explicit verification](#device-verification) or a "trust on first use" (TOFU) mechanism). 2. Via explicit verification of the device's Ed25519 signing key, as contained in the device keys structure. This is no longer recommended.