Inferencium/website
1
0
Fork 0
Code Issues Activity

Update Key page.

Browse Source
This commit is contained in:
inference 2023-01-13 21:02:22 +00:00
parent 5e7dc6a8b4
commit 3d6343043c
Signed by: inference
SSH Key Fingerprint: SHA256:9Pl0nZ2UJacgm+IeEtLSZ4FOESgP1eKCtRflfPfdX9M
1 changed files with 7 additions and 44 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

51
key.html
View File

@ -5,7 +5,7 @@
<!-- Copyright 2022-2023 Inference --> <!-- Copyright 2022-2023 Inference -->
<!-- SPDX-License-Identifier: BSD-3-Clause-Clear --> <!-- SPDX-License-Identifier: BSD-3-Clause-Clear -->
<!-- Version: 0.0.0.0 --> <!-- Version: 1.0.0.1 -->
<html> <html>
@ -33,58 +33,21 @@
<body> <body>
<h1>Key</h1> <h1>Key</h1>
<br> <br>
<h2>End-to-end Encrypted Contact Methods</h2> <p>Note: Verification does not verify a person, only their devices, and can be defeated via coercion or other
<br>
<h3>Preferred</h3>
<p>Whenever possible, use the following contact methods; they allow verification to mitigate man-in-the-middle
attacks, have high security, and reasonable privacy.<br>
<br>
<p>Use the
<a href="key.html"
>keys</a> for each contact method to verify my devices.<br>
Note: Verification does not verify a person, only their devices, and can be defeated via coercion or other
force.</p> force.</p>
<br> <br>
<p><img class="logo-small" src="asset/img/logo-signal.png" <h2>End-to-end Encrypted Contact Methods</h2>
width="40px" height="40px"/> <br>
<a class="body-link" href="contact/signal.html"
>Signal</a><p>
<p><img class="logo-small" src="asset/img/logo-xmpp.png" <p><img class="logo-small" src="asset/img/logo-xmpp.png"
width="40px" height="40px"/> width="40px" height="40px"/>
<a class="body-link" href="contact/xmpp.html" <a class="body-link" href="contact/xmpp.html"
>XMPP</a><p> >XMPP</a><p>
<br> <br>
<br> <br>
<!-- Place metadata-free contact methods here. --> <h2>File and Git Signing</h2>
<!-- Clarify that preferred methods should be used whenever possible. -->
<h3>Metadata-free</h3>
<p>If metadata leakage is an issue for you, you can use the following contact methods.<br>
<br> <br>
Note: These services do not have verification functionality and will be treated as less secure; <strong>unless <p><a class="body-link" href="key/ssh.html"
you really need to use these services, use a preferred method instead.</strong></p> >SSH</a></p>
<br>
<p><img class="logo-small" src="asset/img/logo-briar.png"
width="40px" height="40px"/>
<a class="body-link" href="contact/briar.html"
>Briar</a></p>
<p><img class="logo-small" src="asset/img/logo-session.png"
width="40px" height="40px"/>
<a class="body-link" href="contact/session.html"
>Session</a></p>
<br>
<br>
<br>
<!-- Place non-private contact methods here. -->
<!-- Clarify that these contact methods are for public contact only. -->
<h2>Non-private Contact Methods</h2>
<p>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.</p>
<br>
<p><img class="logo-small" src="asset/img/logo-pleroma.png"
width="40px" height="40px"/>
<a class="body-link" href="https://plr.inferencium.net/inference/"
>Fediverse</a></p>
<br> <br>
<br> <br>
</body> </body>