AtHeartEngineer/docs-mdbook
1
0
Fork 0
mirror of https://github.com/AtHeartEngineer/docs-mdbook.git synced 2026-01-09 17:17:54 -05:00
Code Issues Packages Projects Releases Wiki Activity

Use html comments for comments

Browse Source
This commit is contained in:
Hendrik Eeckhaut
2023-08-30 19:06:56 +02:00
parent 7bf9e4397e
commit c5a68d830f
2 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
src/protocol/verification.md
View File

@@ -14,7 +14,7 @@ A `Verifier`` receives the following from the `User`:
and performs the following steps to verify the commitments: and performs the following steps to verify the commitments:
// you can see these steps in tlsn/tlsn-core/tests/api.rs <!-- // you can see these steps in tlsn/tlsn-core/tests/api.rs -->
- verify that `Session Header` was signed by the Notary - verify that `Session Header` was signed by the Notary
- verify handshake_data against handshake_commitment - verify handshake_data against handshake_commitment
@@ -28,4 +28,4 @@ and performs the following steps to verify the commitments:
To summarize: the `Verifier` will only learn those portions of the TLS session transcript which the `User` chose to reveal. The portions which were not revealed (`User`'s private data) will appear to the `Verifier` as redacted. Here is an example of what the `Verifier` output may look like: To summarize: the `Verifier` will only learn those portions of the TLS session transcript which the `User` chose to reveal. The portions which were not revealed (`User`'s private data) will appear to the `Verifier` as redacted. Here is an example of what the `Verifier` output may look like:
// paste here a picture of an HTTP request with redacted fields <!-- // paste here a picture of an HTTP request with redacted fields -->

2
src/spec/notarized_session.md
View File

@@ -45,7 +45,7 @@ The total amount of application data bytes that the `User` sent to and received
## Session Data ## Session Data
// (can be seen in tlsn-core/src/session/data.rs) <!-- // (can be seen in tlsn-core/src/session/data.rs) -->
- `handshake_data_decommitment` contains `HandshakeData` which the `User` committed to (with salt) - `handshake_data_decommitment` contains `HandshakeData` which the `User` committed to (with salt)
`HandshakeData` contains various TLS-specific details: `HandshakeData` contains various TLS-specific details: