torproject/community
1
0
Fork 0
mirror of https://github.com/torproject/community.git synced 2025-02-22 19:12:29 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

fixes reported by translator Kate_, thanks!

Browse Source
This commit is contained in:
emmapeel 2022-06-29 16:52:47 +00:00
parent 5d965128ef
commit 9e1028c6ed
5 changed files with 6 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
content/onion-services/advanced/https/contents.lr
View File

@ -32,7 +32,7 @@ That said, there are some specific cases where you would need or want to have an
We compiled some topics and arguments, so you can analyze what's the best for your onion site:
1. As anyone can generate an onion address and its 56 random alphanumeric characters, some enterprise onions believe that associating their onion site to an HTTPS certificate might be a solution to announce their service to users.
1. As anyone can generate an onion address and its 56 random alphanumeric characters, some enterprise administrators believe that associating their onion site to an HTTPS certificate might be a solution to announce their service to users.
Users would need to click and do a manual verification, and that would show that they're visiting the onion site that they're expecting.
Alternatively, websites can provide other ways to verify their onion address using HTTPS, for example, linking their onion site address from an HTTPS-authenticated page, or using [Onion-Location](../onion-location/).
@ -76,3 +76,4 @@ In the nearby future, we hope that [Let's Encrypt](https://letsencrypt.org/) CA
* [DigiCert: Get TLS certificate with Extended Validation (EV) for your onion site (2015)](https://www.digicert.com/blog/onion-officially-recognized-special-use-domain/)
* [HARICA: Get a TLS certificate with Domain Validation (DV) for your onion site (2021)](https://blog.torproject.org/tls-certificate-for-onion-site)
* [The ".onion" Special-Use Domain Name - IETF RFC 7686](https://tools.ietf.org/html/rfc7686)
* [EOTK - Enterprise Onion Toolkit](https://github.com/alecmuffett/eotk)

2
content/relay/setup/guard/archlinux/contents.lr
View File

@ -21,7 +21,7 @@ To install the `tor` package on Arch Linux, please run:
### 3. Configure `/etc/tor/torrc`
This is a very simple version of the `torrc` configuration file in order to run a Bridge on the Tor network:
Put the configuration file `/etc/tor/torrc` in place
```
Nickname myNiceRelay # Change "myNiceRelay" to something you like

2
content/relay/setup/guard/voidlinux/contents.lr
View File

@ -21,7 +21,7 @@ To install the `tor` package on Void Linux, please run:
### 3. Configure `/etc/tor/torrc`
This is a very simple version of the `torrc` configuration file in order to run a Bridge on the Tor network:
Put the configuration file `/etc/tor/torrc` in place
```
Nickname myNiceRelay # Change "myNiceRelay" to something you like

2
content/relay/setup/snowflake/browser/contents.lr
View File

@ -6,7 +6,7 @@ title: Browser Snowflake proxy
---
body:
Running a Snowflake proxy as a browser add on is a great low-effort way to donate bandwidth if you don't have acces to an always-on highly connected server.
Running a Snowflake proxy as a browser add on is a great low-effort way to donate bandwidth if you don't have access to an always-on highly connected server.
There are very few requirements to running a browser-based proxy:
1. Use Firefox or Chromium/Chrome as your browser
2. Have WebRTC enabled

2
content/relay/setup/snowflake/standalone/contents.lr
View File

@ -56,7 +56,7 @@ You will need Go 1.13+ to run the Snowflake proxy.
4. Run the Snowflake proxy.
For our fallback proxy-go instances on snowflake-broker, [we manage proxy-go instances using runit](https://gitlab.torproject.org/tpo/anti-censorship/team/-/wikis/Survival-Guides/Snowflake-Bridge-Survival-Guide#standalone-proxy-go-instances).
However, a simpler nohup command will also allow you to run an instance in the background.
However, a simpler `nohup` command will also allow you to run an instance in the background.
```
nohup ./proxy &
```