deploy: 06d771f388

faq.html

@@ -187,6 +187,7 @@
 <li><a href="#faq5">Is the Notary an essential part of the TLSNotary protocol?</a></li>
 <li><a href="#faq6">Which TLS versions are supported?</a></li>
 <li><a href="#faq7">What is the overhead of using the TLSNotary protocol?</a></li>
+<li><a href="#faq8">Does TLSNotary use a proxy?</a></li>
 </ul>
 <h3 id="faq1"><a class="header" href="#faq1">Doesn't TLS allow a third party to verify data authenticity?</a></h3>
 <p>No, it does not. TLS is designed to guarantee the authenticity of data <strong>only to the participants</strong> of the TLS connection. TLS does not have a mechanism to enable the server to "sign" the data.</p>
@@ -211,6 +212,8 @@ There are no immediate plans to support TLS 1.3. Once the web starts to transiti
 <p>~25MB (a fixed cost per one TLSNotary session) + ~10 MB per every 1KB of outgoing data + ~40KB per every 1 KB of incoming data.</p>
 <p>In a concrete scenario of sending a 1KB HTTP request followed by a 100KB response, the <code>Prover's</code> overhead will be:</p>
 <p>25 + 10 + 4 = ~39 MB of <strong>upload</strong> data.</p>
+<h3 id="faq8"><a class="header" href="#faq8">Does TLSNotary use a proxy?</a></h3>
+<p>A proxy is required only for the browser extension because browsers do not allow extensions to open TCP connections. Instead, our extension opens a websocket connection to a proxy (local or remote) which opens a TCP connection with the server. Our custom TLS client is then attached to this connection and the proxy only sees encrypted data.</p>
 
                     </main>
 

print.html

@@ -257,6 +257,7 @@ With TLSNotary, Alice can selectively prove the authenticity of arbitrary portio
 <li><a href="faq.html#faq5">Is the Notary an essential part of the TLSNotary protocol?</a></li>
 <li><a href="faq.html#faq6">Which TLS versions are supported?</a></li>
 <li><a href="faq.html#faq7">What is the overhead of using the TLSNotary protocol?</a></li>
+<li><a href="faq.html#faq8">Does TLSNotary use a proxy?</a></li>
 </ul>
 <h3 id="faq1"><a class="header" href="#faq1">Doesn't TLS allow a third party to verify data authenticity?</a></h3>
 <p>No, it does not. TLS is designed to guarantee the authenticity of data <strong>only to the participants</strong> of the TLS connection. TLS does not have a mechanism to enable the server to "sign" the data.</p>
@@ -281,6 +282,8 @@ There are no immediate plans to support TLS 1.3. Once the web starts to transiti
 <p>~25MB (a fixed cost per one TLSNotary session) + ~10 MB per every 1KB of outgoing data + ~40KB per every 1 KB of incoming data.</p>
 <p>In a concrete scenario of sending a 1KB HTTP request followed by a 100KB response, the <code>Prover's</code> overhead will be:</p>
 <p>25 + 10 + 4 = ~39 MB of <strong>upload</strong> data.</p>
+<h3 id="faq8"><a class="header" href="#faq8">Does TLSNotary use a proxy?</a></h3>
+<p>A proxy is required only for the browser extension because browsers do not allow extensions to open TCP connections. Instead, our extension opens a websocket connection to a proxy (local or remote) which opens a TCP connection with the server. Our custom TLS client is then attached to this connection and the proxy only sees encrypted data.</p>
 <div style="break-before: page; page-break-before: always;"></div><link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/katex@0.16.4/dist/katex.min.css">
 <h1 id="quick-start"><a class="header" href="#quick-start">Quick Start</a></h1>
 <p>This quick start will help you get started with TLSNotary, both in native <a href="quick_start/rust.html">Rust</a> and in the <a href="quick_start/browser_extension.html">browser</a>.</p>