Difference between revisions of "Trust Graph"
(→Context) |
(→Social Networks) |
||
| (6 intermediate revisions by the same user not shown) | |||
| Line 3: | Line 3: | ||
==Context== | ==Context== | ||
==Web of Trust== | ==Web of Trust== | ||
| + | ===Designed to create a [[Trust Graph]]=== | ||
Phil Zimmermann, the creator of Pretty Good Privacy (PGP). spoke and wrote explicitly and repeatedly about the Web of Trust as a deliberate alternative to centralized authority. Here is what he actually said, using direct statements and closely paraphrased explanations from his own writings and interviews. | Phil Zimmermann, the creator of Pretty Good Privacy (PGP). spoke and wrote explicitly and repeatedly about the Web of Trust as a deliberate alternative to centralized authority. Here is what he actually said, using direct statements and closely paraphrased explanations from his own writings and interviews. | ||
| Line 54: | Line 55: | ||
Chains of introductions | Chains of introductions | ||
Local decisions about whom to trust and how far that trust extends | Local decisions about whom to trust and how far that trust extends | ||
| − | |||
Why he believed it mattered politically | Why he believed it mattered politically | ||
| Line 66: | Line 66: | ||
No single point of failure | No single point of failure | ||
No institution that could be coerced into mass surveillance | No institution that could be coerced into mass surveillance | ||
| − | |||
One‑paragraph summary (faithful to Zimmermann) | One‑paragraph summary (faithful to Zimmermann) | ||
Phil Zimmermann described the Web of Trust as a decentralized, peer‑to‑peer system for establishing the validity of cryptographic keys without relying on central authorities. Trust, in his view, was a local, user‑defined mechanism for deciding who is competent to vouch for key ownership. He saw the Web of Trust not only as a technical solution, but as a civil‑liberties design choice that put control of privacy directly in the hands of individuals. [philzimmermann.com]. | Phil Zimmermann described the Web of Trust as a decentralized, peer‑to‑peer system for establishing the validity of cryptographic keys without relying on central authorities. Trust, in his view, was a local, user‑defined mechanism for deciding who is competent to vouch for key ownership. He saw the Web of Trust not only as a technical solution, but as a civil‑liberties design choice that put control of privacy directly in the hands of individuals. [philzimmermann.com]. | ||
| + | ===Why did it Fail=== | ||
| + | the Web of Trust didn’t fail because it was wrong — it failed because it asked too much of humans, too early, at Internet scale. | ||
| + | Below is a precise, historically grounded explanation of why Phil Zimmermann’s Web of Trust (WoT) did not achieve mass adoption, with each reason tied to documented critiques and evolution paths. | ||
| + | |||
| + | ====It required sustained human effort (and humans didn’t do it)==== | ||
| + | The Web of Trust depends on people manually verifying and signing each other’s keys. In practice: | ||
| + | |||
| + | Most users never verified fingerprints | ||
| + | Very few participated in key‑signing | ||
| + | Trust graphs stayed sparse | ||
| + | |||
| + | This low participation was widely observed and documented as the primary failure mode: few keys accumulated meaningful trust paths, making the system fragile and ineffective for most users. [undercodetesting.com] | ||
| + | Zimmermann himself acknowledged that the system relied on user judgment and supervision, which proved unrealistic outside expert communities. [mit.edu] | ||
| + | |||
| + | ====It was cognitively and UX‑heavy==== | ||
| + | Using the Web of Trust required users to understand: | ||
| + | |||
| + | Public vs private keys | ||
| + | Trust vs validity | ||
| + | Partial vs full trust | ||
| + | Trust path depth | ||
| + | Revocation, expiration, re‑signing | ||
| + | |||
| + | Even technically competent users found this confusing, and non‑technical users simply could not adopt it reliably. This usability barrier is repeatedly cited as a core reason for failure. [reddit.com], [ssh.com] | ||
| + | As a result, encryption tools that automated trust decisions replaced WoT in practice. [undercodetesting.com] | ||
| + | |||
| + | ====No strong network effect emerged==== | ||
| + | The Web of Trust relies on emergence — trust becoming valuable only once many people participate. | ||
| + | But adoption stalled before that tipping point: | ||
| + | |||
| + | If your contacts didn’t use PGP, WoT had no value | ||
| + | If WoT had no value, people didn’t use it | ||
| + | |||
| + | This classic “cold start” problem meant the Web of Trust never crossed into mainstream usefulness. [reddit.com] | ||
| + | |||
| + | ====Key servers became a weak link==== | ||
| + | Although the trust model was decentralized, key distribution wasn’t: | ||
| + | |||
| + | Public key servers accumulated massive numbers of stale, spoofed, or malicious keys | ||
| + | Revocation and update mechanisms were weak | ||
| + | Poisoning attacks became feasible | ||
| + | |||
| + | By the mid‑2010s, key server infrastructure was widely regarded as “broken,” undermining confidence in the Web of Trust ecosystem. [lupinepublishers.com], [link.springer.com] | ||
| + | |||
| + | ====It did not scale cleanly beyond small communities==== | ||
| + | The Web of Trust did work in: | ||
| + | Cryptography circles | ||
| + | Open‑source communities | ||
| + | Activist and journalist networks | ||
| + | |||
| + | But scaling it to enterprises, governments, or the general public proved impractical due to: | ||
| + | Lack of centralized policy enforcement | ||
| + | Difficulty automating trust decisions | ||
| + | Fragility under key churn and algorithm deprecation | ||
| + | |||
| + | Modern analyses explicitly recommend WoT only for small, expert communities. [axelspire.com] | ||
| + | |||
| + | ====Simpler trust models won in practice==== | ||
| + | Over time, the ecosystem shifted toward: | ||
| + | |||
| + | Hierarchical PKI (browsers, TLS) | ||
| + | Trust On First Use (TOFU) (SSH, Signal) | ||
| + | Platform‑managed identity (messaging apps) | ||
| + | |||
| + | These models traded philosophical purity for: | ||
| + | |||
| + | Automation | ||
| + | Predictability | ||
| + | Usability | ||
| + | |||
| + | This shift is well‑documented as a pragmatic response to WoT’s operational complexity. [undercodetesting.com] | ||
| + | |||
| + | ====Zimmermann’s design was ahead of its time==== | ||
| + | Crucially, many modern systems now revisit WoT ideas — but with: | ||
| + | Automation | ||
| + | Better UX | ||
| + | Verifiable credentials | ||
| + | Agent‑mediated trust | ||
| + | |||
| + | W3C and decentralized identity communities explicitly study WoT’s failure to avoid repeating it. [lists.w3.org] | ||
| + | In other words: the idea survived; the original implementation didn’t. | ||
| + | |||
| + | ====Not an Enterprise Solution==== | ||
| + | The Web of Trust did not solve enterprise Identity and Access problems. This problem was solved by [[Kerberos]], [[SAML]] and [[OIDC]]. The enterprise was willing to pay money for these solutions that gave them the control that they needed. | ||
| + | |||
| + | ====Verdict==== | ||
| + | The Web of Trust failed not because decentralized trust is impossible, but because PGP’s implementation depended on manual human behavior that does not scale, lacked usable tooling, never achieved network effects, and was undermined by weak key distribution infrastructure. It succeeded socially in small expert networks, but failed ergonomically and operationally for the general Internet. [undercodetesting.com], [axelspire.com] | ||
| + | |||
| + | ==Solutions== | ||
| + | |||
| + | ===Social Networks=== | ||
| + | Online social networks (OSNs) are becoming a popular method of meeting people and keeping in touch | ||
| + | with friends. OSNs resort to trust evaluation models and algorithms, as to improve service qualities and | ||
| + | enhance user experiences. Understanding Graph-based Trust Evaluation in Online Social | ||
| + | Networks: Methodologies and Challenges<ref>Wenjun Jiang, Guojun Wang, Md Zakirul Alam Bhuiyan, Jie Wu, ''Understanding Graph-based Trust Evaluation in Online Social Networks: Methodologies and Challenges'' ACM Computing Surveys, Vol. V, No. N, Article A 2016-02 ACM https://cis.temple.edu/~wu/research/publications/Publication_files/20160219-trustsurvey-acm.pdf</ref> | ||
==References== | ==References== | ||
[[Category: Trust]] | [[Category: Trust]] | ||
Latest revision as of 19:49, 24 February 2026
Contents
- 1 Definition
- 2 Context
- 3 Web of Trust
- 3.1 Designed to create a Trust Graph
- 3.2 Why did it Fail
- 3.2.1 It required sustained human effort (and humans didn’t do it)
- 3.2.2 It was cognitively and UX‑heavy
- 3.2.3 No strong network effect emerged
- 3.2.4 Key servers became a weak link
- 3.2.5 It did not scale cleanly beyond small communities
- 3.2.6 Simpler trust models won in practice
- 3.2.7 Zimmermann’s design was ahead of its time
- 3.2.8 Not an Enterprise Solution
- 3.2.9 Verdict
- 4 Solutions
- 5 References
Definition
Context
Web of Trust
Designed to create a Trust Graph
Phil Zimmermann, the creator of Pretty Good Privacy (PGP). spoke and wrote explicitly and repeatedly about the Web of Trust as a deliberate alternative to centralized authority. Here is what he actually said, using direct statements and closely paraphrased explanations from his own writings and interviews.
Zimmermann’s core idea: trust without central authorities Zimmermann introduced the Web of Trust to solve what he saw as the fundamental problem of public‑key cryptography:
How do you know a key really belongs to the person it claims to belong to, without relying on a central authority?
He rejected certificate authorities as the default answer and instead designed a peer‑to‑peer trust model. In The Evolution of PGP’s Web of Trust, Zimmermann explained:
The Web of Trust describes the way the system operates about as accurately as any phrase. It is a solution to the problem of connecting people who have never met and therefore never had a chance to exchange secure keys. [philzimmermann.com]
What “trust” meant to Zimmermann (and what it did not)
Zimmermann was careful to define trust narrowly and mechanically — not socially or emotionally.
He wrote:
Trust is the mechanism that is used to decide whether a key is valid. A key is valid if it is actually owned by the person who claims to own it. You tell PGP whom you trust to introduce keys; in return, PGP tells you which keys are valid. [philzimmermann.com]
So in Zimmermann’s model:
Trust ≠ believing someone is “good” Trust = believing someone is competent to vouch for key ownership
Why he opposed centralized PKI
Zimmermann explicitly designed the Web of Trust as an alternative to hierarchical certificate authorities (CAs). In explanations of PGP’s design, he emphasized that:
There is no central controlling authority
Each user issues and manages their own certificates Trust emerges from overlapping personal attestations
This reflected his political and civil‑liberties concerns. As summarized in a technical history of PGP based on his writings:
Zimmermann’s approach to digital certificate administration, with its “web of trust,” mirrors his concern that people should have the power to control their own privacy. PGP empowers people to take their privacy into their own hands. [hxmel.com]
“Web of Trust” as an early peer‑to‑peer network
Zimmermann later pointed out that the Web of Trust was historically significant beyond cryptography.
In Beautiful Security, he and Jon Callas wrote:
The Web of Trust was an early peer‑to‑peer design, and arguably one of the first social networks. [philzimmermann.com]
This was not metaphorical — the trust graph literally consisted of:
People signing other people’s keys Chains of introductions Local decisions about whom to trust and how far that trust extends
Why he believed it mattered politically Zimmermann consistently linked the Web of Trust to resistance against surveillance and control. In Why I Wrote PGP, he warned:
The government has a track record that does not inspire confidence that they will never abuse our civil liberties. To make cryptography harder to criminalize, use it as much as possible while it is legal. [hxmel.com]
The Web of Trust was part of that strategy:
No central authority to pressure No single point of failure No institution that could be coerced into mass surveillance
One‑paragraph summary (faithful to Zimmermann)
Phil Zimmermann described the Web of Trust as a decentralized, peer‑to‑peer system for establishing the validity of cryptographic keys without relying on central authorities. Trust, in his view, was a local, user‑defined mechanism for deciding who is competent to vouch for key ownership. He saw the Web of Trust not only as a technical solution, but as a civil‑liberties design choice that put control of privacy directly in the hands of individuals. [philzimmermann.com].
Why did it Fail
the Web of Trust didn’t fail because it was wrong — it failed because it asked too much of humans, too early, at Internet scale. Below is a precise, historically grounded explanation of why Phil Zimmermann’s Web of Trust (WoT) did not achieve mass adoption, with each reason tied to documented critiques and evolution paths.
It required sustained human effort (and humans didn’t do it)
The Web of Trust depends on people manually verifying and signing each other’s keys. In practice:
Most users never verified fingerprints Very few participated in key‑signing Trust graphs stayed sparse
This low participation was widely observed and documented as the primary failure mode: few keys accumulated meaningful trust paths, making the system fragile and ineffective for most users. [undercodetesting.com] Zimmermann himself acknowledged that the system relied on user judgment and supervision, which proved unrealistic outside expert communities. [mit.edu]
It was cognitively and UX‑heavy
Using the Web of Trust required users to understand:
Public vs private keys Trust vs validity Partial vs full trust Trust path depth Revocation, expiration, re‑signing
Even technically competent users found this confusing, and non‑technical users simply could not adopt it reliably. This usability barrier is repeatedly cited as a core reason for failure. [reddit.com], [ssh.com] As a result, encryption tools that automated trust decisions replaced WoT in practice. [undercodetesting.com]
No strong network effect emerged
The Web of Trust relies on emergence — trust becoming valuable only once many people participate. But adoption stalled before that tipping point:
If your contacts didn’t use PGP, WoT had no value If WoT had no value, people didn’t use it
This classic “cold start” problem meant the Web of Trust never crossed into mainstream usefulness. [reddit.com]
Key servers became a weak link
Although the trust model was decentralized, key distribution wasn’t:
Public key servers accumulated massive numbers of stale, spoofed, or malicious keys Revocation and update mechanisms were weak Poisoning attacks became feasible
By the mid‑2010s, key server infrastructure was widely regarded as “broken,” undermining confidence in the Web of Trust ecosystem. [lupinepublishers.com], [link.springer.com]
It did not scale cleanly beyond small communities
The Web of Trust did work in:
Cryptography circles Open‑source communities Activist and journalist networks
But scaling it to enterprises, governments, or the general public proved impractical due to:
Lack of centralized policy enforcement Difficulty automating trust decisions Fragility under key churn and algorithm deprecation
Modern analyses explicitly recommend WoT only for small, expert communities. [axelspire.com]
Simpler trust models won in practice
Over time, the ecosystem shifted toward:
Hierarchical PKI (browsers, TLS) Trust On First Use (TOFU) (SSH, Signal) Platform‑managed identity (messaging apps)
These models traded philosophical purity for:
Automation Predictability Usability
This shift is well‑documented as a pragmatic response to WoT’s operational complexity. [undercodetesting.com]
Zimmermann’s design was ahead of its time
Crucially, many modern systems now revisit WoT ideas — but with:
Automation Better UX Verifiable credentials Agent‑mediated trust
W3C and decentralized identity communities explicitly study WoT’s failure to avoid repeating it. [lists.w3.org] In other words: the idea survived; the original implementation didn’t.
Not an Enterprise Solution
The Web of Trust did not solve enterprise Identity and Access problems. This problem was solved by Kerberos, SAML and OIDC. The enterprise was willing to pay money for these solutions that gave them the control that they needed.
Verdict
The Web of Trust failed not because decentralized trust is impossible, but because PGP’s implementation depended on manual human behavior that does not scale, lacked usable tooling, never achieved network effects, and was undermined by weak key distribution infrastructure. It succeeded socially in small expert networks, but failed ergonomically and operationally for the general Internet. [undercodetesting.com], [axelspire.com]
Solutions
Social Networks
Online social networks (OSNs) are becoming a popular method of meeting people and keeping in touch with friends. OSNs resort to trust evaluation models and algorithms, as to improve service qualities and enhance user experiences. Understanding Graph-based Trust Evaluation in Online Social Networks: Methodologies and Challenges[1]
References
- ↑ Wenjun Jiang, Guojun Wang, Md Zakirul Alam Bhuiyan, Jie Wu, Understanding Graph-based Trust Evaluation in Online Social Networks: Methodologies and Challenges ACM Computing Surveys, Vol. V, No. N, Article A 2016-02 ACM https://cis.temple.edu/~wu/research/publications/Publication_files/20160219-trustsurvey-acm.pdf