AtHeartEngineer/website
1
0
Fork 0
mirror of https://github.com/tlsnotary/website.git synced 2026-01-09 14:58:09 -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/Protocol/mpc-tls/encryption.md
View File

@@ -11,7 +11,8 @@ This section explains how the `Prover` and `Verifier` use MPC to encrypt data se
To encrypt the plaintext, both parties input their TLS key shares as private inputs to the [MPC](../../mpc/deap.md) protocol, along with some other public data. Additionally, the `Prover` inputs her plaintext as a private input.
![Encryption](../../diagrams/mpc-encryption.svg)
![Encryption](../../../diagrams/light/mpc-encryption.svg#gh-light-mode-only)
![Encryption](../../../diagrams/dark/mpc-encryption.svg#gh-dark-mode-only)
Both parties see the resulting ciphertext and execute the [2PC MAC](../../mpc/mac.md) protocol to compute the MAC for the ciphertext.
@@ -23,7 +24,8 @@ Once the `Prover` receives the ciphertext and its associated MAC from the server
Next, the parties decrypt the ciphertext by providing their key shares as private inputs to the [MPC](../../mpc/deap.md) protocol, along with the ciphertext and some other public data.
![Decryption](../../diagrams/mpc-decryption.svg)
![Decryption](../../../diagrams/light/mpc-decryption.svg#gh-light-mode-only)
![Decryption](../../../diagrams/dark/mpc-decryption.svg#gh-dark-mode-only)
The resulting plaintext is revealed ONLY to the `Prover`.

3
docs/Protocol/mpc-tls/handshake.md
View File

@@ -4,7 +4,8 @@ sidebar_position: 1
# Handshake
![](../../diagrams/key_exchange.svg)
![Encryption](../../../diagrams/light/key_exchange.svg#gh-light-mode-only)
![Encryption](../../../diagrams/dark/key_exchange.svg#gh-dark-mode-only)
A TLS handshake is the first step in establishing a TLS connection between a `Prover` and a `Server`. In TLSNotary the `Prover` is the one who starts the TLS handshake and physically communicates with the `Server`, but all cryptographic TLS operations are performed together with the `Verifier` using MPC.