Clear Human Web: Where a Person Vouches for Every Client

summary

The gist

The paper proposes the Clear Human Web, a part of the public web where sites open only to clients a person vouches for.

In short

The Clear Human Web proposes a system where sites only open to clients vouched for by a person's wallet. This aims to verify if a person stands behind a client without revealing other personal details. The construction uses anonymous proofs that allow users to visit sites while maintaining privacy, addressing the lack of accountability on the web.

Key concepts

Clear Human Web
A part of the public web where access is restricted based on a person vouching for it. This system reveals only whether a person stands behind a client, offering accountability without exposing other identifying information.
Anonymous Proofs
Digital tokens issued by an issuer that a person holds in their wallet. A site checks these proofs to ensure they come from a trusted source but does not learn the user's identity or track multiple visits from the same person.
P1 Admission by persons
A property requiring that sites can be admitted into the system by individuals. The construction aims to satisfy this, ensuring that people can use the web without needing a new root of trust for every site they visit.

Terminology used across episodes

This episode discusses

The paper

Clear Human Web: Where a Person Vouches for Every Client · Read on arXiv

Lorenzo Porcelli

Transcript

Introduction to the show: ident: Security Radio. Generated commentary on the latest security and cryptography papers.

Nadia: We're looking at the paper: "Clear Human Web: Where a Person Vouches for Every Client".

Elias: Here's the gist of the paper. The paper proposes the Clear Human Web, a part of the public web where sites open only to clients a person vouches for.

Nadia: This construction aims to reveal whether a person stands behind the client, which reveals nothing else.

Elias: The Problem Addressed The problem has three faces, one for each party on the web.

Nadia: Whoever publishes has no fence.

Paper summary: Nadia: We're now getting into how this paper actually sets up that web. They start by pointing out that on the existing web, publishers have no fence, measurers have no count, and readers have no proof of identity <ref:2611.06286#pg2>.

Elias: Exactly. The fundamental issue is a web that cannot see the person who is making the request. They call for one cure: a check that a person stands behind the client, which reveals nothing else about them <ref:2611.06286#pg3>.

Priya: So, what's the proposed mechanism again, focusing only on what's in the summary? I want to make sure we get the high-level idea right before we get into how it runs.

Nadia: The construction involves a person’s wallet presenting their personal identification data to an issuer. This issuer is the only party that acts as a relying party and hands back a bounded stock of anonymous proofs of personhood. Then, the person's browser spends one proof at every site that runs the gate when those sites ask for it <ref:2611.06286#pg1>.

Elias: The site only checks that the proof came from an issuer it trusts and opens its door, but it doesn't learn who the person is, and it can't tell if two visits come from the same person <ref:2611.06286#pg1>. Nothing changes in the protocols of the web or in what publishers are obligated to do.

Priya: That sounds like a really clean separation of concerns. It suggests that we don't need to overhaul every single protocol just to get this one specific verification layer working properly <ref:2611.06286#pg2>.

Nadia: Right, and the paper lays out five properties they have to satisfy: admission by persons, no identity for the person, unlinkability, bounded multiplicity for visits, and delegation tolerance <ref:2611.06286#pg3>. They show that an optimum solution exists where k equals one token per site and no tokens at all <ref:2611.06286#pg3>.

Elias: And they prove this optimum works against seven different adversaries, which shows the construction is quite robust under various attack models <ref:2611.06286#pg3>. This gives us a solid benchmark for what's achievable in this space.

Priya: So, before we move on to the conclusion and title implications, what’s the main takeaway from all this setup? What is the practical meaning of "Clear Human Web"?

Nadia: The main point is that one bit of information—that a person stands behind a client—is enough to let a part of the public web emerge wherever sites choose to join it <ref:2611.06286#pg1>. It’s about making that verification happen without needing a new root of trust from scratch.

Elias: It’s essentially using the EU wallet to supply that bit, which is a blind RSA signature over a random value that carries no attribute <ref:2611.06286#pg3>.

Conclusion: Nadia: So we’re wrapping up our discussion on "Clear Human Web: Where a Person Vouches for Every Client." The authors are Lorenzo Porcelli and his independent research group <ref:2611.06286#pg1>.

Elias: And the title itself suggests that the core value isn't just verification, but the ability for sites to join this system based on a single vouching person <ref:2611.06286#pg3>. It’s about defining a specific structure where trust is delegated by an individual, not by some centralized authority.

Priya: From my perspective as someone focused on privacy, what does this mean for the average user who just wants to browse the web without their identity being tracked everywhere?

Nadia: It means that instead of every site trying to figure out if you're a human or an automated script, they can rely on this specific mechanism where you only need to prove you have a valid token from an issuer <ref:2611.06286#pg3>. The system only makes the enforcement happen per person rather than per address <ref:2611.06286#pg3>.

Elias: That distinction is important because the optimum construction they found removes that linking problem when you use Tor for example, where the address itself says nothing about who is using it <ref:2611.06286#pg3>. The gap between a site that can't report and an issuer that can't see is what this per-site pseudonym closes <ref:2611.06286#pg3>.

Priya: And the limitations they state are pretty clear too, right? What’s the practical stop for this approach?

Nadia: They point out a few limits. First, you still need someone with a PID in their wallet to participate <ref:2611.06286#pg2>. Second, the construction today inherits links from the web even without Tor <ref:2611.06286#pg3>. And finally, they mention that two extensions follow from the same proof, like writing or voting, which needs a visitor that a site can recognize and refuse without naming them <ref:2611.06286#pg3>.

Elias: So the next step toward that optimum involves adding A zero tokens in the browser to handle those extensions <ref:2611.06286#pg3>. It’s an iterative process, not a single fix for everything.

Priya: It sounds like a very focused piece of research that defines a specific, verifiable layer on top of the existing infrastructure rather than trying to replace everything at once.

Nadia: That’s right. We saw how this paper defines the Clear Human Web through five properties and seven adversaries and showed which ones the construction they proposed satisfies against each adversary <ref:2611.06286#pg3>. It shows exactly where this concept fits in terms of what it can do for the web as a whole, without overpromising on what it can achieve immediately <ref:2611.06286#pg3>.

More episodes

← Home