Trust Over IP - Revision history

Tom: /* Context */

2023-12-18T06:36:27Z

‎Context

Tom: /* Full Title or Meme */

2023-12-17T06:17:37Z

‎Full Title or Meme

Tom: /* References */

2023-12-17T05:50:20Z

‎References

Tom at 01:47, 17 December 2023

2023-12-17T01:47:06Z

Tom: Tom moved page Trust Over IP. to Trust Over IP without leaving a redirect: typo

2023-10-28T01:38:23Z

Tom moved page Trust Over IP. to Trust Over IP without leaving a redirect: typo

Tom at 23:38, 27 October 2023

2023-10-27T23:38:38Z

Tom: Created page with "==Full Title or Meme== One means of enabling trust ==References== [;Category: Trust]]"

2023-10-27T23:15:27Z

Created page with "==Full Title or Meme== One means of enabling trust ==References== [;Category: Trust]]"

New page

==Full Title or Meme==
One means of enabling [[trust]]

==References==

[;Category: Trust]]

@@ Line 6: / Line 6: @@
 *[https://www.trustoverip.org/news/2023/12/15/announcing-public-review-of-the-didwebs-method-specification/ did:webs Method Specification.] (2023-12-15)
 When DIDs were first invented, the inventors thought that someday there might be perhaps a dozen or so different types of DIDs, called DID methods. Their reasoning was that DIDs solved a very narrow problem—how to create a cryptographically-verifiable identifier—an identifier over which the controller (person, organization, device, bot, etc.) could prove control by virtue of having the associated private key. This new type of identifier would not need to be registered with any centralized authority and could not be spoofed or taken away by some other party (unless they could steal the private key).
@@ Line 20: / Line 19: @@
 did:web:example.com:user:alice
-It is that easy. The irony is that the did:web method was very nearly rejected by the W3C DID Working Group for two reasons: It is a stretch to call it decentralized since it depends on DNS domain names which require centralized registries. As a result, it inherits all of the security flaws of DNS, and then adds the additional vulnerabilities of storing a “naked” DID document on a web server. Since the DID document contains the public key associated with the DID, anyone who can manage to replace the real DID document with their own version can completely hijack the DID.
+Of course this is not decentralized since it depends on DNS domain names which require centralized registries. As a result, it inherits all of the security flaws of DNS, and then adds the additional vulnerabilities of storing a “naked” DID document on a web server. Since the DID document contains the public key associated with the DID, anyone who can manage to replace the real DID document with their own version can completely hijack the DID.
-For these reasons, once DID adoption started to kick in, it came as somewhat of a shock that did:web was proving to be so popular. In fact, some DID proponents became quite worried that the security issues with did:web might lead to a breach whose ensuing publicity might give all DIDs a bad name. Thankfully, as those concerns mounted, by the summer of 2023, no less than four independent groups all had the same basic insight: the flaws in did:web could be fixed by tunneling a self-certifying identifier inside a did:web string.
+For these reasons, once DID adoption started to kick in, it came as somewhat of a shock that did:web was proving to be so popular. In fact, some DID proponents became quite worried that the security vulnerabilitiess with did:web might lead to an exploit. Thankfully, as those concerns mounted, by the summer of 2023, no less than four independent groups all had the same basic insight: the vulnerabilities in did:web could be fixed by tunneling a self-certifying identifier inside a did:web string.
 ==References==
 [[Category: Trust]]

@@ Line 1: / Line 1: @@
 ==Full Title or Meme==
-One means of enabling [[trust]]
+One means of enabling [[trust]] which was introduced by the [[Verifiable Credential]] folk as Rebooting the Web of Trust.
 ==Context==

@@ Line 6: / Line 6: @@
 *[https://www.trustoverip.org/news/2023/12/15/announcing-public-review-of-the-didwebs-method-specification/ did:webs Method Specification.] (2023-12-15)
 ==References==
 [[Category: Trust]]

@@ Line 4: / Line 4: @@
 ==Context==
 The ToPI<ref>ToIP, ''Why Trust Over IP'' https://trustoverip.org/why-toip/overview/ </ref>
 ==References==
-[;Category: Trust]]
+[[Category: Trust]]

← Older revision	Revision as of 01:38, 28 October 2023
(No difference)