diff --git a/blog/untrusted_the_issue_with_decentralisation.html b/blog/untrusted_the_issue_with_decentralisation.html index da381c5..fcbfe2c 100644 --- a/blog/untrusted_the_issue_with_decentralisation.html +++ b/blog/untrusted_the_issue_with_decentralisation.html @@ -5,7 +5,7 @@ - + @@ -123,25 +123,24 @@

In order to have a root of trust, I have posted my keys to my website, which is protected by multiple layers of security:

- 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.
-
- 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.
-
- 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.
-
- 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.
-
- 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.

+
    +
  1. 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.
    2. +
  2. 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.
    3. +
  3. 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.
    4. +
  4. 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.
    5. +
+
+

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.