Skip to content

Commit 008842a

Browse files
heeckhauheeckhau
authored
Privacy and Scaling Explorations -> Privacy Stewards of Ethereum (#30)
1 parent 5ea1291 commit 008842a

File tree

7 files changed

+34
-34
lines changed

7 files changed

+34
-34
lines changed

‎README.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@ All diagrams are created using draw.io. The diagram source files are stored in t
3030
* Front matter: https://docusaurus.io/docs/markdown-features#front-matter
3131

3232
Other Docusaurus websites at PSE:
33-
* MACI: https://github.com/privacy-scaling-explorations/maci/tree/dev/apps/website
34-
* MPC: https://github.com/privacy-scaling-explorations/mpc-framework-website
33+
* MACI: https://github.com/privacy-ethereum/maci/tree/main/apps/website
34+
* MPC: https://github.com/privacy-ethereum/mpc-framework-website
3535

3636
> **Disclaimer**: While we appreciate all contributions, we do not prioritize minor grammatical fixes (e.g., correcting typos or rewording sentences) unless they significantly improve clarity in technical documentation. These contributions can be a distraction for the team. If you notice a grammatical error, please let us know on our Discord.

‎docs/glossary.md‎

Lines changed: 22 additions & 22 deletions
Original file line numberDiff line numberDiff line change
@@ -1,24 +1,24 @@
11
# Glossary
22

3-
| Term | Explanation |
4-
| ----- | ----------------------------------------------- |
5-
| 2PC | Secure Two-party computation |
6-
| A2M | Addition-to-Multiplication |
7-
| AES | Advanced Encryption Standard |
8-
| DEAP | Dual Execution with Asymmetric Privacy |
9-
| ECB | Electronic codebook (encryption mode) |
10-
| ECDH | Elliptic-Curve Diffie-Hellman |
11-
| GC | Garbled Circuit |
12-
| GCM | Galois/Counter Mode |
13-
| GHASH | GCM hash |
14-
| HMAC | Hash-based Message Authentication Code |
15-
| M2a | Multiplication-to-Addition |
16-
| MAC | Message Authentication Code |
17-
| MPC | Secure Multi-party computation |
18-
| OT | oblivious transfer |
19-
| PMS | Pre master secret (TLS) |
20-
| PRF | Pseudo Random Function |
21-
| PRG | pseudorandom generator |
22-
| PSE | Privacy and Scaling Exploration |
23-
| RSA | Rivest–Shamir–Adleman (public-key cryptosystem) |
24-
| TLS | transport layer security |
3+
| Term | Explanation |
4+
| ----- | -------------------------------------------------------------------------- |
5+
| 2PC | Secure Two-party computation |
6+
| A2M | Addition-to-Multiplication |
7+
| AES | Advanced Encryption Standard |
8+
| DEAP | Dual Execution with Asymmetric Privacy |
9+
| ECB | Electronic codebook (encryption mode) |
10+
| ECDH | Elliptic-Curve Diffie-Hellman |
11+
| GC | Garbled Circuit |
12+
| GCM | Galois/Counter Mode |
13+
| GHASH | GCM hash |
14+
| HMAC | Hash-based Message Authentication Code |
15+
| M2a | Multiplication-to-Addition |
16+
| MAC | Message Authentication Code |
17+
| MPC | Secure Multi-party computation |
18+
| OT | oblivious transfer |
19+
| PMS | Pre master secret (TLS) |
20+
| PRF | Pseudo Random Function |
21+
| PRG | pseudorandom generator |
22+
| PSE | Privacy Stewards of Ethereum (formerly "Privacy and Scaling Explorations") |
23+
| RSA | Rivest–Shamir–Adleman (public-key cryptosystem) |
24+
| TLS | transport layer security |

‎docs/intro.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -78,7 +78,7 @@ TLSNotary currently supports TLS 1.2. Support for TLS 1.3 is on the roadmap.
7878

7979
## Who is behind TLSNotary?
8080

81-
TLSNotary is developed by the [Privacy and Scaling Exploration (PSE)](https://pse.dev) research lab of the Ethereum Foundation. The PSE team is committed to conceptualizing and testing use cases for cryptographic primitives.
81+
TLSNotary is developed by the [Privacy Stewards of Ethereum (PSE)](https://pse.dev) research and development lab of the Ethereum Foundation.
8282

8383
TLSNotary is not a new project; in fact, it has been around for [more than a decade](https://bitcointalk.org/index.php?topic=173220.0).
8484

‎docs/notary_server.md‎

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -9,11 +9,11 @@ Refer to the server's [README.md](https://github.com/tlsnotary/tlsn/tree/main/cr
99

1010
1. The following files are needed before running a notary server.
1111

12-
| File | Purpose | File Type | Compulsory | Sample Command |
13-
| ---------------------------- | ------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------ | ---------------------------- | --------------------------------------------------------------------------------------------------------------------- |
14-
| TLS private key | The private key used for the notary server's TLS certificate to establish TLS connections with provers | TLS private key in PEM format | Yes unless TLS is turned off | \<Generated when creating CSR for your Certificate Authority, e.g. using [Certbot](https://certbot.eff.org/)> |
15-
| TLS certificate | The notary server's TLS certificate to establish TLS connections with provers | TLS certificate in PEM format | Yes unless TLS is turned off | \<Obtained from your Certificate Authority, e.g. [Let's Encrypt](https://letsencrypt.org/)> |
16-
| Notary signing key | The private key used by the notary server to sign the attestation | A K256 or P256 elliptic curve private key in PKCS#8 PEM format | Yes | `openssl genpkey -algorithm EC -out eckey.pem -pkeyopt ec_paramgen_curve:secp256k1 -pkeyopt ec_param_enc:named_curve` |
12+
| File | Purpose | File Type | Compulsory | Sample Command |
13+
| ------------------ | ------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------- | ---------------------------- | --------------------------------------------------------------------------------------------------------------------- |
14+
| TLS private key | The private key used for the notary server's TLS certificate to establish TLS connections with provers | TLS private key in PEM format | Yes unless TLS is turned off | \<Generated when creating CSR for your Certificate Authority, e.g. using [Certbot](https://certbot.eff.org/)> |
15+
| TLS certificate | The notary server's TLS certificate to establish TLS connections with provers | TLS certificate in PEM format | Yes unless TLS is turned off | \<Obtained from your Certificate Authority, e.g. [Let's Encrypt](https://letsencrypt.org/)> |
16+
| Notary signing key | The private key used by the notary server to sign the attestation | A K256 or P256 elliptic curve private key in PKCS#8 PEM format | Yes | `openssl genpkey -algorithm EC -out eckey.pem -pkeyopt ec_paramgen_curve:secp256k1 -pkeyopt ec_param_enc:named_curve` |
1717
2. Expose the notary server port (specified in the config) on your server networking setting.
1818
3. Optionally one can turn on [authorization](https://github.com/tlsnotary/tlsn/tree/main/crates/notary/server#authorization), or turn off [TLS](https://github.com/tlsnotary/tlsn/tree/main/crates/notary/server#tls) if TLS is handled by an external setup, e.g. reverse proxy, cloud setup.
1919

@@ -68,7 +68,7 @@ To check the status of the notary server, visit the `healthcheck` endpoint at:
6868

6969
### WebSocket Proxy Server
7070

71-
Because web browsers don't have the ability to make TCP connections directly, TLSNotary requires a WebSocket proxy to set up TCP connections when it is used in a browser. To facilitate the exploration of TLSNotary and to run the examples easily, the TLSNotary team hosts a public WebSocket proxy server. Note that this proxy only supports a predefined set of domains. You can view the full list of supported domains in the [websockify configuration file](https://github.com/privacy-scaling-explorations/tlsn-infra/blob/main/docker/websockify/websockify_config).
71+
Because web browsers don't have the ability to make TCP connections directly, TLSNotary requires a WebSocket proxy to set up TCP connections when it is used in a browser. To facilitate the exploration of TLSNotary and to run the examples easily, the TLSNotary team hosts a public WebSocket proxy server. Note that this proxy only supports a predefined set of domains. You can view the full list of supported domains in the [websockify configuration file](https://github.com/privacy-ethereum/tlsn-infra/blob/main/docker/websockify/websockify_config).
7272

7373
You can utilize this WebSocket proxy with the following syntax:
7474

‎docs/quick_start/browser_extension.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -39,7 +39,7 @@ To use the TLSnotary hosted proxy:
3939
3. Enter `wss://notary.pse.dev/proxy` as **proxy API**
4040
4. Click **Save**
4141

42-
> ⚠️ **Note:** The TLSNotary hosted proxy only supports a predefined set of domains. You can view the full list of supported domains in the [websockify configuration file](https://github.com/privacy-scaling-explorations/tlsn-infra/blob/main/docker/websockify/websockify_config).
42+
> ⚠️ **Note:** The TLSNotary hosted proxy only supports a predefined set of domains. You can view the full list of supported domains in the [websockify configuration file](https://github.com/privacy-ethereum/tlsn-infra/blob/main/docker/websockify/websockify_config).
4343
4444
To run your own websocket proxy **locally**, run:
4545
1. Install [wstcp](https://github.com/sile/wstcp):

‎docusaurus.config.ts‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -185,7 +185,7 @@ const config: Config = {
185185
],
186186
},
187187
],
188-
copyright: `TLSNotary is a project of Privacy and Scaling Explorations, an Ethereum Foundation supported team.`,
188+
copyright: `TLSNotary is a project of the Ethereum Foundation.`,
189189
},
190190
prism: {
191191
theme: prismThemes.github,

‎src/pages/about.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: About
33
---
44
## Who we are
55

6-
TLSNotary is an open-source protocol developed by the **Privacy and Scaling Exploration (PSE)** research lab of the Ethereum Foundation.
6+
TLSNotary is an open-source protocol developed by the **Privacy Stewards of Ethereum (PSE)** research and development lab of the Ethereum Foundation.
77

88
TLSNotary is not a new project; in fact, it has been around for **more than a decade**. In 2022, TLSNotary was rebuilt from the ground up in **Rust** incorporating state-of-the-art cryptographic protocols. This renewed version of the TLSNotary protocol offers enhanced security, privacy, and performance.
99

0 commit comments

Comments
 (0)