Inferencium/website
1
0
Fork 0
Code Issues Activity

Switch from hyphen-formatted list to HTML ordered list.

Browse Source
This commit is contained in:
inference 2023-03-14 05:55:44 +00:00
parent 9ef8c5a8b4
commit ed1f257bc4
Signed by: inference
SSH Key Fingerprint: SHA256:9Pl0nZ2UJacgm+IeEtLSZ4FOESgP1eKCtRflfPfdX9M
1 changed files with 19 additions and 20 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

39
blog/untrusted_the_issue_with_decentralisation.html
View File

@ -5,7 +5,7 @@
<!-- Copyright 2022-2023 Jake Winters -->
<!-- SPDX-License-Identifier: BSD-3-Clause-Clear -->
<!-- Version: 3.1.0.12 -->
<!-- Version: 3.2.0.13 -->
<html>
@ -123,25 +123,24 @@
<p>In order to have a root of trust, I have posted my keys to my website, which is protected by
multiple layers of security:<br>
<br>
0. I have provided identification to my domain name registrar, to ensure I can access the website I
rightfully own, should it be compromised, by providing identification to the domain name
registrar.<br>
<br>
1. I have provided identification to my virtual private server host, to ensure I can access the
virtual private servers I rightfully rent, should they be compromised, by providing identification
to the virtual private server host.<br>
<br>
2. I have pinned my website to a globally trusted certificate authority, Let's Encrypt, which is a
trusted party to manage TLS certificates and ensure ownership of the domain when connecting to
it.<br>
<br>
3. I have enabled DNSSEC on my domain, so it is extremely difficult to spoof my domain to make you
believe you're connecting to it when you're actually connecting to someone else's.<br>
<br>
While not the most secure implementation of a root of trust, it is the most secure implementation
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>
<ol>
<li>I have provided identification to my domain name registrar, to ensure I can access the website I
rightfully own, should it be compromised, by providing identification to the domain name
registrar.</li>
<li>I have provided identification to my virtual private server host, to ensure I can access the
virtual private servers I rightfully rent, should they be compromised, by providing identification
to the virtual private server host.</li>
<li>I have pinned my website to a globally trusted certificate authority, Let's Encrypt, which is a
trusted party to manage TLS certificates and ensure ownership of the domain when connecting to
it.</li>
<li>I have enabled DNSSEC on my domain, so it is extremely difficult to spoof my domain to make you
believe you're connecting to it when you're actually connecting to someone else's.</li>
</ol>
<br>
<p>While not the most secure implementation of a root of trust, it is the most secure implementation
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>
<br>
<br>