Inferencium/website
1
0
Fork 0
Code Issues Activity

Add HTML sections.

Browse Source
This commit is contained in:
inference 2023-06-26 02:30:14 +01:00
parent a42f11d56f
commit 44264f740c
Signed by: inference
SSH Key Fingerprint: SHA256:9Pl0nZ2UJacgm+IeEtLSZ4FOESgP1eKCtRflfPfdX9M
1 changed files with 103 additions and 91 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
blog/untrusted_the_issue_with_decentralisation.html
View File

@ -5,7 +5,7 @@
<!-- Copyright 2022 Jake Winters -->
<!-- SPDX-License-Identifier: BSD-3-Clause -->
<!-- Version: 4.1.0.22 -->
<!-- Version: 4.1.0.23 -->
<html>
@ -32,6 +32,7 @@
<p class="update_date">Posted: 2022-06-30 (UTC+00:00)</p>
<p class="update_date">Updated: 2022-10-29 (UTC+00:00)</p>
<!-- Table of contents -->
<section id="toc">
<h2 id="toc"><a href="#toc" class="h2">Table of Contents<a/></h2>
<ul>
<li><a href="#introduction" class="body-link">Introduction</a></li>
@ -42,6 +43,8 @@
<li><a href="#solution" class="body-link">Solution</a></li>
<li><a href="#conclusion" class="body-link">Conclusion</a></li>
</ul>
</section>
<section id="introduction">
<h2 id="introduction"><a href="#introduction" class="h2">Introduction</a></h2>
<p>A recent trend is seeing people move towards decentralised services and platforms. While this is
reasonable and I can understand why they are doing such a thing, they are seemingly doing it without
@ -49,7 +52,10 @@
there is no way to pin a key to a specific person, to ensure that you are communicating with the
same person you are supposed to be communicating with. In this article, I will discuss some of the
security issues with the decentralised model.</p>
</section>
<section id="examples">
<h2 id="examples"><a href="#examples" class="h2">Examples</a></h2>
<section id="examples-messaging">
<h3 id="examples-messaging"><a href="#examples-messaging" class="h3">Messaging</a></h3>
<p>When it comes to messaging your contacts on a centralised platform, such as Twitter or Facebook,
the keys are pinned to that user account, using the user's password as the method of identification.
@ -72,6 +78,9 @@
literally no way to know if the person you are communicating with is the real person or an imposter;
there is no root of trust. This point is fatal; game over. The only way to establish trust again
would be to physically meet and exchange keys.</p>
</section>
</section>
<section id="solution">
<h2 id="solution"><a href="#solution" class="h2">Solution</a></h2>
<p>I'll cut to the chase; there isn't a definitive solution. The best way to handle this situation
is to design your threat model and think about your reasoning for avoiding centralised platforms. Is
@ -106,6 +115,8 @@
currently available to me. While the domain name registrar or virtual private server host could
tamper with my domain and data, they are the most trustworthy parties available. In its current
form, decentralisation would make this impossible to implement in any form.</p>
</section>
<section id="conclusion">
<h2 id="conclusion"><a href="#conclusion" class="h2">Conclusion</a></h2>
<p>Do not demand anonymity; demand privacy and control of your own data. Complete anonymity makes it
impossible to have a root of trust, and is typically never necessary. It is possible for someone
@ -124,5 +135,6 @@
Decentralisation does not solve the government issue. In order to live a happy, fun, and fulfilled
life, while protecting yourself against logical threats, there are only two words you must live by:
Threat model.</p>
</section>
</body>
</html>