From 3d6343043c1a86a554b596d09d94a74922a99523 Mon Sep 17 00:00:00 2001 From: inference Date: Fri, 13 Jan 2023 21:02:22 +0000 Subject: [PATCH] Update Key page. --- key.html | 51 +++++++-------------------------------------------- 1 file changed, 7 insertions(+), 44 deletions(-) diff --git a/key.html b/key.html index 13e0e7b..7c2113c 100644 --- a/key.html +++ b/key.html @@ -5,7 +5,7 @@ - + @@ -33,58 +33,21 @@

Key


-

End-to-end Encrypted Contact Methods

-
-

Preferred

-

Whenever possible, use the following contact methods; they allow verification to mitigate man-in-the-middle - attacks, have high security, and reasonable privacy.
-
-

Use the - keys for each contact method to verify my devices.
- Note: Verification does not verify a person, only their devices, and can be defeated via coercion or other +

Note: Verification does not verify a person, only their devices, and can be defeated via coercion or other force.


-

- Signal

+

End-to-end Encrypted Contact Methods

+

XMPP



- - -

Metadata-free

-

If metadata leakage is an issue for you, you can use the following contact methods.
+

File and Git Signing


- Note: These services do not have verification functionality and will be treated as less secure; unless - you really need to use these services, use a preferred method instead.

-
-

- Briar

-

- Session

-
-
-
- - -

Non-private Contact Methods

-

The following contact methods do not utilise end-to-end encryption, or I do not use such functionality; they - are suitable for public contact only, including directly and groups. Do not use these methods if confidentiality - and/or privacy is required.

-
-

- Fediverse

+

SSH