From a0766ff728fd76763c3b5bb4f724e60d37736c32 Mon Sep 17 00:00:00 2001 From: He4eT Date: Wed, 15 Apr 2026 19:44:40 +0200 Subject: [PATCH] posts: encrypted_XMPP: update draft --- src/pages/posts/2026/encrypted_XMPP.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/src/pages/posts/2026/encrypted_XMPP.md b/src/pages/posts/2026/encrypted_XMPP.md index 1950f92..12b8e71 100644 --- a/src/pages/posts/2026/encrypted_XMPP.md +++ b/src/pages/posts/2026/encrypted_XMPP.md @@ -117,8 +117,6 @@ and can derive a hash from them, commonly called a fingerprint. Keys are usually managed automatically by the XMPP client, and in normal use you should never need to handle them manually. In fact, you probably don’t even need to know what they look like. -The only thing you need to do is keep them secret -and back them up if necessary. A fingerprint lets you identify a specific client of your contact and verify that it hasn’t been spoofed.