diff --git a/src/HomePage.tsx b/src/HomePage.tsx
index a63e7f7..16a3642 100644
--- a/src/HomePage.tsx
+++ b/src/HomePage.tsx
@@ -5,6 +5,7 @@ import Usecases from './components/Usecases';
import About from './components/About';
import Footer from './components/Footer';
import How from './components/How';
+import Pagesigner from './components/Pagesigner';
function HomePage() {
return (
@@ -15,6 +16,7 @@ function HomePage() {
Export data from any web application and prove facts about it without compromising on privacy.
- ); diff --git a/src/components/How.css b/src/components/How.css index 8f543b3..7bc65c4 100644 --- a/src/components/How.css +++ b/src/components/How.css @@ -2,20 +2,50 @@ display: flex; flex-direction: row; align-items: center; - padding-block: 12px; - padding: 100px; + padding-top: 50px; + padding-bottom: 50px; } #How .body { - display: grid; - grid-template-columns: repeat(2, 1fr); + display: flex; + flex-direction: row; gap: 2.5rem; -} - -#How .diagram-container { - padding: 10px; + align-items: center; } #How .diagram { - display: flex; + padding: 30px; +} + +#How .diagram-container { + display: flex; + border: 5px solid var(--brown); + border-radius: 30px; + justify-content: center; +} + +#How .text-container { + text-align: left; +} + +@media only screen and (max-width: 1440px) { + #How { + display: flex; + flex-direction: row; + align-items: center; + justify-content: center; + padding-top: 50px; + padding-bottom: 50px; + } + + #How .body { + flex-direction: column; + position: static; + max-width: 67%; + } + + #How .diagram { + max-width: 80%; + padding: 30px; + } } diff --git a/src/components/How.tsx b/src/components/How.tsx index 56299ee..f8257b8 100644 --- a/src/components/How.tsx +++ b/src/components/How.tsx @@ -8,7 +8,7 @@ export default function How() {
@@ -18,7 +18,8 @@ export default function How() {
At the core of the TLSNotary protocol is dividing TLS session keys between two parties (Client and Notary) and then using secure two-party computation (2PC) to encrypt and authenticate requests from the Client to a TLS-enabled webserver.
- During the protocol neither the Client nor Notary are in posession of the full TLS session keys, they only know their shares of those keys. This preserves the security assumptions of TLS while at the same time allowing the Client to prove to the Notary the authenticity of the transcript.
+ During the protocol neither the Client nor Notary are in posession of the full TLS session keys, they only know their shares of those keys.
+ This preserves the security assumptions of TLS while at the same time allows the Client to prove to the Notary the authenticity of the transcript.
This is all achieved with full privacy. The Notary is never aware of which webserver is being queried, nor do they ever see the unencrypted communications.
diff --git a/src/components/Navbar.tsx b/src/components/Navbar.tsx
index ddd4ec9..76e15be 100644
--- a/src/components/Navbar.tsx
+++ b/src/components/Navbar.tsx
@@ -20,7 +20,7 @@ function Navbar() {
+ Looking for our legacy implementation? +
+ + + + +