tlsnotary/website
1
0
Fork 0
mirror of https://github.com/tlsnotary/website.git synced 2026-01-08 21:48:05 -05:00
Code Issues Packages Projects Releases Wiki Activity

Improved diagrams (dark/light mode support)

Browse Source
This commit is contained in:
Hendrik Eeckhaut
2025-05-14 16:29:01 +02:00
parent feb2ff2756
commit 961185c4d4
93 changed files with 3918 additions and 79 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
docs/intro.md
View File

@@ -19,7 +19,8 @@ The TLSNotary protocol consists of 3 steps:
2. The `Prover` **selectively discloses** the data to the `Verifier`.
3. The `Verifier` **verifies** the data.
![](./diagrams/overview_prover_verifier.svg)
![](../diagrams/light/overview_prover_verifier.svg#gh-light-mode-only)
![](../diagrams/dark/overview_prover_verifier.svg#gh-dark-mode-only)
### ① Multi-party TLS Request
@@ -41,7 +42,8 @@ The `Verifier` now validates the proof received from the `Prover`. The data orig
Since the validation of the TLS traffic neither reveals anything about the plaintext of the TLS session nor about the `Server`, it is possible to outsource the MPC-TLS verification ① to a general-purpose TLS verifier, which we term a `Notary`. This `Notary` can sign (aka *notarize*) ② the data, making it portable. The `Prover` can then take this signed data and selectively disclose ③ sections to an application-specific `Verifier`, who then verifies the data ④.
![](./diagrams/overview_notary.svg)
![](../diagrams/light/overview_notary.svg#gh-light-mode-only)
![](../diagrams/dark/overview_notary.svg#gh-dark-mode-only)
In this setup, the `Notary` cryptographically signs commitments to the data and the server's identity. The `Prover` can store this signed data, redact it, and share it with any `Verifier` as they see fit, making the signed data both reusable and portable.