[tor-commits] [tor/main] Sync ReleaseNotes and ChangeLog from release-{0.3.5, 0.4.5, 0.4.6} to main.
commit ecb9cee26659996bb64c563e0e13f820e905804d
Author: Alexander Færøy
Date: Mon Oct 25 23:41:05 2021 +
Sync ReleaseNotes and ChangeLog from release-{0.3.5, 0.4.5, 0.4.6} to main.
---
ChangeLog| 177 +++
ReleaseNotes | 177 +++
2 files changed, 354 insertions(+)
diff --git a/ChangeLog b/ChangeLog
index 4239f86a31..a061775812 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -244,6 +244,65 @@ Changes in version 0.4.7.1-alpha - 2021-09-17
Fixes bug 40467; bugfix on 0.4.3.1-alpha. Patch by Neel Chauhan.
+Changes in version 0.4.6.8 - 2021-10-26
+ This version fixes several bugs from earlier versions of Tor. One
+ highlight is a fix on how we track DNS timeouts to report general
+ relay overload.
+
+ o Major bugfixes (relay, overload state):
+- Relays report the general overload state for DNS timeout errors
+ only if X% of all DNS queries over Y seconds are errors. Before
+ that, it only took 1 timeout to report the overload state which
+ was just too low of a threshold. The X and Y values are 1% and 10
+ minutes respectively but they are also controlled by consensus
+ parameters. Fixes bug 40491; bugfix on 0.4.6.1-alpha.
+
+ o Minor features (fallbackdir):
+- Regenerate fallback directories for October 2021. Closes
+ ticket 40493.
+
+ o Minor features (testing):
+- On a testing network, relays can now use the
+ TestingMinTimeToReportBandwidth option to change the smallest
+ amount of time over which they're willing to report their observed
+ maximum bandwidth. Previously, this was fixed at 1 day. For
+ safety, values under 2 hours are only supported on testing
+ networks. Part of a fix for ticket 40337.
+- Relays on testing networks no longer rate-limit how frequently
+ they are willing to report new bandwidth measurements. Part of a
+ fix for ticket 40337.
+- Relays on testing networks now report their observed bandwidths
+ immediately from startup. Previously, they waited until they had
+ been running for a full day. Closes ticket 40337.
+
+ o Minor bugfix (onion service):
+- Do not flag an HSDir as non-running in case the descriptor upload
+ or fetch fails. An onion service closes pending directory
+ connections before uploading a new descriptor which can thus lead
+ to wrongly flagging many relays and thus affecting circuit building
+ path selection. Fixes bug 40434; bugfix on 0.2.0.13-alpha.
+- Improve logging when a bad HS version is given. Fixes bug 40476;
+ bugfix on 0.4.6.1-alpha.
+
+ o Minor bugfix (CI, onion service):
+- Exclude onion service version 2 Stem tests in our CI. Fixes bug 40500;
+ bugfix on 0.3.2.1-alpha.
+
+ o Minor bugfixes (compatibility):
+- Fix compatibility with the most recent Libevent versions, which no
+ longer have an evdns_set_random_bytes() function. Because this
+ function has been a no-op since Libevent 2.0.4-alpha, it is safe
+ for us to just stop calling it. Fixes bug 40371; bugfix
+ on 0.2.1.7-alpha.
+
+ o Minor bugfixes (onion service, TROVE-2021-008):
+- Only log v2 access attempts once total, in order to not pollute
+ the logs with warnings and to avoid recording the times on disk
+ when v2 access was attempted. Note that the onion address was
+ _never_ logged. This counts as a Low-severity security issue.
+ Fixes bug 40474; bugfix on 0.4.5.8.
+
+
Changes in version 0.4.6.7 - 2021-08-16
This version fixes several bugs from earlier versions of Tor,
including one that could lead to a denial-of-service attack. Everyone
@@ -290,6 +349,87 @@ Changes in version 0.4.6.7 - 2021-08-16
schedules.) Fixes bug 40383; bugfix on 0.2.0.3-alpha.
+Changes in version 0.4.5.11 - 2021-10-26
+ The major change in this version is that v2 onion services are now
+ disabled at the client, service, and relay: any Tor nodes running this
+ version and onward will stop supporting v2 onion services. This is the
+ last step in the long deprecation process of v2 onion services.
+ Everyone running an earlier version, whether as a client, a relay, or
+ an onion service, should upgrade to Tor 0.3.5.17, 0.4.5.11,
+ or 0.4.6.8.
+
+ o Major feature (onion service v2):
+- See https://blog.torproject.org/v2-deprecation-timeline for
+ details on how to transition from v2 to v3.
+- The control port commands HSFETCH and HSPOST no longer allow
+ version 2, and it is no longer possible to create a v2 service
+ with ADD_ONION.
+- Tor no longer allows creating v2 services, or connecting as a
+ client to a v2 service. Relays will decline to be a v2 HSDir or
+ introduction point. This effectively disables onion service
+ version 2 Tor-wide. Closes ticket 40476.
+
+ o Minor features (bridge, backport from 0.4.6.8):
+- We
[tor-commits] [community/master] Better markdown formatting
commit 6d1053915ca2e55951bcd4c7faced2b0b085233c Author: gus Date: Mon Oct 25 18:57:13 2021 -0300 Better markdown formatting --- content/relay/setup/guard/centos-rhel/contents.lr | 20 ++-- content/relay/setup/guard/debian-ubuntu/contents.lr | 14 +++--- content/relay/setup/guard/dragonflybsd/contents.lr | 20 ++-- content/relay/setup/guard/fedora/contents.lr| 14 +++--- content/relay/setup/guard/freebsd/contents.lr | 19 ++- content/relay/setup/guard/netbsd/contents.lr| 16 +--- content/relay/setup/guard/openbsd/contents.lr | 19 ++- 7 files changed, 63 insertions(+), 59 deletions(-) diff --git a/content/relay/setup/guard/centos-rhel/contents.lr b/content/relay/setup/guard/centos-rhel/contents.lr index 0d8372b..fc5b7d8 100644 --- a/content/relay/setup/guard/centos-rhel/contents.lr +++ b/content/relay/setup/guard/centos-rhel/contents.lr @@ -6,19 +6,19 @@ title: CentOS/RHEL --- body: -# 1. Enable Automatic Software Updates +### 1. Enable Automatic Software Updates One of the most important things to keeps your relay secure is to install security updates timely and ideally automatically so you can not forget about it. Follow the instructions to enable [automatic software updates](updates) for your operating system. -# 2. Install `epel-release` +### 2. Install `epel-release` -To install `tor` on CentOS/RHEL, you need to enable the use of the [EPEL](https://fedoraproject.org/wiki/EPEL) Repository first. To do so, you must install the `epel-release` package: +To install `tor` package on CentOS/RHEL, you need to install the [EPEL](https://fedoraproject.org/wiki/EPEL) repository first: ``` # yum install epel-release ``` -Recent versions of CentOS/RHEL are using `dnf` instead of `yum`, so the command to install the package would be: +Recent versions of CentOS/RHEL are using `dnf` instead of `yum`: ``` # dnf install epel-release @@ -26,7 +26,7 @@ Recent versions of CentOS/RHEL are using `dnf` instead of `yum`, so the command If you are on a recent version that uses `dnf`, please keep using it for the following steps where `yum` is called on this setup guide. -# 3. Configure Tor Project's Repository +### 3. Configure Tor Project's Repository Configuring the Tor Project's Repository for CentOS/RHEL consists basically on setting up `/etc/yum.repos.d/Tor.repo` with the following content: @@ -42,7 +42,7 @@ cost=100 More information about it can be found [here](https://support.torproject.org/rpm/). -# 4. Install `tor` +### 4. Package installation Once you are set with EPEL and the Tor repositories, you are now able to install the package: @@ -52,9 +52,9 @@ Once you are set with EPEL and the Tor repositories, you are now able to install Please note that when you are installing the first package from the EPEL repository you will be asked about verifying the EPEL's GPG signing key. Please ensure the key matches with the one available on the [Fedora Project website](https://getfedora.org/keys/). This will also happens when installing packages from Tor's repository for the first time - again you must ensure the key matches. -# 5. Configure `/etc/tor/torrc` +### 5. Configuration file -This is a very simple version of the `torrc` configuration file in order to run a Middle/Guard relay on the Tor network: +Put the configuration file `/etc/tor/torrc` in place: ``` NicknamemyNiceRelay # Change "myNiceRelay" to something you like @@ -64,7 +64,7 @@ ExitRelay 0 SocksPort 0 ``` -# 6. Enable and Start `tor` +### 6. Enable and Start `tor` Recent versions os CentOS/RHEL which ship with systemd: @@ -79,7 +79,7 @@ Should you use an older release like CentOS/RHEL 6, that will be: # service tor start ``` -# 7. Final Notes +### 7. Final Notes If you are having trouble setting up your relay, have a look at our [help section](/relay/getting-help/). If your relay is now running, check out the [post-install](/relay/setup/post-install/) notes. diff --git a/content/relay/setup/guard/debian-ubuntu/contents.lr b/content/relay/setup/guard/debian-ubuntu/contents.lr index a93ba19..95f9eef 100644 --- a/content/relay/setup/guard/debian-ubuntu/contents.lr +++ b/content/relay/setup/guard/debian-ubuntu/contents.lr @@ -6,16 +6,16 @@ title: Debian/Ubuntu --- body: -# 1. Enable Automatic Software Updates +### 1. Enable Automatic Software Updates One of the most important things to keeps your relay secure is to install security updates timely and ideally automatically so you can not forget about it. Follow the instructions to enable [automatic software updates](updates) for your operating system. -# 2. Configure Tor Project's Repository +### 2. Configure Tor Project's Repository Configuring the Tor Project's package repository for Debian/Ubuntu is documented
[tor-commits] [community/master] rename: centosrhel -> centos-rhel, and debianubuntu -> debian-ubuntu. build OK
commit 1d4afa979cdd0def4df083ec94690bfe65bb8c88
Author: VinÃcius Zavam
Date: Mon Oct 25 09:17:38 2021 +
rename: centosrhel -> centos-rhel, and debianubuntu -> debian-ubuntu. build
OK
---
content/relay/setup/guard/{centosrhel => centos-rhel}/contents.lr | 0
content/relay/setup/guard/{centosrhel => centos-rhel}/updates/contents.lr | 0
content/relay/setup/guard/{debianubuntu => debian-ubuntu}/contents.lr | 0
.../relay/setup/guard/{debianubuntu => debian-ubuntu}/updates/contents.lr | 0
4 files changed, 0 insertions(+), 0 deletions(-)
diff --git a/content/relay/setup/guard/centosrhel/contents.lr
b/content/relay/setup/guard/centos-rhel/contents.lr
similarity index 100%
rename from content/relay/setup/guard/centosrhel/contents.lr
rename to content/relay/setup/guard/centos-rhel/contents.lr
diff --git a/content/relay/setup/guard/centosrhel/updates/contents.lr
b/content/relay/setup/guard/centos-rhel/updates/contents.lr
similarity index 100%
rename from content/relay/setup/guard/centosrhel/updates/contents.lr
rename to content/relay/setup/guard/centos-rhel/updates/contents.lr
diff --git a/content/relay/setup/guard/debianubuntu/contents.lr
b/content/relay/setup/guard/debian-ubuntu/contents.lr
similarity index 100%
rename from content/relay/setup/guard/debianubuntu/contents.lr
rename to content/relay/setup/guard/debian-ubuntu/contents.lr
diff --git a/content/relay/setup/guard/debianubuntu/updates/contents.lr
b/content/relay/setup/guard/debian-ubuntu/updates/contents.lr
similarity index 100%
rename from content/relay/setup/guard/debianubuntu/updates/contents.lr
rename to content/relay/setup/guard/debian-ubuntu/updates/contents.lr
___
tor-commits mailing list
tor-commits@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits
[tor-commits] [community/master] relay/setup (Linux-distros): give all setup guides consistent words to configure de Tor Project repo
commit 3cbe7f7b4a5d71809477bb3067d67909a8477e1f Author: VinÃcius Zavam Date: Sun Oct 24 19:44:41 2021 + relay/setup (Linux-distros): give all setup guides consistent words to configure de Tor Project repo --- content/relay/setup/guard/centosrhel/contents.lr | 4 ++-- content/relay/setup/guard/debianubuntu/contents.lr | 4 ++-- content/relay/setup/guard/fedora/contents.lr | 4 ++-- 3 files changed, 6 insertions(+), 6 deletions(-) diff --git a/content/relay/setup/guard/centosrhel/contents.lr b/content/relay/setup/guard/centosrhel/contents.lr index 52697dc..0d8372b 100644 --- a/content/relay/setup/guard/centosrhel/contents.lr +++ b/content/relay/setup/guard/centosrhel/contents.lr @@ -26,9 +26,9 @@ Recent versions of CentOS/RHEL are using `dnf` instead of `yum`, so the command If you are on a recent version that uses `dnf`, please keep using it for the following steps where `yum` is called on this setup guide. -# 3. Enable Tor Project's Repository +# 3. Configure Tor Project's Repository -Enabling the Tor Project's Repository for CentOS/RHEL consists basically on setting up `/etc/yum.repos.d/Tor.repo` with the following content: +Configuring the Tor Project's Repository for CentOS/RHEL consists basically on setting up `/etc/yum.repos.d/Tor.repo` with the following content: ``` [tor] diff --git a/content/relay/setup/guard/debianubuntu/contents.lr b/content/relay/setup/guard/debianubuntu/contents.lr index c1d7c35..a93ba19 100644 --- a/content/relay/setup/guard/debianubuntu/contents.lr +++ b/content/relay/setup/guard/debianubuntu/contents.lr @@ -11,9 +11,9 @@ body: One of the most important things to keeps your relay secure is to install security updates timely and ideally automatically so you can not forget about it. Follow the instructions to enable [automatic software updates](updates) for your operating system. -# 2. Configure Tor Package Repository +# 2. Configure Tor Project's Repository -Enable the Tor Project's package repository by following the instructions **[here](https://support.torproject.org/apt/tor-deb-repo/)**. +Configuring the Tor Project's package repository for Debian/Ubuntu is documented **[here](https://support.torproject.org/apt/tor-deb-repo/)**. Please follow those instructions before proceeding. # 3. Install `tor` diff --git a/content/relay/setup/guard/fedora/contents.lr b/content/relay/setup/guard/fedora/contents.lr index d392889..a3fb9cd 100644 --- a/content/relay/setup/guard/fedora/contents.lr +++ b/content/relay/setup/guard/fedora/contents.lr @@ -10,9 +10,9 @@ body: One of the most important things to keeps your relay secure is to install security updates timely and ideally automatically so you can not forget about it. Follow the instructions to enable [automatic software updates](updates) for your operating system. -# 2. Enable Tor Project's Repository +# 2. Configure Tor Project's Repository -Enabling the Tor Project's Repository for Fedora consists basically on setting up `/etc/yum.repos.d/Tor.repo` with the following content: +Configuring the Tor Project's Repository for Fedora consists basically on setting up `/etc/yum.repos.d/Tor.repo` with the following content: ``` [tor] ___ tor-commits mailing list tor-commits@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits
[tor-commits] [community/master] Merge branch 'consistency-linux'
commit 1110fb1b741b6662b16bb9ead63970da95f50e91 Merge: 195b50b 1d4afa9 Author: gus Date: Mon Oct 25 18:38:46 2021 -0300 Merge branch 'consistency-linux' content/relay/setup/guard/centos-rhel/contents.lr | 95 ++ .../updates/contents.lr| 0 content/relay/setup/guard/centosrhel/contents.lr | 78 -- .../relay/setup/guard/debian-ubuntu/contents.lr| 62 ++ .../updates/contents.lr| 0 content/relay/setup/guard/debianubuntu/contents.lr | 60 -- content/relay/setup/guard/fedora/contents.lr | 35 7 files changed, 178 insertions(+), 152 deletions(-) ___ tor-commits mailing list tor-commits@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits
[tor-commits] [community/master] relay/setup (Debian/Ubuntu): minor fixes on Markdown for shell console
commit 6738a608b285ce8bc23ca4527aba0fb88a8c3c16 Author: VinÃcius Zavam Date: Sun Oct 24 19:37:18 2021 + relay/setup (Debian/Ubuntu): minor fixes on Markdown for shell console --- content/relay/setup/guard/debianubuntu/contents.lr | 11 +++ 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/content/relay/setup/guard/debianubuntu/contents.lr b/content/relay/setup/guard/debianubuntu/contents.lr index 1936917..c1d7c35 100644 --- a/content/relay/setup/guard/debianubuntu/contents.lr +++ b/content/relay/setup/guard/debianubuntu/contents.lr @@ -19,9 +19,10 @@ Enable the Tor Project's package repository by following the instructions **[her Ensure you update the packages database before installing the package, than call `apt` to install it: -`apt update` - -`apt install tor` +``` +# apt update +# apt install tor +``` # 4. Configure `/etc/tor/torrc` @@ -39,7 +40,9 @@ SocksPort 0 Restart the `tor` daemon, so your configuration changes take effect: -`systemctl restart tor@default` +``` +# systemctl restart tor@default +``` # 6. Final Notes ___ tor-commits mailing list tor-commits@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits
[tor-commits] [community/master] relay/setup (Fedora): minor fixes on Markdown for shell console
commit 8192d06ce4fe1450697bef5f38d865604e0c1290 Author: VinÃcius Zavam Date: Sun Oct 24 19:35:50 2021 + relay/setup (Fedora): minor fixes on Markdown for shell console --- content/relay/setup/guard/fedora/contents.lr | 8 ++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/content/relay/setup/guard/fedora/contents.lr b/content/relay/setup/guard/fedora/contents.lr index caec0f2..d392889 100644 --- a/content/relay/setup/guard/fedora/contents.lr +++ b/content/relay/setup/guard/fedora/contents.lr @@ -30,7 +30,9 @@ More information about it can be found [here](https://support.torproject.org/rpm Once you are set with EPEL and the Tor repositories, you are now able to install the package: -`dnf install tor` +``` +# dnf install tor +``` # 4. Configure `/etc/tor/torrc` @@ -46,7 +48,9 @@ SocksPort 0 # 5. Enable and Start `tor` -`systemctl enable --now tor` +``` +# systemctl enable --now tor +``` # 6. Final Notes ___ tor-commits mailing list tor-commits@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits
[tor-commits] [community/master] relay/setup (CentOS-likes): add note about the first time using the Tor repo
commit d29d38d755fd39559c140414a6241aa41efcd2ca Author: VinÃcius Zavam Date: Sun Oct 24 13:43:58 2021 + relay/setup (CentOS-likes): add note about the first time using the Tor repo --- content/relay/setup/guard/centosrhel/contents.lr | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/relay/setup/guard/centosrhel/contents.lr b/content/relay/setup/guard/centosrhel/contents.lr index 70e1cdb..81f1d30 100644 --- a/content/relay/setup/guard/centosrhel/contents.lr +++ b/content/relay/setup/guard/centosrhel/contents.lr @@ -44,7 +44,7 @@ Once you are set with EPEL and the Tor repositories, you are now able to install `yum install tor` -Please note that when you are installing the first package from the EPEL repository you will be asked about verifying the EPEL's GPG signing key. Please ensure the key matches with the one available on the [Fedora Project website](https://getfedora.org/keys/). +Please note that when you are installing the first package from the EPEL repository you will be asked about verifying the EPEL's GPG signing key. Please ensure the key matches with the one available on the [Fedora Project website](https://getfedora.org/keys/). This will also happens when installing packages from Tor's repository for the first time - again you must ensure the key matches. # 5. Configure `/etc/tor/torrc` ___ tor-commits mailing list tor-commits@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits
[tor-commits] [community/master] relay/setup (Fedora): promote full page update, to follow previous changes
commit e96b9cb7e89ffd7eb2e0c76b5cc651d4f8ce515e Author: VinÃcius Zavam Date: Sun Oct 24 13:47:21 2021 + relay/setup (Fedora): promote full page update, to follow previous changes --- content/relay/setup/guard/fedora/contents.lr | 35 +++- 1 file changed, 19 insertions(+), 16 deletions(-) diff --git a/content/relay/setup/guard/fedora/contents.lr b/content/relay/setup/guard/fedora/contents.lr index 997ed43..caec0f2 100644 --- a/content/relay/setup/guard/fedora/contents.lr +++ b/content/relay/setup/guard/fedora/contents.lr @@ -10,7 +10,9 @@ body: One of the most important things to keeps your relay secure is to install security updates timely and ideally automatically so you can not forget about it. Follow the instructions to enable [automatic software updates](updates) for your operating system. -# 2. Add the following to `/etc/yum.repos.d/tor.repo` and then install the tor package. +# 2. Enable Tor Project's Repository + +Enabling the Tor Project's Repository for Fedora consists basically on setting up `/etc/yum.repos.d/Tor.repo` with the following content: ``` [tor] @@ -22,30 +24,31 @@ gpgkey=https://rpm.torproject.org/fedora/public_gpg.key cost=100 ``` -`sudo dnf install tor` +More information about it can be found [here](https://support.torproject.org/rpm/). +# 3. Install `tor` -# 3. Configuration File +Once you are set with EPEL and the Tor repositories, you are now able to install the package: -Put the configuration file `/etc/tor/torrc` in place: +`dnf install tor` -``` -#change the nickname "myNiceRelay" to a name that you like -Nickname myNiceRelay -ORPort 9001 -ExitRelay 0 -# Change the email address below and be aware that it will be published -ContactInfo tor-operator@your-emailaddress-domain -``` +# 4. Configure `/etc/tor/torrc` -# 4. Start the tor daemon and make sure it starts at boot +This is a very simple version of the `torrc` configuration file in order to run a Middle/Guard relay on the Tor network: ``` -systemctl enable tor -systemctl start tor +NicknamemyNiceRelay # Change "myNiceRelay" to something you like +ContactInfo your@e-mail # Write your e-mail and be aware it will be published +ORPort 443 # You might use a different port, should you want to +ExitRelay 0 +SocksPort 0 ``` -# 5. Final notes +# 5. Enable and Start `tor` + +`systemctl enable --now tor` + +# 6. Final Notes If you are having trouble setting up your relay, have a look at our [help section](/relay/getting-help/). If your relay is now running, check out the [post-install](/relay/setup/post-install/) notes. ___ tor-commits mailing list tor-commits@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits
[tor-commits] [community/master] relay/setup (CentOS/RHEL): minor fixes on Markdown for shell console
commit 91a6ee5f3e5a871786d4d8ca352088d9db7b21a3 Author: VinÃcius Zavam Date: Sun Oct 24 19:34:14 2021 + relay/setup (CentOS/RHEL): minor fixes on Markdown for shell console --- content/relay/setup/guard/centosrhel/contents.lr | 24 1 file changed, 16 insertions(+), 8 deletions(-) diff --git a/content/relay/setup/guard/centosrhel/contents.lr b/content/relay/setup/guard/centosrhel/contents.lr index 81f1d30..52697dc 100644 --- a/content/relay/setup/guard/centosrhel/contents.lr +++ b/content/relay/setup/guard/centosrhel/contents.lr @@ -14,11 +14,15 @@ One of the most important things to keeps your relay secure is to install securi To install `tor` on CentOS/RHEL, you need to enable the use of the [EPEL](https://fedoraproject.org/wiki/EPEL) Repository first. To do so, you must install the `epel-release` package: -`yum install epel-release` +``` +# yum install epel-release +``` Recent versions of CentOS/RHEL are using `dnf` instead of `yum`, so the command to install the package would be: -`dnf install epel-release` +``` +# dnf install epel-release +``` If you are on a recent version that uses `dnf`, please keep using it for the following steps where `yum` is called on this setup guide. @@ -42,7 +46,9 @@ More information about it can be found [here](https://support.torproject.org/rpm Once you are set with EPEL and the Tor repositories, you are now able to install the package: -`yum install tor` +``` +# yum install tor +``` Please note that when you are installing the first package from the EPEL repository you will be asked about verifying the EPEL's GPG signing key. Please ensure the key matches with the one available on the [Fedora Project website](https://getfedora.org/keys/). This will also happens when installing packages from Tor's repository for the first time - again you must ensure the key matches. @@ -62,19 +68,21 @@ SocksPort 0 Recent versions os CentOS/RHEL which ship with systemd: -`systemctl enable --now tor` +``` +# systemctl enable --now tor +``` Should you use an older release like CentOS/RHEL 6, that will be: -`service tor enable` - -`service tor start` +``` +# service tor enable +# service tor start +``` # 7. Final Notes If you are having trouble setting up your relay, have a look at our [help section](/relay/getting-help/). If your relay is now running, check out the [post-install](/relay/setup/post-install/) notes. - --- html: two-columns-page.html --- ___ tor-commits mailing list tor-commits@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits
[tor-commits] [community/master] relay/setup (CentOS-likes): promote full page update, to follow Debian-like changes
commit db26be9c90ff2f313b118aa46528861d81479cd7 Author: VinÃcius Zavam Date: Sun Oct 24 13:32:31 2021 + relay/setup (CentOS-likes): promote full page update, to follow Debian-like changes --- content/relay/setup/guard/centosrhel/contents.lr | 57 +--- 1 file changed, 32 insertions(+), 25 deletions(-) diff --git a/content/relay/setup/guard/centosrhel/contents.lr b/content/relay/setup/guard/centosrhel/contents.lr index e5e7afd..54b7d29 100644 --- a/content/relay/setup/guard/centosrhel/contents.lr +++ b/content/relay/setup/guard/centosrhel/contents.lr @@ -10,13 +10,21 @@ body: One of the most important things to keeps your relay secure is to install security updates timely and ideally automatically so you can not forget about it. Follow the instructions to enable [automatic software updates](updates) for your operating system. -# 2. Enable the EPEL repository +# 2. Install `epel-release` -To install `tor` package on CentOS/RHEL, you need to install the [EPEL](https://fedoraproject.org/wiki/EPEL) repository first: +To install `tor` on CentOS/RHEL, you need to enable the use of the [EPEL](https://fedoraproject.org/wiki/EPEL) Repository first. To do so, you must install the `epel-release` package: `yum install epel-release` -# 3. Add the following to /etc/yum.repos.d/tor.repo and then install the tor package. +Recent versions of CentOS/RHEL are using `dnf` instead of `yum`, so the command to install the package would be: + +`dnf install epel-release` + +If you are on a recent version that uses `dnf`, please keep using it for the following steps where `yum` is called on this setup guide. + +# 3. Enable Tor Project's Repository + +Enabling the Tor Project's Repository for CentOS/RHEL consists basically on setting up `/etc/yum.repos.d/Tor.repo` with the following content: ``` [tor] @@ -28,40 +36,39 @@ gpgkey=https://rpm.torproject.org/centos/public_gpg.key cost=100 ``` +More information about it can be found [here](https://support.torproject.org/rpm/). + +# 4. Install `tor` + +Once you are set with EPEL and the Tor repositories, you are now able to install the package: + `yum install tor` -When you install the first package from the EPEL repository you will be asked about verifying the EPEL GPG signing key. -Please ensure the key matches with the one available on the [Fedora Project website](https://getfedora.org/keys/). +Please note that when you are installing the first package from the EPEL repository you will be asked about verifying the EPEL's GPG signing key. Please ensure the key matches with the one available on the [Fedora Project website](https://getfedora.org/keys/). -# 4. Put the tor configuration file `/etc/tor/torrc` in place +# 5. Configure `/etc/tor/torrc` ``` -#change the nickname "myNiceRelay" to a name that you like -Nickname myNiceRelay -ORPort 9001 -SocksPort 0 -ExitRelay 0 -# Change the email address below and be aware that it will be published -ContactInfo tor-operator@your-emailaddress-domain +NicknamemyNiceRelay # Change "myNiceRelay" to something you like +ContactInfo your@e-mail # Write your e-mail and be aware it will be published +ORPort 443 # You might use a different port, should you want to +ExitRelay 0 +SocksPort 0 ``` -# 5. Enable and start your Tor relay +# 6. Enable and Start `tor` -CentOS 7 / RHEL 7: +Recent versions os CentOS/RHEL which ship with systemd: -``` -systemctl enable tor -systemctl start tor -``` +`systemctl enable --now tor` -CentOS 6 / RHEL 6: +Should you use an older release like CentOS/RHEL 6, that will be: -``` -service tor enable -service tor start -``` +`service tor enable` + +`service tor start` -# 6. Final notes +# 7. Final Notes If you are having trouble setting up your relay, have a look at our [help section](/relay/getting-help/). If your relay is now running, check out the [post-install](/relay/setup/post-install/) notes. ___ tor-commits mailing list tor-commits@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits
[tor-commits] [community/master] relay/setup (CentOS-likes): add a note about "torrc" configurations
commit d0408f6496bae9097d8a734d56b315d2f837ebf0 Author: VinÃcius Zavam Date: Sun Oct 24 13:33:44 2021 + relay/setup (CentOS-likes): add a note about "torrc" configurations --- content/relay/setup/guard/centosrhel/contents.lr | 2 ++ 1 file changed, 2 insertions(+) diff --git a/content/relay/setup/guard/centosrhel/contents.lr b/content/relay/setup/guard/centosrhel/contents.lr index 54b7d29..70e1cdb 100644 --- a/content/relay/setup/guard/centosrhel/contents.lr +++ b/content/relay/setup/guard/centosrhel/contents.lr @@ -48,6 +48,8 @@ Please note that when you are installing the first package from the EPEL reposit # 5. Configure `/etc/tor/torrc` +This is a very simple version of the `torrc` configuration file in order to run a Middle/Guard relay on the Tor network: + ``` NicknamemyNiceRelay # Change "myNiceRelay" to something you like ContactInfo your@e-mail # Write your e-mail and be aware it will be published ___ tor-commits mailing list tor-commits@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits
[tor-commits] [community/master] relay/setup (Debian-likes): offers the simplest "torrc" possible --- while here, remove the ControlSocket option as it is already set to zero by default
commit 98bac1226986fa3d30ab939f7100b940e33e13d5 Author: VinÃcius Zavam Date: Sun Oct 24 13:05:10 2021 + relay/setup (Debian-likes): offers the simplest "torrc" possible --- while here, remove the ControlSocket option as it is already set to zero by default --- content/relay/setup/guard/debianubuntu/contents.lr | 13 + 1 file changed, 5 insertions(+), 8 deletions(-) diff --git a/content/relay/setup/guard/debianubuntu/contents.lr b/content/relay/setup/guard/debianubuntu/contents.lr index b81978f..27431ee 100644 --- a/content/relay/setup/guard/debianubuntu/contents.lr +++ b/content/relay/setup/guard/debianubuntu/contents.lr @@ -29,14 +29,11 @@ apt install tor This is a very simple version of the `torrc` configuration file in order to run a Middle/Guard relay on the Tor network: ``` -#change the nickname "myNiceRelay" to a name that you like -Nickname myNiceRelay -ORPort 443 -ExitRelay 0 -SocksPort 0 -ControlSocket 0 -# Change the email address below and be aware that it will be published -ContactInfo tor-operator@your-emailaddress-domain +NicknamemyNiceRelay # Change "myNiceRelay" to something you like +ContactInfo your@e-mail # Write your e-mail and be aware it will be published +ORPort 443 # You might use a different port, should you want to +ExitRelay 0 +SocksPort 0 ``` # 5. Restart the Service ___ tor-commits mailing list tor-commits@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits
[tor-commits] [community/master] relay/setup (Debian-likes): fix minor typos/pontuations, and empty spaces
commit c73e35793c32370c7ca6117254b88db90d8d63eb Author: VinÃcius Zavam Date: Sun Oct 24 12:57:54 2021 + relay/setup (Debian-likes): fix minor typos/pontuations, and empty spaces --- content/relay/setup/guard/debianubuntu/contents.lr | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/content/relay/setup/guard/debianubuntu/contents.lr b/content/relay/setup/guard/debianubuntu/contents.lr index 884e4f9..c72554b 100644 --- a/content/relay/setup/guard/debianubuntu/contents.lr +++ b/content/relay/setup/guard/debianubuntu/contents.lr @@ -13,15 +13,15 @@ Follow the instructions to enable [automatic software updates](updates) for your # 2. Configure Tor Package Repository -Enable the Torproject package repository by following the instructions **[here](https://support.torproject.org/apt/tor-deb-repo/)**. +Enable the Tor Project's package repository by following the instructions **[here](https://support.torproject.org/apt/tor-deb-repo/)**. -# 3. Package Installation +# 3. Install `tor` Install the `tor` package: `apt update && apt install tor` -# 4. Configuration File +# 4. Configure `/etc/tor/torrc` Put the configuration file `/etc/tor/torrc` in place: @@ -42,7 +42,7 @@ Restart the tor daemon so your configuration changes take effect: `systemctl restart tor@default` -# 6. Final notes +# 6. Final Notes If you are having trouble setting up your relay, have a look at our [help section](/relay/getting-help/). If your relay is now running, check out the [post-install](/relay/setup/post-install/) notes. ___ tor-commits mailing list tor-commits@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits
[tor-commits] [community/master] relay/setup (Debian-likes): revert markdown used to call commands
commit a7d7c8864fedc66d33349c3e5c4ef97b0dbdbe09 Author: VinÃcius Zavam Date: Sun Oct 24 13:10:30 2021 + relay/setup (Debian-likes): revert markdown used to call commands --- content/relay/setup/guard/debianubuntu/contents.lr | 11 --- 1 file changed, 4 insertions(+), 7 deletions(-) diff --git a/content/relay/setup/guard/debianubuntu/contents.lr b/content/relay/setup/guard/debianubuntu/contents.lr index 27431ee..1936917 100644 --- a/content/relay/setup/guard/debianubuntu/contents.lr +++ b/content/relay/setup/guard/debianubuntu/contents.lr @@ -19,10 +19,9 @@ Enable the Tor Project's package repository by following the instructions **[her Ensure you update the packages database before installing the package, than call `apt` to install it: -``` -apt update -apt install tor -``` +`apt update` + +`apt install tor` # 4. Configure `/etc/tor/torrc` @@ -40,9 +39,7 @@ SocksPort 0 Restart the `tor` daemon, so your configuration changes take effect: -``` -systemctl restart tor@default -``` +`systemctl restart tor@default` # 6. Final Notes ___ tor-commits mailing list tor-commits@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits
[tor-commits] [community/master] relay/setup (Debian-likes): fix how markdown is used to call commands
commit bf1d6aa1fb0d7b28724da09ee190e271ca30f921 Author: VinÃcius Zavam Date: Sun Oct 24 13:03:25 2021 + relay/setup (Debian-likes): fix how markdown is used to call commands --- content/relay/setup/guard/debianubuntu/contents.lr | 15 ++- 1 file changed, 10 insertions(+), 5 deletions(-) diff --git a/content/relay/setup/guard/debianubuntu/contents.lr b/content/relay/setup/guard/debianubuntu/contents.lr index c72554b..b81978f 100644 --- a/content/relay/setup/guard/debianubuntu/contents.lr +++ b/content/relay/setup/guard/debianubuntu/contents.lr @@ -17,13 +17,16 @@ Enable the Tor Project's package repository by following the instructions **[her # 3. Install `tor` -Install the `tor` package: +Ensure you update the packages database before installing the package, than call `apt` to install it: -`apt update && apt install tor` +``` +apt update +apt install tor +``` # 4. Configure `/etc/tor/torrc` -Put the configuration file `/etc/tor/torrc` in place: +This is a very simple version of the `torrc` configuration file in order to run a Middle/Guard relay on the Tor network: ``` #change the nickname "myNiceRelay" to a name that you like @@ -38,9 +41,11 @@ ContactInfo tor-operator@your-emailaddress-domain # 5. Restart the Service -Restart the tor daemon so your configuration changes take effect: +Restart the `tor` daemon, so your configuration changes take effect: -`systemctl restart tor@default` +``` +systemctl restart tor@default +``` # 6. Final Notes ___ tor-commits mailing list tor-commits@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits
[tor-commits] [tor/release-0.4.6] Update ChangeLog and ReleaseNotes after tor#40500 was merged.
commit 2ae7a71f433b8d30ab481f31468064063be8f77a Author: Alexander Færøy Date: Mon Oct 25 21:16:25 2021 + Update ChangeLog and ReleaseNotes after tor#40500 was merged. --- ChangeLog | 4 ReleaseNotes| 4 changes/ticket40500 | 3 --- 3 files changed, 8 insertions(+), 3 deletions(-) diff --git a/ChangeLog b/ChangeLog index 146b2a6909..e1fe3161f1 100644 --- a/ChangeLog +++ b/ChangeLog @@ -38,6 +38,10 @@ Changes in version 0.4.6.8 - 2021-10-26 - Improve logging when a bad HS version is given. Fixes bug 40476; bugfix on 0.4.6.1-alpha. + o Minor bugfix (CI, onion service): +- Exclude onion service version 2 Stem tests in our CI. Fixes bug 40500; + bugfix on 0.3.2.1-alpha. + o Minor bugfixes (compatibility): - Fix compatibility with the most recent Libevent versions, which no longer have an evdns_set_random_bytes() function. Because this diff --git a/ReleaseNotes b/ReleaseNotes index 13fe228fc2..483012ed39 100644 --- a/ReleaseNotes +++ b/ReleaseNotes @@ -42,6 +42,10 @@ Changes in version 0.4.6.8 - 2021-10-26 - Improve logging when a bad HS version is given. Fixes bug 40476; bugfix on 0.4.6.1-alpha. + o Minor bugfix (CI, onion service): +- Exclude onion service version 2 Stem tests in our CI. Fixes bug 40500; + bugfix on 0.3.2.1-alpha. + o Minor bugfixes (compatibility): - Fix compatibility with the most recent Libevent versions, which no longer have an evdns_set_random_bytes() function. Because this diff --git a/changes/ticket40500 b/changes/ticket40500 deleted file mode 100644 index 2e5ff39761..00 --- a/changes/ticket40500 +++ /dev/null @@ -1,3 +0,0 @@ - o Minor bugfix (CI, onion service): -- Exclude onion service version 2 Stem tests in our CI. Fixes bug 40500; - bugfix on 0.3.2.1-alpha. ___ tor-commits mailing list tor-commits@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits
[tor-commits] [tor/release-0.4.6] Merge branch 'maint-0.4.6' into release-0.4.6
commit 9e44116fe660b9f189c43dee389fe9db9a4f03ec Merge: 81b37dacb5 0c5128eeb2 Author: Alexander Færøy Date: Mon Oct 25 21:03:14 2021 + Merge branch 'maint-0.4.6' into release-0.4.6 changes/ticket40500 | 3 +++ scripts/ci/ci-driver.sh | 7 +++ 2 files changed, 6 insertions(+), 4 deletions(-) ___ tor-commits mailing list tor-commits@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits
[tor-commits] [tor/release-0.4.6] Merge branch 'maint-0.4.5' into maint-0.4.6
commit 0c5128eeb24c5f9e6b62117eb668f0c7679d0fc3 Merge: d496a75026 12c3787305 Author: Alexander Færøy Date: Mon Oct 25 21:02:55 2021 + Merge branch 'maint-0.4.5' into maint-0.4.6 changes/ticket40500 | 3 +++ scripts/ci/ci-driver.sh | 7 +++ 2 files changed, 6 insertions(+), 4 deletions(-) ___ tor-commits mailing list tor-commits@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits
[tor-commits] [tor/release-0.4.6] ci: Exclude HSv2 Stem tests
commit 12c37873050624ce2baff2db0cbbf26ef18e6111
Author: David Goulet
Date: Mon Oct 25 13:37:38 2021 -0400
ci: Exclude HSv2 Stem tests
Signed-off-by: David Goulet
---
changes/ticket40500 | 3 +++
scripts/ci/ci-driver.sh | 8
2 files changed, 11 insertions(+)
diff --git a/changes/ticket40500 b/changes/ticket40500
new file mode 100644
index 00..2e5ff39761
--- /dev/null
+++ b/changes/ticket40500
@@ -0,0 +1,3 @@
+ o Minor bugfix (CI, onion service):
+- Exclude onion service version 2 Stem tests in our CI. Fixes bug 40500;
+ bugfix on 0.3.2.1-alpha.
diff --git a/scripts/ci/ci-driver.sh b/scripts/ci/ci-driver.sh
index c07d99188b..e83b3d6f46 100755
--- a/scripts/ci/ci-driver.sh
+++ b/scripts/ci/ci-driver.sh
@@ -460,12 +460,20 @@ fi
if [[ "${STEM}" = "yes" ]]; then
start_section "Stem"
+ # 0.3.5 and onward have now disabled onion service v2 so we need to exclude
+ # these Stem tests from now on.
+ EXCLUDE_TESTS="--exclude-test
control.controller.test_ephemeral_hidden_services_v2 --exclude-test
control.controller.test_hidden_services_conf --exclude-test
control.controller.test_with_ephemeral_hidden_services_basic_auth
--exclude-test control.controller.test_without_ephemeral_hidden_services
--exclude-test
control.controller.test_with_ephemeral_hidden_services_basic_auth_no_credentials"
if [[ "${TOR_VER_AT_LEAST_044}" = 'yes' ]]; then
# This should probably be part of some test-stem make target.
+
+ # Disable the check around EXCLUDE_TESTS that requires double quote. We
+ # need it to be expanded.
+ # shellcheck disable=SC2086
if runcmd timelimit -p -t 520 -s USR1 -T 30 -S ABRT \
python3 "${STEM_PATH}/run_tests.py" \
--tor src/app/tor \
--integ --test control.controller \
+ $EXCLUDE_TESTS \
--test control.base_controller \
--test process \
--log TRACE \
___
tor-commits mailing list
tor-commits@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits
[tor-commits] [tor/release-0.4.5] Merge branch 'maint-0.4.5' into release-0.4.5
commit 290196a1391c194fc11fbf5145d2a058501c955f Merge: 10d469a731 12c3787305 Author: Alexander Færøy Date: Mon Oct 25 21:01:58 2021 + Merge branch 'maint-0.4.5' into release-0.4.5 changes/ticket40500 | 3 +++ scripts/ci/ci-driver.sh | 8 2 files changed, 11 insertions(+) ___ tor-commits mailing list tor-commits@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits
[tor-commits] [tor/maint-0.4.6] ci: Exclude HSv2 Stem tests
commit 12c37873050624ce2baff2db0cbbf26ef18e6111
Author: David Goulet
Date: Mon Oct 25 13:37:38 2021 -0400
ci: Exclude HSv2 Stem tests
Signed-off-by: David Goulet
---
changes/ticket40500 | 3 +++
scripts/ci/ci-driver.sh | 8
2 files changed, 11 insertions(+)
diff --git a/changes/ticket40500 b/changes/ticket40500
new file mode 100644
index 00..2e5ff39761
--- /dev/null
+++ b/changes/ticket40500
@@ -0,0 +1,3 @@
+ o Minor bugfix (CI, onion service):
+- Exclude onion service version 2 Stem tests in our CI. Fixes bug 40500;
+ bugfix on 0.3.2.1-alpha.
diff --git a/scripts/ci/ci-driver.sh b/scripts/ci/ci-driver.sh
index c07d99188b..e83b3d6f46 100755
--- a/scripts/ci/ci-driver.sh
+++ b/scripts/ci/ci-driver.sh
@@ -460,12 +460,20 @@ fi
if [[ "${STEM}" = "yes" ]]; then
start_section "Stem"
+ # 0.3.5 and onward have now disabled onion service v2 so we need to exclude
+ # these Stem tests from now on.
+ EXCLUDE_TESTS="--exclude-test
control.controller.test_ephemeral_hidden_services_v2 --exclude-test
control.controller.test_hidden_services_conf --exclude-test
control.controller.test_with_ephemeral_hidden_services_basic_auth
--exclude-test control.controller.test_without_ephemeral_hidden_services
--exclude-test
control.controller.test_with_ephemeral_hidden_services_basic_auth_no_credentials"
if [[ "${TOR_VER_AT_LEAST_044}" = 'yes' ]]; then
# This should probably be part of some test-stem make target.
+
+ # Disable the check around EXCLUDE_TESTS that requires double quote. We
+ # need it to be expanded.
+ # shellcheck disable=SC2086
if runcmd timelimit -p -t 520 -s USR1 -T 30 -S ABRT \
python3 "${STEM_PATH}/run_tests.py" \
--tor src/app/tor \
--integ --test control.controller \
+ $EXCLUDE_TESTS \
--test control.base_controller \
--test process \
--log TRACE \
___
tor-commits mailing list
tor-commits@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits
[tor-commits] [tor/maint-0.4.6] Merge branch 'maint-0.4.5' into maint-0.4.6
commit 0c5128eeb24c5f9e6b62117eb668f0c7679d0fc3 Merge: d496a75026 12c3787305 Author: Alexander Færøy Date: Mon Oct 25 21:02:55 2021 + Merge branch 'maint-0.4.5' into maint-0.4.6 changes/ticket40500 | 3 +++ scripts/ci/ci-driver.sh | 7 +++ 2 files changed, 6 insertions(+), 4 deletions(-) ___ tor-commits mailing list tor-commits@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits
[tor-commits] [tor/release-0.4.5] ci: Exclude HSv2 Stem tests
commit 12c37873050624ce2baff2db0cbbf26ef18e6111
Author: David Goulet
Date: Mon Oct 25 13:37:38 2021 -0400
ci: Exclude HSv2 Stem tests
Signed-off-by: David Goulet
---
changes/ticket40500 | 3 +++
scripts/ci/ci-driver.sh | 8
2 files changed, 11 insertions(+)
diff --git a/changes/ticket40500 b/changes/ticket40500
new file mode 100644
index 00..2e5ff39761
--- /dev/null
+++ b/changes/ticket40500
@@ -0,0 +1,3 @@
+ o Minor bugfix (CI, onion service):
+- Exclude onion service version 2 Stem tests in our CI. Fixes bug 40500;
+ bugfix on 0.3.2.1-alpha.
diff --git a/scripts/ci/ci-driver.sh b/scripts/ci/ci-driver.sh
index c07d99188b..e83b3d6f46 100755
--- a/scripts/ci/ci-driver.sh
+++ b/scripts/ci/ci-driver.sh
@@ -460,12 +460,20 @@ fi
if [[ "${STEM}" = "yes" ]]; then
start_section "Stem"
+ # 0.3.5 and onward have now disabled onion service v2 so we need to exclude
+ # these Stem tests from now on.
+ EXCLUDE_TESTS="--exclude-test
control.controller.test_ephemeral_hidden_services_v2 --exclude-test
control.controller.test_hidden_services_conf --exclude-test
control.controller.test_with_ephemeral_hidden_services_basic_auth
--exclude-test control.controller.test_without_ephemeral_hidden_services
--exclude-test
control.controller.test_with_ephemeral_hidden_services_basic_auth_no_credentials"
if [[ "${TOR_VER_AT_LEAST_044}" = 'yes' ]]; then
# This should probably be part of some test-stem make target.
+
+ # Disable the check around EXCLUDE_TESTS that requires double quote. We
+ # need it to be expanded.
+ # shellcheck disable=SC2086
if runcmd timelimit -p -t 520 -s USR1 -T 30 -S ABRT \
python3 "${STEM_PATH}/run_tests.py" \
--tor src/app/tor \
--integ --test control.controller \
+ $EXCLUDE_TESTS \
--test control.base_controller \
--test process \
--log TRACE \
___
tor-commits mailing list
tor-commits@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits
[tor-commits] [tor/release-0.4.5] Update ChangeLog and ReleaseNotes after tor#40500 was merged.
commit 2504bce7c3bccac0f225fa116bcaef2d64696de6 Author: Alexander Færøy Date: Mon Oct 25 21:08:07 2021 + Update ChangeLog and ReleaseNotes after tor#40500 was merged. --- ChangeLog | 4 ReleaseNotes| 4 changes/ticket40500 | 3 --- 3 files changed, 8 insertions(+), 3 deletions(-) diff --git a/ChangeLog b/ChangeLog index 13bc05f610..4cec8341eb 100644 --- a/ChangeLog +++ b/ChangeLog @@ -47,6 +47,10 @@ Changes in version 0.4.5.11 - 2021-10-26 immediately from startup. Previously, they waited until they had been running for a full day. Closes ticket 40337. + o Minor bugfix (CI, onion service): +- Exclude onion service version 2 Stem tests in our CI. Fixes bug 40500; + bugfix on 0.3.2.1-alpha. + o Minor bugfix (onion service, backport from 0.4.6.8): - Do not flag an HSDir as non-running in case the descriptor upload or fetch fails. An onion service closes pending directory diff --git a/ReleaseNotes b/ReleaseNotes index ed07c1703b..15e53b2b93 100644 --- a/ReleaseNotes +++ b/ReleaseNotes @@ -51,6 +51,10 @@ Changes in version 0.4.5.11 - 2021-10-26 immediately from startup. Previously, they waited until they had been running for a full day. Closes ticket 40337. + o Minor bugfix (CI, onion service): +- Exclude onion service version 2 Stem tests in our CI. Fixes bug 40500; + bugfix on 0.3.2.1-alpha. + o Minor bugfix (onion service, backport from 0.4.6.8): - Do not flag an HSDir as non-running in case the descriptor upload or fetch fails. An onion service closes pending directory diff --git a/changes/ticket40500 b/changes/ticket40500 deleted file mode 100644 index 2e5ff39761..00 --- a/changes/ticket40500 +++ /dev/null @@ -1,3 +0,0 @@ - o Minor bugfix (CI, onion service): -- Exclude onion service version 2 Stem tests in our CI. Fixes bug 40500; - bugfix on 0.3.2.1-alpha. ___ tor-commits mailing list tor-commits@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits
[tor-commits] [tor/maint-0.4.5] ci: Exclude HSv2 Stem tests
commit 12c37873050624ce2baff2db0cbbf26ef18e6111
Author: David Goulet
Date: Mon Oct 25 13:37:38 2021 -0400
ci: Exclude HSv2 Stem tests
Signed-off-by: David Goulet
---
changes/ticket40500 | 3 +++
scripts/ci/ci-driver.sh | 8
2 files changed, 11 insertions(+)
diff --git a/changes/ticket40500 b/changes/ticket40500
new file mode 100644
index 00..2e5ff39761
--- /dev/null
+++ b/changes/ticket40500
@@ -0,0 +1,3 @@
+ o Minor bugfix (CI, onion service):
+- Exclude onion service version 2 Stem tests in our CI. Fixes bug 40500;
+ bugfix on 0.3.2.1-alpha.
diff --git a/scripts/ci/ci-driver.sh b/scripts/ci/ci-driver.sh
index c07d99188b..e83b3d6f46 100755
--- a/scripts/ci/ci-driver.sh
+++ b/scripts/ci/ci-driver.sh
@@ -460,12 +460,20 @@ fi
if [[ "${STEM}" = "yes" ]]; then
start_section "Stem"
+ # 0.3.5 and onward have now disabled onion service v2 so we need to exclude
+ # these Stem tests from now on.
+ EXCLUDE_TESTS="--exclude-test
control.controller.test_ephemeral_hidden_services_v2 --exclude-test
control.controller.test_hidden_services_conf --exclude-test
control.controller.test_with_ephemeral_hidden_services_basic_auth
--exclude-test control.controller.test_without_ephemeral_hidden_services
--exclude-test
control.controller.test_with_ephemeral_hidden_services_basic_auth_no_credentials"
if [[ "${TOR_VER_AT_LEAST_044}" = 'yes' ]]; then
# This should probably be part of some test-stem make target.
+
+ # Disable the check around EXCLUDE_TESTS that requires double quote. We
+ # need it to be expanded.
+ # shellcheck disable=SC2086
if runcmd timelimit -p -t 520 -s USR1 -T 30 -S ABRT \
python3 "${STEM_PATH}/run_tests.py" \
--tor src/app/tor \
--integ --test control.controller \
+ $EXCLUDE_TESTS \
--test control.base_controller \
--test process \
--log TRACE \
___
tor-commits mailing list
tor-commits@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits
[tor-commits] [tor/main] Merge branch 'maint-0.4.6' into main
commit 04788dcf40947a01f9b8f0315f6353318f46d026 Merge: 91c83d1e08 0c5128eeb2 Author: Alexander Færøy Date: Mon Oct 25 21:03:14 2021 + Merge branch 'maint-0.4.6' into main changes/ticket40500 | 3 +++ scripts/ci/ci-driver.sh | 7 +++ 2 files changed, 6 insertions(+), 4 deletions(-) ___ tor-commits mailing list tor-commits@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits
[tor-commits] [tor/main] Merge branch 'maint-0.4.5' into maint-0.4.6
commit 0c5128eeb24c5f9e6b62117eb668f0c7679d0fc3 Merge: d496a75026 12c3787305 Author: Alexander Færøy Date: Mon Oct 25 21:02:55 2021 + Merge branch 'maint-0.4.5' into maint-0.4.6 changes/ticket40500 | 3 +++ scripts/ci/ci-driver.sh | 7 +++ 2 files changed, 6 insertions(+), 4 deletions(-) ___ tor-commits mailing list tor-commits@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits
[tor-commits] [tor/main] ci: Exclude HSv2 Stem tests
commit 12c37873050624ce2baff2db0cbbf26ef18e6111
Author: David Goulet
Date: Mon Oct 25 13:37:38 2021 -0400
ci: Exclude HSv2 Stem tests
Signed-off-by: David Goulet
---
changes/ticket40500 | 3 +++
scripts/ci/ci-driver.sh | 8
2 files changed, 11 insertions(+)
diff --git a/changes/ticket40500 b/changes/ticket40500
new file mode 100644
index 00..2e5ff39761
--- /dev/null
+++ b/changes/ticket40500
@@ -0,0 +1,3 @@
+ o Minor bugfix (CI, onion service):
+- Exclude onion service version 2 Stem tests in our CI. Fixes bug 40500;
+ bugfix on 0.3.2.1-alpha.
diff --git a/scripts/ci/ci-driver.sh b/scripts/ci/ci-driver.sh
index c07d99188b..e83b3d6f46 100755
--- a/scripts/ci/ci-driver.sh
+++ b/scripts/ci/ci-driver.sh
@@ -460,12 +460,20 @@ fi
if [[ "${STEM}" = "yes" ]]; then
start_section "Stem"
+ # 0.3.5 and onward have now disabled onion service v2 so we need to exclude
+ # these Stem tests from now on.
+ EXCLUDE_TESTS="--exclude-test
control.controller.test_ephemeral_hidden_services_v2 --exclude-test
control.controller.test_hidden_services_conf --exclude-test
control.controller.test_with_ephemeral_hidden_services_basic_auth
--exclude-test control.controller.test_without_ephemeral_hidden_services
--exclude-test
control.controller.test_with_ephemeral_hidden_services_basic_auth_no_credentials"
if [[ "${TOR_VER_AT_LEAST_044}" = 'yes' ]]; then
# This should probably be part of some test-stem make target.
+
+ # Disable the check around EXCLUDE_TESTS that requires double quote. We
+ # need it to be expanded.
+ # shellcheck disable=SC2086
if runcmd timelimit -p -t 520 -s USR1 -T 30 -S ABRT \
python3 "${STEM_PATH}/run_tests.py" \
--tor src/app/tor \
--integ --test control.controller \
+ $EXCLUDE_TESTS \
--test control.base_controller \
--test process \
--log TRACE \
___
tor-commits mailing list
tor-commits@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits
[tor-commits] [tor/main] Add Changelog and ReleaseNotes entry for tor#40500.
commit 0c521881f68aa8e2646775ff6951214f503e2f79 Author: Alexander Færøy Date: Mon Oct 25 21:18:35 2021 + Add Changelog and ReleaseNotes entry for tor#40500. --- ChangeLog | 4 ReleaseNotes| 4 changes/ticket40500 | 3 --- 3 files changed, 8 insertions(+), 3 deletions(-) diff --git a/ChangeLog b/ChangeLog index 3cd9cc33de..4239f86a31 100644 --- a/ChangeLog +++ b/ChangeLog @@ -99,6 +99,10 @@ Changes in version 0.4.7.2-alpha - 2021-10-26 service leading to filling the logs with useless warnings. Fixes bug 34083; bugfix on 0.3.2.1-alpha. + o Minor bugfix (CI, onion service): +- Exclude onion service version 2 Stem tests in our CI. Fixes bug 40500; + bugfix on 0.3.2.1-alpha. + o Minor bugfixes (onion service, config): - Fix a memory leak for a small config line string that could occur if the onion service failed to be configured from file properly. diff --git a/ReleaseNotes b/ReleaseNotes index 8bcb61e7fa..34b8113bcb 100644 --- a/ReleaseNotes +++ b/ReleaseNotes @@ -32,6 +32,10 @@ Changes in version 0.4.6.7 - 2021-08-16 - Send back the extended SOCKS error 0xF6 (Onion Service Invalid Address) for a v2 onion address. Fixes bug 40421; bugfix on 0.4.6.2-alpha. + o Minor bugfix (CI, onion service): +- Exclude onion service version 2 Stem tests in our CI. Fixes bug 40500; + bugfix on 0.3.2.1-alpha. + o Minor bugfixes (relay): - Reduce the compression level for data streaming from HIGH to LOW in order to reduce CPU load on the directory relays. Fixes bug 40301; diff --git a/changes/ticket40500 b/changes/ticket40500 deleted file mode 100644 index 2e5ff39761..00 --- a/changes/ticket40500 +++ /dev/null @@ -1,3 +0,0 @@ - o Minor bugfix (CI, onion service): -- Exclude onion service version 2 Stem tests in our CI. Fixes bug 40500; - bugfix on 0.3.2.1-alpha. ___ tor-commits mailing list tor-commits@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits
[tor-commits] [tpo/master] Add new Tor Browser version 10.5.10
commit 850c13426074970e99794e688a6cd12a5154cb53 Author: Matthew Finkel Date: Mon Oct 25 17:56:29 2021 + Add new Tor Browser version 10.5.10 --- databags/versions.ini | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/databags/versions.ini b/databags/versions.ini index 41366765..23a4f5e1 100644 --- a/databags/versions.ini +++ b/databags/versions.ini @@ -1,15 +1,15 @@ [torbrowser-stable] -version = 10.5.8 +version = 10.5.10 win32 = 0.4.5.10 [torbrowser-android-stable] -version = 10.5.9 +version = 10.5.10 [torbrowser-win-stable] -version = 10.5.8 +version = 10.5.10 [torbrowser-linux-stable] -version = 10.5.8 +version = 10.5.10 [torbrowser-alpha] version = 11.0a9 ___ tor-commits mailing list tor-commits@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits
[tor-commits] [community/master] relay/setup (FreeBSD): follow Software Updates headline
commit 195b50bbf4a0ba1732b61ebfbd4b07a49a4d6d04 Author: VinÃcius Zavam Date: Sat Oct 23 10:10:53 2021 + relay/setup (FreeBSD): follow Software Updates headline relay/setup (NetBSD): follow Software Updates headline - here the text for the topic was added too relay/setup (NetBSD): fix topics counter relay/setup (OpenBSD): follow Software Updates headline relay/setup (OpenBSD): fix topics counter relay/setup (DragonFlyBSD): follow Software Updates headline relay/setup (DragonFlyBSD): fix topics counter relay/setup: use same text to describe "torrc" - DragonFlyBSD, and NetBSD updated relay/setup (DragonFlyBSD): rename "configuration" step - follow very same standard used by the other BSD systems relay/setup (NetBSD): make sure we have a "Final Notes" section relay/setup (OpenBSD): make sure we have a "Final Notes" section relay/setup (FreeBSD): update 12.0 to 12.2, after reproduced setup to confirm it works relay/setup (*BSD): offer a standard "torrc" when possible relay/setup (DragonFlyBSD): rename "install" and "start" steps - follow same way described by other BSD systems relay/setup (NetBSD): add small note about "pkgin" and "pkg_add" relay/setup (DragonFlyBSD): shrink "Recommendations" about pkg relay/setup (OpenBSD): avoid long titles, and line breaks relay/setup (FreeBSD): avoid long titles, and line breaks relay/setup (*BSD): remove colon from "Start tor" step relay/setup (OpenBSD): fix mention about recent OpenBSD versions - that is not related to amd64 only relay/setup (DragonFlyBSD): minor fixes on markdown for shell console relay/setup (FreeBSD): minor fixes on markdown for shell console relay/setup (NetBSD): minor fixes on markdown for shell console relay/setup (OpenBSD): minor fixes on markdown for shell console relay/setup (NetBSD): minor typo fix setup/relay (OpenBSD): apply fix fished from #158 guard (OpenBSD): make tor daemon happy on OpenBSD --- content/relay/setup/guard/dragonflybsd/contents.lr | 57 ++ content/relay/setup/guard/freebsd/contents.lr | 40 +++ content/relay/setup/guard/netbsd/contents.lr | 36 +- content/relay/setup/guard/openbsd/contents.lr | 48 ++ 4 files changed, 100 insertions(+), 81 deletions(-) diff --git a/content/relay/setup/guard/dragonflybsd/contents.lr b/content/relay/setup/guard/dragonflybsd/contents.lr index f5e9c39..d98ec6f 100644 --- a/content/relay/setup/guard/dragonflybsd/contents.lr +++ b/content/relay/setup/guard/dragonflybsd/contents.lr @@ -6,29 +6,30 @@ title: DragonflyBSD --- body: -# 1. Bootstrap `pkg` +# 1. Enable Automatic Software Updates -DragonFlyBSD's daily snapshots and releases (starting with 3.4) come with `pkg` already installed. -Upgrades from earlier releases, however, will not have it. +One of the most important things to keeps your relay secure is to install security updates timely and ideally automatically so you can not forget about it. Follow the instructions to enable automatic software updates for your operating system. -If `pkg` is missing on the system for any reason, it can be quickly bootstrapped without having to build it from source or even having **DPorts** installed: +# 2. Bootstrap `pkg` + +DragonFlyBSD's daily snapshots and releases (starting with 3.4) come with `pkg` already installed. Upgrades from earlier releases, however, will not have it. If `pkg` is missing on the system for any reason, it can be quickly bootstrapped without having to build it from source or even having **DPorts** installed: ``` -cd /usr -make pkg-bootstrap -rehash -pkg-static install -y pkg -rehash +# cd /usr +# make pkg-bootstrap +# rehash +# pkg-static install -y pkg +# rehash ``` -### 1.1. Recommended Steps to Setup `pkg` +### 2.1. Recommended Steps to Setup `pkg` Here, it will be similar to what we have on a **FreeBSD** system, and we are going to use HTTPS to fetch our packages, and updates - so here we also need an extra package to help us out (ca_root_nss). Installing the `ca_root_nss` package: ``` -pkg install ca_root_nss +# pkg install ca_root_nss ``` For fresh installations, the file `/usr/local/etc/pkg/repos/df-latest.conf.sample` is copied to `/usr/local/etc/pkg/repos/df-latest`. The files ending in the ".sample" extension are ignored; pkg(8) only reads files that end in ".conf" and it will read as many as it finds. @@ -43,53 +44,49 @@ We can simply edit the **URL** used to point out the repositories on `/usr/local After applying all these changes, we update the packages list again and try to check if there's already a new update to apply: ``` -pkg update -f -pkg upgrade -y -f +# pkg update -f +# pkg upgrade -y -f ``` -# 2. Package
[tor-commits] [lego/master] Merge remote-tracking branch 'hackerncoder/support-86'
commit bc96ee58985e63529559653e14b42430ad972c10
Merge: e28f603 4238e9a
Author: kez
Date: Mon Oct 25 13:29:58 2021 -0700
Merge remote-tracking branch 'hackerncoder/support-86'
assets/scss/_tor.scss | 6 ++
assets/static/css/bootstrap.css | 6 ++
2 files changed, 12 insertions(+)
diff --cc assets/static/css/bootstrap.css
index 43a9cb7,81ea9a1..12f731f
--- a/assets/static/css/bootstrap.css
+++ b/assets/static/css/bootstrap.css
@@@ -10081,9 -7969,14 +10081,15 @@@ size .no
.sticky {
position: sticky;
top: 105px;
- z-index: 999; }
+ z-index: 999;
+}
+ @media (max-width: 991px) {
+ .d-sm-block .sticky {
+ position: static !important;
+ }
+ }
+
@media (max-width: 767px) {
.mobile {
display: block !important;
___
tor-commits mailing list
tor-commits@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits
[tor-commits] [lego/master] tpo/web/support#86: reduce .sticky top px amount
commit 74642273c671f53c979c4e29f2edab5ecef08f20
Author: HackerNCoder
Date: Sat Sep 4 00:30:35 2021 +
tpo/web/support#86: reduce .sticky top px amount
---
assets/scss/_tor.scss | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/assets/scss/_tor.scss b/assets/scss/_tor.scss
index ddd6d16..5fe4408 100644
--- a/assets/scss/_tor.scss
+++ b/assets/scss/_tor.scss
@@ -715,7 +715,7 @@ table {
// Sticky menu
.sticky {
position: sticky;
- top: 105px;
+ top: 70px;
z-index: 999;
}
___
tor-commits mailing list
tor-commits@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits
[tor-commits] [lego/master] tpo/web/support#86: Make side static on md screens
commit 3a49ea2a09dd5c3501804bf1b04824175202f94b
Author: HackerNCoder
Date: Sat Sep 4 13:11:10 2021 +
tpo/web/support#86: Make side static on md screens
---
assets/scss/_tor.scss | 8 +++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/assets/scss/_tor.scss b/assets/scss/_tor.scss
index 5fe4408..b92f96a 100644
--- a/assets/scss/_tor.scss
+++ b/assets/scss/_tor.scss
@@ -715,10 +715,16 @@ table {
// Sticky menu
.sticky {
position: sticky;
- top: 70px;
+ top: 105px;
z-index: 999;
}
+@include media-breakpoint-down(md) {
+ .d-sm-block .sticky {
+position: static !important;
+ }
+}
+
// Small devices (landscape phones, less than 768px)
@include media-breakpoint-down(sm) {
.mobile {
___
tor-commits mailing list
tor-commits@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits
[tor-commits] [lego/master] Add compiled part
commit 4238e9a5ac93d4b509236bdf79c2919d2da855fd
Author: HackerNCoder
Date: Sat Sep 18 15:39:18 2021 +
Add compiled part
---
assets/static/css/bootstrap.css | 6 ++
1 file changed, 6 insertions(+)
diff --git a/assets/static/css/bootstrap.css b/assets/static/css/bootstrap.css
index 5efb48f..81ea9a1 100644
--- a/assets/static/css/bootstrap.css
+++ b/assets/static/css/bootstrap.css
@@ -7971,6 +7971,12 @@ size
top: 105px;
z-index: 999; }
+@media (max-width: 991px) {
+ .d-sm-block .sticky {
+position: static !important;
+ }
+}
+
@media (max-width: 767px) {
.mobile {
display: block !important;
___
tor-commits mailing list
tor-commits@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits
[tor-commits] [torspec/main] Fix typos and cleanup
commit 29245fd50d1ee3d96cca52154da4d888f34fedea Author: Dimitris Apostolou Date: Mon Oct 25 23:03:20 2021 +0300 Fix typos and cleanup --- README.md | 2 +- bandwidth-file-spec.txt | 2 +- bridgedb-spec.txt | 2 +- control-spec.txt| 6 +++--- dir-list-spec.txt | 4 ++-- dos-spec.md | 2 +- ext-orport-spec.txt | 6 +++--- guard-spec.txt | 2 +- param-spec.txt | 6 +++--- path-spec.txt | 8 pt-spec.txt | 8 rend-spec-v3.txt| 24 srv-spec.txt| 12 ++-- tor-spec.txt| 6 +++--- 14 files changed, 45 insertions(+), 45 deletions(-) diff --git a/README.md b/README.md index 1a02a37..bce6bcf 100644 --- a/README.md +++ b/README.md @@ -6,7 +6,7 @@ the reader to implement a compatible implementation of Tor without ever having to read the Tor source code. The [proposals](/proposals) directory holds our design proposals. These -include historical documents that have now been merged into . For more +include historical documents that have now been merged into. For more information on the proposal process, including an explanation of how to make new proposals, see, see [001-process.txt](/proposals/001-process.txt). diff --git a/bandwidth-file-spec.txt b/bandwidth-file-spec.txt index 58ce83c..d9f4db6 100644 --- a/bandwidth-file-spec.txt +++ b/bandwidth-file-spec.txt @@ -1161,7 +1161,7 @@ B.1. Scaling requirements B.2. A linear scaling method - If scaling is required, here is a simple linear bandwith scaling + If scaling is required, here is a simple linear bandwidth scaling method, which ensures that all bandwidth votes contain approximately the same total bandwidth: diff --git a/bridgedb-spec.txt b/bridgedb-spec.txt index 5ccce92..51f6e5d 100644 --- a/bridgedb-spec.txt +++ b/bridgedb-spec.txt @@ -94,7 +94,7 @@ Table of Contents in the bridge network status parsed earlier or if the bridge does not have the Running flag. BridgeDB discards bridge descriptors which have a different purpose - than "bridge". BridgeDB can be configured to only accept descriptors + than "bridge". BridgeDB can be configured to only accept descriptors with another purpose or not discard descriptors based on purpose at all. BridgeDB memorizes the IP addresses and OR ports of the remaining diff --git a/control-spec.txt b/control-spec.txt index 1feb250..0e2add3 100644 --- a/control-spec.txt +++ b/control-spec.txt @@ -1023,7 +1023,7 @@ Table of Contents "net/listeners/dir" - Listeners for Tor directory protocol, as decribed in dir-spec.txt. + Listeners for Tor directory protocol, as described in dir-spec.txt. "net/listeners/socks" @@ -2699,7 +2699,7 @@ Table of Contents [NOTE: This feature was removed in Tor 0.3.2.1-alpha.] - Tor generates this event when it's an directory authority, and + Tor generates this event when it's a directory authority, and somebody has just uploaded a server descriptor. Syntax: @@ -3736,7 +3736,7 @@ Table of Contents Program = The program path as defined in the *TransportPlugin configuration option. Tor accepts relative and full path. - Transport = This value indicate a hint on what the PT is such as the + Transport = This value indicates a hint on what the PT is such as the name or the protocol used for instance. Message = The status message that the PT sends back to the tor parent process minus the "STATUS" string prefix. Formatted as diff --git a/dir-list-spec.txt b/dir-list-spec.txt index c2d83f4..65af536 100644 --- a/dir-list-spec.txt +++ b/dir-list-spec.txt @@ -358,7 +358,7 @@ Table of Contents recent Tor versions. weight was removed in version 2.0.0, but is documented because it - may be of interest to libraries implementing Tor's fallaback + may be of interest to libraries implementing Tor's fallback behaviour. DQUOTE SP+ key_value DQUOTE SP* NL @@ -457,7 +457,7 @@ Table of Contents Libraries SHOULD consider the potential load on the authorities, and whether other sources can meet their needs. - Libraries that require high-uptime availablility of Tor directory + Libraries that require high-uptime availability of Tor directory information should investigate the following options: * OnionOO: https://metrics.torproject.org/onionoo.html diff --git a/dos-spec.md b/dos-spec.md index d1ca55c..04470b2 100644 --- a/dos-spec.md +++ b/dos-spec.md @@ -46,7 +46,7 @@ kinds of allocation: * Half-open stream records. * Cached onion service descriptors (hsdir only). * Cached DNS resolves (relay only). - * GEOIP-based usage activity statistics. + * GEOIP-based usage activity statistics. Note that directory caches aren't counted, since those are stored on disk and accessed via mmap.
[tor-commits] [torspec/main] Fix grammar in README.md
commit d3165c9ae0d346288ccb94fbfb831d2686f7abf3 Author: Nick Mathewson Date: Mon Oct 25 16:35:46 2021 -0400 Fix grammar in README.md --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index bce6bcf..3ad1db4 100644 --- a/README.md +++ b/README.md @@ -6,9 +6,9 @@ the reader to implement a compatible implementation of Tor without ever having to read the Tor source code. The [proposals](/proposals) directory holds our design proposals. These -include historical documents that have now been merged into. For more -information on the proposal process, including an explanation of how to -make new proposals, see, see +include historical documents that have now been merged into the main +specifications. For more information on the proposal process, including an +explanation of how to make new proposals, see [001-process.txt](/proposals/001-process.txt). ## What you can find here ___ tor-commits mailing list tor-commits@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits
[tor-commits] [torspec/main] Add proposals 336 and 337.
commit ea41a664476e7bc3690f080fbd3c13e2e32629fc
Author: Nick Mathewson
Date: Fri Oct 22 17:36:04 2021 -0400
Add proposals 336 and 337.
---
proposals/336-randomize-guard-retries.md | 87 +++
proposals/337-simpler-guard-usability.md | 138 +++
2 files changed, 225 insertions(+)
diff --git a/proposals/336-randomize-guard-retries.md
b/proposals/336-randomize-guard-retries.md
new file mode 100644
index 000..5ee5b71
--- /dev/null
+++ b/proposals/336-randomize-guard-retries.md
@@ -0,0 +1,87 @@
+```
+Filename: 336-randomize-guard-retries.md
+Title: Randomized schedule for guard retries
+Author: Nick Mathewson
+Created: 2021-10-22
+Status: Open
+```
+
+# Introduction
+
+When we notice that a guard isn't working, we don't mark it as retriable
+until a certain interval has passed. Currently, these intervals are
+fixed, as described in the documentation for `GUARDS_RETRY_SCHED` in
+`guard-spec` appendix A.1. Here we propose using a randomized retry
+interval instead, based on the same decorrelated-jitter algorithm we use
+for directory retries.
+
+The upside of this approach is that it makes our behavior in
+the presence of an unreliable network a bit harder for an attacker to
+predict. It also means that if a guard goes down for a while, its
+clients will notice that it is up at staggered times, rather than
+probing it in lock-step.
+
+The downside of this approach is that we can, if we get unlucky
+enough, completely fail to notice that a preferred guard is online when
+we would otherwise have noticed sooner.
+
+Note that when a guard is marked retriable, it isn't necessarily retried
+immediately. Instead, its status is changed from "Unreachable" to
+"Unknown", which will cause it to get retried.
+
+For reference, our previous schedule was:
+
+```
+ {param:PRIMARY_GUARDS_RETRY_SCHED}
+ -- every 10 minutes for the first six hours,
+ -- every 90 minutes for the next 90 hours,
+ -- every 4 hours for the next 3 days,
+ -- every 9 hours thereafter.
+
+ {param:GUARDS_RETRY_SCHED} --
+ -- every hour for the first six hours,
+ -- every 4 hours for the next 90 hours,
+ -- every 18 hours for the next 3 days,
+ -- every 36 hours thereafter.
+```
+
+# The new algorithm
+
+We re-use the decorrelated-jitter algorithm from `dir-spec` section 5.5.
+The specific formula used to compute the 'i+1'th delay is:
+
+```
+Delay_{i+1} = MIN(cap, random_between(lower_bound, upper_bound))
+where upper_bound = MAX(lower_bound+1, Delay_i * 3)
+ lower_bound = MAX(1, base_delay).
+```
+
+For primary guards, we set base_delay to 30 seconds and cap to 6 hours.
+
+For non-primary guards, we set base_delay to 10 minutes and cap to 36
+hours.
+
+(These parameters were selected by simulating the results of using them
+until they looked "a bit more aggressive" than the current algorithm, but
+not too much.)
+
+The average behavior for the new primary schedule is:
+
+```
+First 1.0 hours: 10.14283 attempts. (Avg delay 4m 47.41s)
+First 6.0 hours: 19.02377 attempts. (Avg delay 15m 36.95s)
+First 96.0 hours: 56.11173 attempts. (Avg delay 1h 40m 3.13s)
+First 168.0 hours: 83.67091 attempts. (Avg delay 1h 58m 43.16s)
+Steady state: 2h 36m 44.63s between attempts.
+```
+
+The average behavior for the new non-primary schedule is:
+
+```
+First 1.0 hours: 3.08069 attempts. (Avg delay 14m 26.08s)
+First 6.0 hours: 8.1473 attempts. (Avg delay 35m 25.27s)
+First 96.0 hours: 22.57442 attempts. (Avg delay 3h 49m 32.16s)
+First 168.0 hours: 29.02873 attempts. (Avg delay 5h 27m 2.36s)
+Steady state: 11h 15m 28.47s between attempts.
+```
+
diff --git a/proposals/337-simpler-guard-usability.md
b/proposals/337-simpler-guard-usability.md
new file mode 100644
index 000..d75c4d8
--- /dev/null
+++ b/proposals/337-simpler-guard-usability.md
@@ -0,0 +1,138 @@
+```
+Filename: 337-simpler-guard-usability.md
+Title: A simpler way to decide, "Is this guard usable?"
+Author: Nick Mathewson
+Created: 2021-10-22
+Status: Open
+```
+
+# Introduction
+
+The current `guard-spec` describes a mechanism for how to behave when
+our primary guards are unreachable, and we don't know which other guards
+are reachable. This proposal describes a simpler method, currently
+implemented in [Arti](https://gitlab.torproject.org/tpo/core/arti/).
+
+(Note that this method might not actually give different results: its
+only advantage is that it is much simpler to implement.)
+
+## The task at hand
+
+For illustration, we'll assume that our primary guards are P1, P2, and
+P3, and our subsequent guards (in preference order) are G1, G2, G3, and
+so on. The status of each guard is Reachable (we think we can connect
+to it), Unreachable (we think it's down), or Unknown (we haven't tried
+it recently).
+
+The question becomes, "What should we do when P1, P2, and P3 are
+Unreachable, and G1, G2, ... are all Unknown"?
+
+In this circumstance, we _could_ say that we only build circuits to G1,
[tor-commits] [torspec/main] Update proposal index.
commit c10dd31c0dcf970b8e199e029d56fc483f8a216c Author: Nick Mathewson Date: Mon Oct 25 16:33:21 2021 -0400 Update proposal index. --- proposals/000-index.txt | 4 proposals/BY_INDEX.md | 2 ++ proposals/README.md | 2 ++ 3 files changed, 8 insertions(+) diff --git a/proposals/000-index.txt b/proposals/000-index.txt index af0c8b1..3ae1776 100644 --- a/proposals/000-index.txt +++ b/proposals/000-index.txt @@ -256,6 +256,8 @@ Proposals by number: 333 Vanguards lite [DRAFT] 334 A Directory Authority Flag To Mark Relays As Middle-only [OPEN] 335 An authority-only design for MiddleOnly [OPEN] +336 Randomized schedule for guard retries [OPEN] +337 A simpler way to decide, "Is this guard usable?" [OPEN] Proposals by status: @@ -302,6 +304,8 @@ Proposals by status: 332 Ntor protocol with extra data, version 3 334 A Directory Authority Flag To Mark Relays As Middle-only 335 An authority-only design for MiddleOnly + 336 Randomized schedule for guard retries + 337 A simpler way to decide, "Is this guard usable?" ACCEPTED: 265 Load Balancing with Overhead Parameters [for 0.2.9.x] 275 Stop including meaningful "published" time in microdescriptor consensus [for 0.3.1.x-alpha] diff --git a/proposals/BY_INDEX.md b/proposals/BY_INDEX.md index 5e07863..31cc5f8 100644 --- a/proposals/BY_INDEX.md +++ b/proposals/BY_INDEX.md @@ -253,4 +253,6 @@ Below are a list of proposals sorted by their proposal number. See * [`333-vanguards-lite.md`](/proposals/333-vanguards-lite.md): Vanguards lite [DRAFT] * [`334-middle-only-flag.txt`](/proposals/334-middle-only-flag.txt): A Directory Authority Flag To Mark Relays As Middle-only [OPEN] * [`335-middle-only-redux.md`](/proposals/335-middle-only-redux.md): An authority-only design for MiddleOnly [OPEN] +* [`336-randomize-guard-retries.md`](/proposals/336-randomize-guard-retries.md): Randomized schedule for guard retries [OPEN] +* [`337-simpler-guard-usability.md`](/proposals/337-simpler-guard-usability.md): A simpler way to decide, "Is this guard usable?" [OPEN] diff --git a/proposals/README.md b/proposals/README.md index 49968f8..737dad1 100644 --- a/proposals/README.md +++ b/proposals/README.md @@ -43,6 +43,8 @@ for discussion. * [`332-ntor-v3-with-extra-data.md`](/proposals/332-ntor-v3-with-extra-data.md): Ntor protocol with extra data, version 3 * [`334-middle-only-flag.txt`](/proposals/334-middle-only-flag.txt): A Directory Authority Flag To Mark Relays As Middle-only * [`335-middle-only-redux.md`](/proposals/335-middle-only-redux.md): An authority-only design for MiddleOnly +* [`336-randomize-guard-retries.md`](/proposals/336-randomize-guard-retries.md): Randomized schedule for guard retries +* [`337-simpler-guard-usability.md`](/proposals/337-simpler-guard-usability.md): A simpler way to decide, "Is this guard usable?" ## ACCEPTED proposals: slated for implementation ___ tor-commits mailing list tor-commits@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits
[tor-commits] [lego/master] Rename two-part language codes to use a dash
commit e28f603b3e0353d6bd85c111ac23681cd9245d47
Author: kez
Date: Mon Oct 25 12:57:47 2021 -0700
Rename two-part language codes to use a dash
Lektor's this.alt uses a dash instead of an underscore (i.e. es-AR
instead of es_AR).
---
...{yec-activist-es...@2x.png => yec-activist-es...@2x.png} | Bin
...{yec-activist-es...@3x.png => yec-activist-es...@3x.png} | Bin
...{yec-activist-pt...@2x.png => yec-activist-pt...@2x.png} | Bin
...{yec-activist-pt...@3x.png => yec-activist-pt...@3x.png} | Bin
...{yec-activist-zn...@2x.png => yec-activist-zn...@2x.png} | Bin
...{yec-activist-zn...@3x.png => yec-activist-zn...@3x.png} | Bin
.../svg/{yec-activist-es_AR.svg => yec-activist-es-AR.svg} | 0
.../svg/{yec-activist-pt_BR.svg => yec-activist-pt-BR.svg} | 0
.../svg/{yec-activist-zn_CH.svg => yec-activist-zn-CH.svg} | 0
9 files changed, 0 insertions(+), 0 deletions(-)
diff --git a/assets/static/css/images/home/png/yec-activist-es...@2x.png
b/assets/static/css/images/home/png/yec-activist-es...@2x.png
similarity index 100%
rename from assets/static/css/images/home/png/yec-activist-es...@2x.png
rename to assets/static/css/images/home/png/yec-activist-es...@2x.png
diff --git a/assets/static/css/images/home/png/yec-activist-es...@3x.png
b/assets/static/css/images/home/png/yec-activist-es...@3x.png
similarity index 100%
rename from assets/static/css/images/home/png/yec-activist-es...@3x.png
rename to assets/static/css/images/home/png/yec-activist-es...@3x.png
diff --git a/assets/static/css/images/home/png/yec-activist-pt...@2x.png
b/assets/static/css/images/home/png/yec-activist-pt...@2x.png
similarity index 100%
rename from assets/static/css/images/home/png/yec-activist-pt...@2x.png
rename to assets/static/css/images/home/png/yec-activist-pt...@2x.png
diff --git a/assets/static/css/images/home/png/yec-activist-pt...@3x.png
b/assets/static/css/images/home/png/yec-activist-pt...@3x.png
similarity index 100%
rename from assets/static/css/images/home/png/yec-activist-pt...@3x.png
rename to assets/static/css/images/home/png/yec-activist-pt...@3x.png
diff --git a/assets/static/css/images/home/png/yec-activist-zn...@2x.png
b/assets/static/css/images/home/png/yec-activist-zn...@2x.png
similarity index 100%
rename from assets/static/css/images/home/png/yec-activist-zn...@2x.png
rename to assets/static/css/images/home/png/yec-activist-zn...@2x.png
diff --git a/assets/static/css/images/home/png/yec-activist-zn...@3x.png
b/assets/static/css/images/home/png/yec-activist-zn...@3x.png
similarity index 100%
rename from assets/static/css/images/home/png/yec-activist-zn...@3x.png
rename to assets/static/css/images/home/png/yec-activist-zn...@3x.png
diff --git a/assets/static/css/images/home/svg/yec-activist-es_AR.svg
b/assets/static/css/images/home/svg/yec-activist-es-AR.svg
similarity index 100%
rename from assets/static/css/images/home/svg/yec-activist-es_AR.svg
rename to assets/static/css/images/home/svg/yec-activist-es-AR.svg
diff --git a/assets/static/css/images/home/svg/yec-activist-pt_BR.svg
b/assets/static/css/images/home/svg/yec-activist-pt-BR.svg
similarity index 100%
rename from assets/static/css/images/home/svg/yec-activist-pt_BR.svg
rename to assets/static/css/images/home/svg/yec-activist-pt-BR.svg
diff --git a/assets/static/css/images/home/svg/yec-activist-zn_CH.svg
b/assets/static/css/images/home/svg/yec-activist-zn-CH.svg
similarity index 100%
rename from assets/static/css/images/home/svg/yec-activist-zn_CH.svg
rename to assets/static/css/images/home/svg/yec-activist-zn-CH.svg
___
tor-commits mailing list
tor-commits@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits
[tor-commits] [community/master] Convert untranslatable phrase on homepage to markdown
commit 472628aa24450231c7039e3c81a92a9f5ea7b02c
Author: kez
Date: Wed Oct 13 09:19:37 2021 -0700
Convert untranslatable phrase on homepage to markdown
Context: https://gitlab.torproject.org/tpo/web/community/-/issues/189
---
templates/homepage.html | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/templates/homepage.html b/templates/homepage.html
index 361ac35..99f38a1 100644
--- a/templates/homepage.html
+++ b/templates/homepage.html
@@ -22,9 +22,7 @@
-
- {{ _('The Tor Project is committed to fostering an inclusive
environment and community. Tor is a place where people should feel safe to
engage, share their point of view, and participate.') }} Read our https://gitweb.torproject.org/community/policies.git/tree/code_of_conduct.txt;
title="Code of Conduct" target="_blank">Code of Conduct, https://gitweb.torproject.org/community/policies.git/tree/social_contract.txt;
title="Social Contract" target="_blank">Social Contract, https://gitweb.torproject.org/community/policies.git/tree/statement_of_values.txt;
title="Statement of Values" target="_blank">Statement of Values and learn
about the https://gitweb.torproject.org/community/policies.git/tree/community_council.txt;
title="Tor Commmunity Council" target="_blank">Tor Community Council.
-
+{{ md(_('The Tor Project is committed to fostering an inclusive
environment and community. Tor is a place where people should feel safe to
engage, share their point of view, and participate. Read our [Code of
Conduct](https://gitweb.torproject.org/community/policies.git/tree/code_of_conduct.txt
"Code of Conduct"), [Social
Contract](https://gitweb.torproject.org/community/policies.git/tree/social_contract.txt
"Social Contract"), [Statement of
Values](https://gitweb.torproject.org/community/policies.git/tree/statement_of_values.txt
"Statement of Values"), and learn about the [Tor Community
Council](https://gitweb.torproject.org/community/policies.git/tree/community_council.txt
"Tor Community Council").')) }}
___
tor-commits mailing list
tor-commits@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits
[tor-commits] [donate-static/master] Update YEC metacard to newest version
commit 3f124317a837790ded2f8f1b182155fa48793299 Author: Duncan Date: Mon Oct 25 15:24:30 2021 + Update YEC metacard to newest version --- assets/static/images/donate/yec-metacard.png | Bin 44583 -> 43541 bytes 1 file changed, 0 insertions(+), 0 deletions(-) diff --git a/assets/static/images/donate/yec-metacard.png b/assets/static/images/donate/yec-metacard.png index a97389f9..d016f2c2 100644 Binary files a/assets/static/images/donate/yec-metacard.png and b/assets/static/images/donate/yec-metacard.png differ ___ tor-commits mailing list tor-commits@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits
[tor-commits] [donate-static/master] Fix leftover conflict in .gitlab-ci.yml
commit 115218c8314a1e58ead52c43c95df1ad6206d0b6 Author: kez Date: Mon Oct 25 11:34:14 2021 -0700 Fix leftover conflict in .gitlab-ci.yml --- .gitlab-ci.yml | 5 - 1 file changed, 5 deletions(-) diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml index 7194027c..0abc34f6 100644 --- a/.gitlab-ci.yml +++ b/.gitlab-ci.yml @@ -1,9 +1,4 @@ -<<< HEAD image: node:current-bullseye -=== -image: debian:buster-slim - ->>> e809cc4a6ae50f8734fe7863b8c1a336664fe522 # This template should be usable on any system that's based on apt. # taken from tor gitlabci ___ tor-commits mailing list tor-commits@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits
[tor-commits] [tpo/master] Update lego
commit 6b83d2180b003f87f894aa466bba337b5c19e207 Author: gus Date: Mon Oct 25 15:08:54 2021 -0300 Update lego --- lego | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/lego b/lego index 9d3943e7..c8ed9e1d 16 --- a/lego +++ b/lego @@ -1 +1 @@ -Subproject commit 9d3943e71f27eb5c21756106aef9ad0f4398aef2 +Subproject commit c8ed9e1d9cd895cdfb1a9b18822310b40cc93f58 ___ tor-commits mailing list tor-commits@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits
[tor-commits] [styleguide/master] Update lego
commit 4bd3b3f098f330a164d7c862369f7506430fcb83 Author: gus Date: Mon Oct 25 15:08:25 2021 -0300 Update lego --- lego | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/lego b/lego index 9d3943e..c8ed9e1 16 --- a/lego +++ b/lego @@ -1 +1 @@ -Subproject commit 9d3943e71f27eb5c21756106aef9ad0f4398aef2 +Subproject commit c8ed9e1d9cd895cdfb1a9b18822310b40cc93f58 ___ tor-commits mailing list tor-commits@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits
[tor-commits] [manual/master] Update lego
commit e4876be3fb1e296bf0d4c773ea7d4ad4df687a2e Author: gus Date: Mon Oct 25 15:08:00 2021 -0300 Update lego --- lego | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/lego b/lego index 9d3943e..c8ed9e1 16 --- a/lego +++ b/lego @@ -1 +1 @@ -Subproject commit 9d3943e71f27eb5c21756106aef9ad0f4398aef2 +Subproject commit c8ed9e1d9cd895cdfb1a9b18822310b40cc93f58 ___ tor-commits mailing list tor-commits@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits
[tor-commits] [community/master] Update lego
commit 3197ab5b41565eaec1dfd2c436c310d79e10572e Author: gus Date: Mon Oct 25 15:07:20 2021 -0300 Update lego --- lego | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/lego b/lego index 9d3943e..c8ed9e1 16 --- a/lego +++ b/lego @@ -1 +1 @@ -Subproject commit 9d3943e71f27eb5c21756106aef9ad0f4398aef2 +Subproject commit c8ed9e1d9cd895cdfb1a9b18822310b40cc93f58 ___ tor-commits mailing list tor-commits@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits
[tor-commits] [lego/master] Add yec banner
commit c8ed9e1d9cd895cdfb1a9b18822310b40cc93f58
Author: gus
Date: Mon Oct 25 15:05:11 2021 -0300
Add yec banner
---
templates/navbar.html | 1 +
1 file changed, 1 insertion(+)
diff --git a/templates/navbar.html b/templates/navbar.html
index 204b6a2..6e561dc 100644
--- a/templates/navbar.html
+++ b/templates/navbar.html
@@ -1,3 +1,4 @@
+{% include 'banner.html' %}
{% if not this.color %}
___
tor-commits mailing list
tor-commits@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits
[tor-commits] [torbutton/master] Merge remote-tracking branch 'richardgl/yec-translations'
commit fb69c2dc2c0104146329057150c08adc4ae79560 Merge: 448a4fd2 eafca9c9 Author: Matthew Finkel Date: Mon Oct 25 17:44:11 2021 + Merge remote-tracking branch 'richardgl/yec-translations' chrome/locale/ar/aboutTor.dtd| 28 chrome/locale/bn-BD/aboutTor.dtd | 28 chrome/locale/ca/aboutTor.dtd| 28 chrome/locale/cs/aboutTor.dtd| 28 chrome/locale/da/aboutTor.dtd| 28 chrome/locale/de/aboutTor.dtd| 28 chrome/locale/el/aboutTor.dtd| 32 ++-- chrome/locale/es-AR/aboutTor.dtd | 28 chrome/locale/es-ES/aboutTor.dtd | 28 chrome/locale/eu/aboutTor.dtd| 28 chrome/locale/fa/aboutTor.dtd| 28 chrome/locale/fr/aboutTor.dtd| 28 chrome/locale/ga-IE/aboutTor.dtd | 28 chrome/locale/he/aboutTor.dtd| 28 chrome/locale/hu/aboutTor.dtd| 28 chrome/locale/id/aboutTor.dtd| 28 chrome/locale/is/aboutTor.dtd| 28 chrome/locale/it/aboutTor.dtd| 28 chrome/locale/ja/aboutTor.dtd| 28 chrome/locale/ka/aboutTor.dtd| 28 chrome/locale/ko/aboutTor.dtd| 28 chrome/locale/lt/aboutTor.dtd| 28 chrome/locale/mk/aboutTor.dtd| 28 chrome/locale/ms/aboutTor.dtd| 28 chrome/locale/my/aboutTor.dtd| 28 chrome/locale/nb-NO/aboutTor.dtd | 28 chrome/locale/nl/aboutTor.dtd| 28 chrome/locale/pl/aboutTor.dtd| 28 chrome/locale/pt-BR/aboutTor.dtd | 28 chrome/locale/ro/aboutTor.dtd| 28 chrome/locale/ru/aboutTor.dtd| 28 chrome/locale/sv-SE/aboutTor.dtd | 30 +- chrome/locale/th/aboutTor.dtd| 28 chrome/locale/tr/aboutTor.dtd| 32 ++-- chrome/locale/vi/aboutTor.dtd| 28 chrome/locale/zh-CN/aboutTor.dtd | 28 chrome/locale/zh-TW/aboutTor.dtd | 28 37 files changed, 1041 insertions(+), 5 deletions(-) ___ tor-commits mailing list tor-commits@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits
[tor-commits] [torbutton/master] Translations update (for YEC)
commit eafca9c91b1aefaf3f2575bfcb6350214262c832 Author: Matthew Finkel Date: Thu Oct 21 18:20:03 2021 + Translations update (for YEC) --- chrome/locale/ar/aboutTor.dtd| 28 chrome/locale/bn-BD/aboutTor.dtd | 28 chrome/locale/ca/aboutTor.dtd| 28 chrome/locale/cs/aboutTor.dtd| 28 chrome/locale/da/aboutTor.dtd| 28 chrome/locale/de/aboutTor.dtd| 28 chrome/locale/el/aboutTor.dtd| 32 ++-- chrome/locale/es-AR/aboutTor.dtd | 28 chrome/locale/es-ES/aboutTor.dtd | 28 chrome/locale/eu/aboutTor.dtd| 28 chrome/locale/fa/aboutTor.dtd| 28 chrome/locale/fr/aboutTor.dtd| 28 chrome/locale/ga-IE/aboutTor.dtd | 28 chrome/locale/he/aboutTor.dtd| 28 chrome/locale/hu/aboutTor.dtd| 28 chrome/locale/id/aboutTor.dtd| 28 chrome/locale/is/aboutTor.dtd| 28 chrome/locale/it/aboutTor.dtd| 28 chrome/locale/ja/aboutTor.dtd| 28 chrome/locale/ka/aboutTor.dtd| 28 chrome/locale/ko/aboutTor.dtd| 28 chrome/locale/lt/aboutTor.dtd| 28 chrome/locale/mk/aboutTor.dtd| 28 chrome/locale/ms/aboutTor.dtd| 28 chrome/locale/my/aboutTor.dtd| 28 chrome/locale/nb-NO/aboutTor.dtd | 28 chrome/locale/nl/aboutTor.dtd| 28 chrome/locale/pl/aboutTor.dtd| 28 chrome/locale/pt-BR/aboutTor.dtd | 28 chrome/locale/ro/aboutTor.dtd| 28 chrome/locale/ru/aboutTor.dtd| 28 chrome/locale/sv-SE/aboutTor.dtd | 30 +- chrome/locale/th/aboutTor.dtd| 28 chrome/locale/tr/aboutTor.dtd| 32 ++-- chrome/locale/vi/aboutTor.dtd| 28 chrome/locale/zh-CN/aboutTor.dtd | 28 chrome/locale/zh-TW/aboutTor.dtd | 28 37 files changed, 1041 insertions(+), 5 deletions(-) diff --git a/chrome/locale/ar/aboutTor.dtd b/chrome/locale/ar/aboutTor.dtd index 00f2f913..60f87894 100644 --- a/chrome/locale/ar/aboutTor.dtd +++ b/chrome/locale/ar/aboutTor.dtd @@ -29,3 +29,31 @@ + + + + + + + + diff --git a/chrome/locale/bn-BD/aboutTor.dtd b/chrome/locale/bn-BD/aboutTor.dtd index e52c4b7a..0808560c 100644 --- a/chrome/locale/bn-BD/aboutTor.dtd +++ b/chrome/locale/bn-BD/aboutTor.dtd @@ -29,3 +29,31 @@ + + + + + + + + diff --git a/chrome/locale/ca/aboutTor.dtd b/chrome/locale/ca/aboutTor.dtd index 0741dd00..a566a3a9 100644 --- a/chrome/locale/ca/aboutTor.dtd +++ b/chrome/locale/ca/aboutTor.dtd @@ -29,3 +29,31 @@ + + + + + + + + diff --git a/chrome/locale/cs/aboutTor.dtd b/chrome/locale/cs/aboutTor.dtd index 4a2a2e2b..2d5dd753 100644 --- a/chrome/locale/cs/aboutTor.dtd +++ b/chrome/locale/cs/aboutTor.dtd @@ -29,3 +29,31 @@ + + + + + + + + diff --git a/chrome/locale/da/aboutTor.dtd b/chrome/locale/da/aboutTor.dtd index 09c87f8c..62a0faa8 100644 --- a/chrome/locale/da/aboutTor.dtd +++ b/chrome/locale/da/aboutTor.dtd @@ -29,3 +29,31 @@ + + + + + + + + diff --git a/chrome/locale/de/aboutTor.dtd b/chrome/locale/de/aboutTor.dtd index 65f3834a..05c71121 100644 --- a/chrome/locale/de/aboutTor.dtd +++ b/chrome/locale/de/aboutTor.dtd @@ -29,3 +29,31 @@ + + + + + + + + diff --git a/chrome/locale/el/aboutTor.dtd b/chrome/locale/el/aboutTor.dtd index 8d17ba12..a162ceaa 100644 --- a/chrome/locale/el/aboutTor.dtd +++ b/chrome/locale/el/aboutTor.dtd @@ -22,10 +22,38 @@ - + - + + + + + + + + + diff --git a/chrome/locale/es-AR/aboutTor.dtd b/chrome/locale/es-AR/aboutTor.dtd index 0c4ebb64..df88805e 100644 --- a/chrome/locale/es-AR/aboutTor.dtd +++ b/chrome/locale/es-AR/aboutTor.dtd @@ -29,3 +29,31 @@ + + + + + + + + diff --git a/chrome/locale/es-ES/aboutTor.dtd b/chrome/locale/es-ES/aboutTor.dtd index 0671a826..491c547a 100644 --- a/chrome/locale/es-ES/aboutTor.dtd +++ b/chrome/locale/es-ES/aboutTor.dtd @@ -29,3 +29,31 @@ + + + + + + + + diff --git a/chrome/locale/eu/aboutTor.dtd b/chrome/locale/eu/aboutTor.dtd index b115af74..75ec4f0b 100644 --- a/chrome/locale/eu/aboutTor.dtd +++ b/chrome/locale/eu/aboutTor.dtd @@ -29,3 +29,31 @@ + + + + + + + + diff --git
[tor-commits] [tor/main] last tweak on 0.4.7.2 changelog
commit 91c83d1e0857b84b2cf0594270cc149246f6f15a Author: Roger Dingledine Date: Mon Oct 25 12:48:49 2021 -0400 last tweak on 0.4.7.2 changelog --- ChangeLog | 12 ++-- 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/ChangeLog b/ChangeLog index afc7018fe6..3cd9cc33de 100644 --- a/ChangeLog +++ b/ChangeLog @@ -34,12 +34,12 @@ Changes in version 0.4.7.2-alpha - 2021-10-26 40490; bugfix on 0.4.7.1-alpha. o Major bugfixes (relay, overload state): -- Report the general overload state for DNS timeout errors only if - X% of all DNS queries over Y seconds are errors. Before that, it - only took 1 timeout to report the overload state which was just - too low of a threshold. The X and Y values are 1% and 10 minutes - respectively but they are also controlled by consensus parameters. - Fixes bug 40491; bugfix on 0.4.6.1-alpha. +- Relays report the general overload state for DNS timeout errors + only if X% of all DNS queries over Y seconds are errors. Before + that, it only took 1 timeout to report the overload state which + was just too low of a threshold. The X and Y values are 1% and 10 + minutes respectively but they are also controlled by consensus + parameters. Fixes bug 40491; bugfix on 0.4.6.1-alpha. o Minor feature (authority, relay): - Reject End-Of-Life relays running version 0.4.2.x, 0.4.3.x, ___ tor-commits mailing list tor-commits@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits
[tor-commits] [tor/release-0.4.6] 0.4.6 changelog cleanups
commit 81b37dacb58ebb1619f5f1c6de52cf97b38e48a5 Author: Roger Dingledine Date: Mon Oct 25 12:47:41 2021 -0400 0.4.6 changelog cleanups --- ChangeLog| 32 +++- ReleaseNotes | 37 +++-- 2 files changed, 30 insertions(+), 39 deletions(-) diff --git a/ChangeLog b/ChangeLog index 069efafc87..146b2a6909 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,20 +1,18 @@ Changes in version 0.4.6.8 - 2021-10-26 - This version fixes several bugs from earlier versions of Tor. Worth - noting is a fix on how we use DNS timeout to report general overload. - Everyone running an earlier version, whether as a client, a relay, or - an onion service, should upgrade to Tor 0.3.5.17, 0.4.5.11, - or 0.4.6.8. + This version fixes several bugs from earlier versions of Tor. One + highlight is a fix on how we track DNS timeouts to report general + relay overload. o Major bugfixes (relay, overload state): -- Report the general overload state for DNS timeout errors only if - X% of all DNS queries over Y seconds are errors. Before that, it - only took 1 timeout to report the overload state which was just - too low of a threshold. The X and Y values are 1% and 10 minutes - respectively but they are also controlled by consensus parameters. - Fixes bug 40491; bugfix on 0.4.6.1-alpha. +- Relays report the general overload state for DNS timeout errors + only if X% of all DNS queries over Y seconds are errors. Before + that, it only took 1 timeout to report the overload state which + was just too low of a threshold. The X and Y values are 1% and 10 + minutes respectively but they are also controlled by consensus + parameters. Fixes bug 40491; bugfix on 0.4.6.1-alpha. o Minor features (fallbackdir): -- Regenerate fallback directories for October 2021. Close +- Regenerate fallback directories for October 2021. Closes ticket 40493. o Minor features (testing): @@ -48,11 +46,11 @@ Changes in version 0.4.6.8 - 2021-10-26 on 0.2.1.7-alpha. o Minor bugfixes (onion service, TROVE-2021-008): -- Only log once any v2 access attempts in order to not pollute the - logs with warnings and avoid recording the times on disk when v2 - access was attempted. Important to note that the onion address was - _never_ logged. That is a Low security issue. Fixes bug 40474; - bugfix on 0.4.5.8. +- Only log v2 access attempts once total, in order to not pollute + the logs with warnings and to avoid recording the times on disk + when v2 access was attempted. Note that the onion address was + _never_ logged. This counts as a Low-severity security issue. + Fixes bug 40474; bugfix on 0.4.5.8. Changes in version 0.4.6.7 - 2021-08-16 diff --git a/ReleaseNotes b/ReleaseNotes index 425ee565ad..13fe228fc2 100644 --- a/ReleaseNotes +++ b/ReleaseNotes @@ -3,27 +3,20 @@ release of Tor. If you want to see more detailed descriptions of the changes in each development snapshot, see the ChangeLog file. Changes in version 0.4.6.8 - 2021-10-26 - This version fixes several bugs from earlier versions of Tor. Worth - noting is a fix on how we use DNS timeout to report general overload. - Everyone running an earlier version, whether as a client, a relay, or - an onion service, should upgrade to Tor 0.3.5.17, 0.4.5.11, - or 0.4.6.8. + This version fixes several bugs from earlier versions of Tor. One + highlight is a fix on how we track DNS timeouts to report general + relay overload. o Major bugfixes (relay, overload state): -- Report the general overload state for DNS timeout errors only if - X% of all DNS queries over Y seconds are errors. Before that, it - only took 1 timeout to report the overload state which was just - too low of a threshold. The X and Y values are 1% and 10 minutes - respectively but they are also controlled by consensus parameters. - Fixes bug 40491; bugfix on 0.4.6.1-alpha. - - o Minor features (bridge): -- We now announce the URL to Tor's new bridge status at - https://bridges.torproject.org/ when Tor is configured to run as a - bridge relay. Closes ticket 30477. +- Relays report the general overload state for DNS timeout errors + only if X% of all DNS queries over Y seconds are errors. Before + that, it only took 1 timeout to report the overload state which + was just too low of a threshold. The X and Y values are 1% and 10 + minutes respectively but they are also controlled by consensus + parameters. Fixes bug 40491; bugfix on 0.4.6.1-alpha. o Minor features (fallbackdir): -- Regenerate fallback directories for October 2021. Close +- Regenerate fallback directories for October 2021. Closes ticket 40493. o Minor features (testing): @@ -57,11 +50,11 @@ Changes in version 0.4.6.8 - 2021-10-26 on 0.2.1.7-alpha. o Minor
[tor-commits] [tpo/master] Update lego
commit 95d920e8572d2edf86b672cdc0f1c20d8951cae4 Author: gus Date: Mon Oct 25 13:46:44 2021 -0300 Update lego --- lego | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/lego b/lego index 8bbc4913..9d3943e7 16 --- a/lego +++ b/lego @@ -1 +1 @@ -Subproject commit 8bbc49137960f1e05654b65cdd65ae298cf5cb20 +Subproject commit 9d3943e71f27eb5c21756106aef9ad0f4398aef2 ___ tor-commits mailing list tor-commits@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits
[tor-commits] [styleguide/master] Update lego
commit a2cc18ee225ab7870ce6524f87f9013851bf17e9 Author: gus Date: Mon Oct 25 13:46:06 2021 -0300 Update lego --- lego | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/lego b/lego index 8bbc491..9d3943e 16 --- a/lego +++ b/lego @@ -1 +1 @@ -Subproject commit 8bbc49137960f1e05654b65cdd65ae298cf5cb20 +Subproject commit 9d3943e71f27eb5c21756106aef9ad0f4398aef2 ___ tor-commits mailing list tor-commits@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits
[tor-commits] [manual/master] Update lego
commit a4177509a459f95b0b8acde5de749355c0ea11eb Author: gus Date: Mon Oct 25 13:45:38 2021 -0300 Update lego --- lego | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/lego b/lego index 8bbc491..9d3943e 16 --- a/lego +++ b/lego @@ -1 +1 @@ -Subproject commit 8bbc49137960f1e05654b65cdd65ae298cf5cb20 +Subproject commit 9d3943e71f27eb5c21756106aef9ad0f4398aef2 ___ tor-commits mailing list tor-commits@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits
[tor-commits] [community/master] Update lego
commit b3afab5035b305f0b1016ac896d63b490ae5a83d Author: gus Date: Mon Oct 25 13:44:06 2021 -0300 Update lego --- lego | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/lego b/lego index 8bbc491..9d3943e 16 --- a/lego +++ b/lego @@ -1 +1 @@ -Subproject commit 8bbc49137960f1e05654b65cdd65ae298cf5cb20 +Subproject commit 9d3943e71f27eb5c21756106aef9ad0f4398aef2 ___ tor-commits mailing list tor-commits@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits
[tor-commits] [lego/master] i #33: add discourse logo to footer
commit 9d3943e71f27eb5c21756106aef9ad0f4398aef2 Author: HackerNCoder Date: Fri Oct 15 22:01:40 2021 + i #33: add discourse logo to footer --- templates/footer.html | 5 - 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/templates/footer.html b/templates/footer.html index 1b5b83d..666fcba 100644 --- a/templates/footer.html +++ b/templates/footer.html @@ -78,13 +78,16 @@ + https://forum.torproject.net;> https://www.facebook.com/TorProject/;> https://mastodon.social/@torproject; rel="me"> - https://twitter.com/torproject;> https://www.instagram.com/torproject;> + https://twitter.com/torproject;> https://www.linkedin.com/company/tor-project;> + + https://github.com/torproject;> ___ tor-commits mailing list tor-commits@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits
[tor-commits] [tor/release-0.4.5] 0.4.5 changelog cleanups
commit 10d469a731d4714662b0a06b9e9844af7342f694 Author: Roger Dingledine Date: Mon Oct 25 12:19:00 2021 -0400 0.4.5 changelog cleanups --- ChangeLog| 40 ReleaseNotes | 40 2 files changed, 40 insertions(+), 40 deletions(-) diff --git a/ChangeLog b/ChangeLog index 618da8ee3c..13bc05f610 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,22 +1,22 @@ Changes in version 0.4.5.11 - 2021-10-26 - This version fixes several bugs from earlier versions of Tor. A major - change is that v2 onion service are now disabled at the client, - service and relay meaning that any tor nodes running this version and - onward will stops supporting v2. This is the last step into the long - deprecation process of onion service version 2. Everyone running an - earlier version, whether as a client, a relay, or an onion service, - should upgrade to Tor 0.3.5.17, 0.4.5.11, or 0.4.6.8. + The major change in this version is that v2 onion services are now + disabled at the client, service, and relay: any Tor nodes running this + version and onward will stop supporting v2 onion services. This is the + last step in the long deprecation process of v2 onion services. + Everyone running an earlier version, whether as a client, a relay, or + an onion service, should upgrade to Tor 0.3.5.17, 0.4.5.11, + or 0.4.6.8. o Major feature (onion service v2): - See https://blog.torproject.org/v2-deprecation-timeline for details on how to transition from v2 to v3. -- The control port command HSFETCH and HSPOST don't allow version 2 - as well. It is also not possible to create a v2 service +- The control port commands HSFETCH and HSPOST no longer allow + version 2, and it is no longer possible to create a v2 service with ADD_ONION. -- Tor does NOT allow anymore to create v2 services, to connect as a - client to a v2 service and for a relay to be a v2 HSDir or - introduction point. This effectively disable onion service version - 2 tor wide. Closes 40476. +- Tor no longer allows creating v2 services, or connecting as a + client to a v2 service. Relays will decline to be a v2 HSDir or + introduction point. This effectively disables onion service + version 2 Tor-wide. Closes ticket 40476. o Minor features (bridge, backport from 0.4.6.8): - We now announce the URL to Tor's new bridge status at @@ -24,7 +24,7 @@ Changes in version 0.4.5.11 - 2021-10-26 bridge relay. Closes ticket 30477. o Minor features (fallbackdir): -- Regenerate fallback directories for October 2021. Close +- Regenerate fallback directories for October 2021. Closes ticket 40493. o Minor features (logging, diagnostic, backport from 0.4.6.5): @@ -68,11 +68,11 @@ Changes in version 0.4.5.11 - 2021-10-26 consensus. Fixes bug 40375; bugfix on 0.3.1.1-alpha. o Minor bugfixes (onion service, TROVE-2021-008, backport from 0.4.6.8): -- Only log once any v2 access attempts in order to not pollute the - logs with warnings and avoid recording the times on disk when v2 - access was attempted. Important to note that the onion address was - _never_ logged. That is a Low security issue. Fixes bug 40474; - bugfix on 0.4.5.8. +- Only log v2 access attempts once total, in order to not pollute + the logs with warnings and to avoid recording the times on disk + when v2 access was attempted. Note that the onion address was + _never_ logged. This counts as a Low-severity security issue. + Fixes bug 40474; bugfix on 0.4.5.8. Changes in version 0.4.5.10 - 2021-08-16 @@ -91,7 +91,7 @@ Changes in version 0.4.5.10 - 2021-08-16 CVE-2021-38385. Found by Henry de Valence. o Minor feature (fallbackdir): -- Regenerate fallback directories list. Close ticket 40447. +- Regenerate fallback directories list. Closes ticket 40447. o Minor features (geoip data): - Update the geoip files to match the IPFire Location Database, as diff --git a/ReleaseNotes b/ReleaseNotes index 58f4a9b263..ed07c1703b 100644 --- a/ReleaseNotes +++ b/ReleaseNotes @@ -3,24 +3,24 @@ release of Tor. If you want to see more detailed descriptions of the changes in each development snapshot, see the ChangeLog file. Changes in version 0.4.5.11 - 2021-10-26 - This version fixes several bugs from earlier versions of Tor. A major - change is that v2 onion service are now disabled at the client, - service and relay meaning that any tor nodes running this version and - onward will stops supporting v2. This is the last step into the long - deprecation process of onion service version 2. Everyone running an - earlier version, whether as a client, a relay, or an onion service, - should upgrade to Tor 0.3.5.17, 0.4.5.11, or 0.4.6.8. + The major change in this version is that v2 onion services are now + disabled at the client, service,
[tor-commits] [tor/release-0.3.5] 0.3.5 changelog cleanups
commit 08e4b8d2fcc47a9e2b4666fbdd2f7c27cda5bed6 Author: Roger Dingledine Date: Mon Oct 25 12:06:40 2021 -0400 0.3.5 changelog cleanups --- ChangeLog| 36 ++-- ReleaseNotes | 36 ++-- 2 files changed, 36 insertions(+), 36 deletions(-) diff --git a/ChangeLog b/ChangeLog index d933b5e751..1c1be7149a 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,22 +1,22 @@ Changes in version 0.3.5.17 - 2021-10-26 - This version as a major change which is that v2 onion service are now - disabled at the client, service and relay meaning that any tor nodes - running this version and onward will stops supporting v2. This is the - last step into the long deprecation process of onion service version - 2. Everyone running an earlier version, whether as a client, a relay, - or an onion service, should upgrade to Tor 0.3.5.17, 0.4.5.11, or - 0.4.6.8. + The major change in this version is that v2 onion services are now + disabled at the client, service, and relay: any Tor nodes running this + version and onward will stop supporting v2 onion services. This is the + last step in the long deprecation process of v2 onion services. + Everyone running an earlier version, whether as a client, a relay, or + an onion service, should upgrade to Tor 0.3.5.17, 0.4.5.11, + or 0.4.6.8. o Major feature (onion service v2, backport from 0.4.5.11): - See https://blog.torproject.org/v2-deprecation-timeline for details on how to transition from v2 to v3. -- The control port command HSFETCH and HSPOST don't allow version 2 - as well. It is also not possible to create a v2 service with - ADD_ONION. -- Tor does NOT allow anymore to create v2 services, to connect as a - client to a v2 service and for a relay to be a v2 HSDir or - introduction point. This effectively disable onion service version - 2 tor wide. Closes 40476. +- The control port commands HSFETCH and HSPOST no longer allow + version 2, and it is no longer possible to create a v2 service + with ADD_ONION. +- Tor no longer allows creating v2 services, or connecting as a + client to a v2 service. Relays will decline to be a v2 HSDir or + introduction point. This effectively disables onion service + version 2 Tor-wide. Closes ticket 40476. o Minor features (bridge, backport from 0.4.6.8): - We now announce the URL to Tor's new bridge status at @@ -24,15 +24,15 @@ Changes in version 0.3.5.17 - 2021-10-26 bridge relay. Closes ticket 30477. o Minor features (fallbackdir): -- Regenerate fallback directories for October 2021. Close +- Regenerate fallback directories for October 2021. Closes ticket 40493. o Minor bugfixes (compatibility, backport from 0.4.6.8): - Fix compatibility with the most recent Libevent versions, which no - longer have an evdns_set_random_bytes() function. Because this + longer have an evdns_set_random_bytes() function. Because this function has been a no-op since Libevent 2.0.4-alpha, it is safe - for us to just stop calling it. Fixes bug 40371; bugfix on - 0.2.1.7-alpha. + for us to just stop calling it. Fixes bug 40371; bugfix + on 0.2.1.7-alpha. Changes in version 0.3.5.16 - 2021-08-16 diff --git a/ReleaseNotes b/ReleaseNotes index 4044390c58..5e46554c07 100644 --- a/ReleaseNotes +++ b/ReleaseNotes @@ -3,24 +3,24 @@ release of Tor. If you want to see more detailed descriptions of the changes in each development snapshot, see the ChangeLog file. Changes in version 0.3.5.17 - 2021-10-26 - This version as a major change which is that v2 onion service are now - disabled at the client, service and relay meaning that any tor nodes - running this version and onward will stops supporting v2. This is the - last step into the long deprecation process of onion service version - 2. Everyone running an earlier version, whether as a client, a relay, - or an onion service, should upgrade to Tor 0.3.5.17, 0.4.5.11, or - 0.4.6.8. + The major change in this version is that v2 onion services are now + disabled at the client, service, and relay: any Tor nodes running this + version and onward will stop supporting v2 onion services. This is the + last step in the long deprecation process of v2 onion services. + Everyone running an earlier version, whether as a client, a relay, or + an onion service, should upgrade to Tor 0.3.5.17, 0.4.5.11, + or 0.4.6.8. o Major feature (onion service v2, backport from 0.4.5.11): - See https://blog.torproject.org/v2-deprecation-timeline for details on how to transition from v2 to v3. -- The control port command HSFETCH and HSPOST don't allow version 2 - as well. It is also not possible to create a v2 service with - ADD_ONION. -- Tor does NOT allow anymore to create v2 services, to connect as a - client to a v2 service and for a relay to be a v2
[tor-commits] [tor/main] changelog cleanups for 0.4.7.2-alpha
commit 3e384d7329af0fd64a7b4cedda1ddec307064e65 Author: Roger Dingledine Date: Mon Oct 25 11:53:32 2021 -0400 changelog cleanups for 0.4.7.2-alpha --- ChangeLog | 42 +- 1 file changed, 21 insertions(+), 21 deletions(-) diff --git a/ChangeLog b/ChangeLog index 218e16d003..afc7018fe6 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,12 +1,12 @@ Changes in version 0.4.7.2-alpha - 2021-10-26 - This version is the second alpha release of the 0.4.7.x series. Two - major features were added which are congestion control (prop334) for - network performance and the MiddleOnly flag (prop335) voted by the - authorities used to pin relays to the middle position for various - network health reasons. This version also fixes numerous bugs. + This second alpha release of the 0.4.7.x series adds two major + features: congestion control (prop324) for network performance, and + the MiddleOnly flag (prop335) voted by the authorities to pin relays + to the middle position for various network health reasons. This + release also fixes numerous bugs. The congestion control feature, detailed in proposal 324, still needs - more work before we can enabled it by default. It is currently in its + more work before we can enable it by default. It is currently in its testing and tuning phase which means that you should expect more 0.4.7.x alphas as congestion control gets stabilized and tuned for optimal performance. And so, at this release, it can not be used @@ -54,7 +54,7 @@ Changes in version 0.4.7.2-alpha - 2021-10-26 details on how to transition from v2 to v3. o Minor features (fallbackdir): -- Regenerate fallback directories for October 2021. Close +- Regenerate fallback directories for October 2021. Closes ticket 40493. o Minor features (logging, heartbeat): @@ -90,9 +90,9 @@ Changes in version 0.4.7.2-alpha - 2021-10-26 permitted. Fixes bug 11477; bugfix on 0.2.5.4-alpha. o Minor bugfixes (logging): -- If a channel has never received, transmitted a cell or seen a - client, do not calculate time diffs against 1/1/1970 but log - another prettier message. Fixes bug 40182; bugfix on 0.2.4.4. +- If a channel has never received or transmitted a cell, or seen a + client, do not calculate time diffs against 1/1/1970 but log a + better prettier message. Fixes bug 40182; bugfix on 0.2.4.4. o Minor bugfixes (onion service): - Fix a warning BUG that would occur often on heavily loaded onion @@ -101,18 +101,18 @@ Changes in version 0.4.7.2-alpha - 2021-10-26 o Minor bugfixes (onion service, config): - Fix a memory leak for a small config line string that could occur - if the service failed to be configured from file properly. Fixes - bug 40484; bugfix on 0.3.2.1-alpha. + if the onion service failed to be configured from file properly. + Fixes bug 40484; bugfix on 0.3.2.1-alpha. o Minor bugfixes (onion service, TROVE-2021-008): -- Only log once any v2 access attempts in order to not pollute the - logs with warnings and avoid recording the times on disk when v2 - access was attempted. Important to note that the onion address was - _never_ logged. That is a Low security issue. Fixes bug 40474; - bugfix on 0.4.5.8. +- Only log v2 access attempts once total, in order to not pollute + the logs with warnings and to avoid recording the times on disk + when v2 access was attempted. Note that the onion address was + _never_ logged. This counts as a Low-severity security issue. + Fixes bug 40474; bugfix on 0.4.5.8. - Note that due to #40476 which removes v2 support entirely, this log line is not emitted anymore. We still mention this in the - changelog because it is a low security TROVE. + changelog because it is a Low-severity TROVE. o Minor bugfixes (usability): - Do not log "RENDEZVOUS1 cell with unrecognized rendezvous cookie" @@ -138,11 +138,11 @@ Changes in version 0.4.7.2-alpha - 2021-10-26 o Code simplification and refactoring (rust): - Remove Rust support and its associated code. It is unsupported and - Rust focus should be shifted to arti. Closes 40469. + Rust focus should be shifted to arti. Closes ticket 40469. o Testing (CI, chutney): -- Bump the data size that chutney transmit to 5MB in order to - trigger flow control and congestion window code. Closes +- Bump the data size that chutney transmits to 5MBytes in order to + trigger the flow control and congestion window code. Closes ticket 40485. ___ tor-commits mailing list tor-commits@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits
[tor-commits] [translation/torbutton-torbuttondtd_completed] https://gitweb.torproject.org/translation.git/commit/?h=torbutton-torbuttondtd_completed
commit bf3a57b6caa8119caa68e5cdb31f25a8a1be0368 Author: Translation commit bot Date: Mon Oct 25 15:47:15 2021 + https://gitweb.torproject.org/translation.git/commit/?h=torbutton-torbuttondtd_completed --- fr/torbutton.dtd | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/fr/torbutton.dtd b/fr/torbutton.dtd index 15e96bb417..1c3c6b66bf 100644 --- a/fr/torbutton.dtd +++ b/fr/torbutton.dtd @@ -45,7 +45,7 @@ - + ___ tor-commits mailing list tor-commits@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits
[tor-commits] [translation/torbutton-torbuttondtd] https://gitweb.torproject.org/translation.git/commit/?h=torbutton-torbuttondtd
commit 5675b09fd06c291ff45018ab47f502cdbf6a7bb6 Author: Translation commit bot Date: Mon Oct 25 15:47:13 2021 + https://gitweb.torproject.org/translation.git/commit/?h=torbutton-torbuttondtd --- fr/torbutton.dtd | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/fr/torbutton.dtd b/fr/torbutton.dtd index 52e6c600e7..1c3c6b66bf 100644 --- a/fr/torbutton.dtd +++ b/fr/torbutton.dtd @@ -45,7 +45,7 @@ - + ___ tor-commits mailing list tor-commits@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits
[tor-commits] [translation/fenix-torbrowserstringsxml_completed] https://gitweb.torproject.org/translation.git/commit/?h=fenix-torbrowserstringsxml_completed
commit f334de510ffef6788be9d0ae547ea9eb7dddb55d Author: Translation commit bot Date: Mon Oct 25 15:45:20 2021 + https://gitweb.torproject.org/translation.git/commit/?h=fenix-torbrowserstringsxml_completed --- fr/torbrowser_strings.xml | 5 - 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/fr/torbrowser_strings.xml b/fr/torbrowser_strings.xml index f9b984b6eb..67edad06f7 100644 --- a/fr/torbrowser_strings.xml +++ b/fr/torbrowser_strings.xml @@ -73,4 +73,7 @@ Pour une confidentialité accrue, demander la version anglaise des pages Web. - +Utilisez un masque, utilisez Tor. +Résistez à la pandémie de surveillance. +Votre don sera égalé par les Amis de Tor. + ___ tor-commits mailing list tor-commits@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits
[tor-commits] [translation/abouttor-homepage_completed] https://gitweb.torproject.org/translation.git/commit/?h=abouttor-homepage_completed
commit 9ea39247c689ee34c936f1e49357af2ea41ed90c Author: Translation commit bot Date: Mon Oct 25 15:45:05 2021 + https://gitweb.torproject.org/translation.git/commit/?h=abouttor-homepage_completed --- fr/aboutTor.dtd | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/fr/aboutTor.dtd b/fr/aboutTor.dtd index 82ed7fe280..4b0fbbd854 100644 --- a/fr/aboutTor.dtd +++ b/fr/aboutTor.dtd @@ -47,8 +47,8 @@ Thank you! --> - - + + - + ___ tor-commits mailing list tor-commits@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits
[tor-commits] [translation/abouttor-homepage] https://gitweb.torproject.org/translation.git/commit/?h=abouttor-homepage
commit ab9791be6ac8d6d079c47c25ef9b587aa9115ad1 Author: Translation commit bot Date: Mon Oct 25 15:45:02 2021 + https://gitweb.torproject.org/translation.git/commit/?h=abouttor-homepage --- fr/aboutTor.dtd | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/fr/aboutTor.dtd b/fr/aboutTor.dtd index 77b638e032..4b0fbbd854 100644 --- a/fr/aboutTor.dtd +++ b/fr/aboutTor.dtd @@ -47,7 +47,7 @@ Thank you! --> - +
[tor-commits] [tor/release-0.4.6] Remove already released ChangeLog entry.
commit 546d63e18f37758980381557dc1286a2962b4e0c Author: Alexander Færøy Date: Mon Oct 25 15:23:16 2021 + Remove already released ChangeLog entry. --- ChangeLog | 5 - 1 file changed, 5 deletions(-) diff --git a/ChangeLog b/ChangeLog index a110b80ab4..069efafc87 100644 --- a/ChangeLog +++ b/ChangeLog @@ -13,11 +13,6 @@ Changes in version 0.4.6.8 - 2021-10-26 respectively but they are also controlled by consensus parameters. Fixes bug 40491; bugfix on 0.4.6.1-alpha. - o Minor features (bridge): -- We now announce the URL to Tor's new bridge status at - https://bridges.torproject.org/ when Tor is configured to run as a - bridge relay. Closes ticket 30477. - o Minor features (fallbackdir): - Regenerate fallback directories for October 2021. Close ticket 40493. ___ tor-commits mailing list tor-commits@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits
[tor-commits] [tor/main] Typo: bugfixes -> bugs.
commit e1f93f29cf3a6d23c0e62b37b05239c3c8c83d6d Author: Alexander Færøy Date: Mon Oct 25 15:25:30 2021 + Typo: bugfixes -> bugs. --- ChangeLog | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ChangeLog b/ChangeLog index 6a41c5a3a4..218e16d003 100644 --- a/ChangeLog +++ b/ChangeLog @@ -3,7 +3,7 @@ Changes in version 0.4.7.2-alpha - 2021-10-26 major features were added which are congestion control (prop334) for network performance and the MiddleOnly flag (prop335) voted by the authorities used to pin relays to the middle position for various - network health reasons. This version also fixes numerous bugfixes. + network health reasons. This version also fixes numerous bugs. The congestion control feature, detailed in proposal 324, still needs more work before we can enabled it by default. It is currently in its ___ tor-commits mailing list tor-commits@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits
[tor-commits] [tor/main] Remove already released ChangeLog entry.
commit 0945dbbe520b3516c0e5834bf9c2635968a1ed8d Author: Alexander Færøy Date: Mon Oct 25 15:18:14 2021 + Remove already released ChangeLog entry. --- ChangeLog | 5 - 1 file changed, 5 deletions(-) diff --git a/ChangeLog b/ChangeLog index 6d3d8f8700..6a41c5a3a4 100644 --- a/ChangeLog +++ b/ChangeLog @@ -53,11 +53,6 @@ Changes in version 0.4.7.2-alpha - 2021-10-26 - See https://blog.torproject.org/v2-deprecation-timeline for details on how to transition from v2 to v3. - o Minor features (bridge): -- We now announce the URL to Tor's new bridge status at - https://bridges.torproject.org/ when Tor is configured to run as a - bridge relay. Closes ticket 30477. - o Minor features (fallbackdir): - Regenerate fallback directories for October 2021. Close ticket 40493. ___ tor-commits mailing list tor-commits@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits
[tor-commits] [tor/release-0.4.6] changelog: Changelog for 0.4.6.8
commit 43a711694745cacdfbcb612805bf1f7d8132b486 Author: David Goulet Date: Mon Oct 25 10:43:50 2021 -0400 changelog: Changelog for 0.4.6.8 Signed-off-by: David Goulet --- ChangeLog| 62 ReleaseNotes | 62 2 files changed, 124 insertions(+) diff --git a/ChangeLog b/ChangeLog index 6411324083..a110b80ab4 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,65 @@ +Changes in version 0.4.6.8 - 2021-10-26 + This version fixes several bugs from earlier versions of Tor. Worth + noting is a fix on how we use DNS timeout to report general overload. + Everyone running an earlier version, whether as a client, a relay, or + an onion service, should upgrade to Tor 0.3.5.17, 0.4.5.11, + or 0.4.6.8. + + o Major bugfixes (relay, overload state): +- Report the general overload state for DNS timeout errors only if + X% of all DNS queries over Y seconds are errors. Before that, it + only took 1 timeout to report the overload state which was just + too low of a threshold. The X and Y values are 1% and 10 minutes + respectively but they are also controlled by consensus parameters. + Fixes bug 40491; bugfix on 0.4.6.1-alpha. + + o Minor features (bridge): +- We now announce the URL to Tor's new bridge status at + https://bridges.torproject.org/ when Tor is configured to run as a + bridge relay. Closes ticket 30477. + + o Minor features (fallbackdir): +- Regenerate fallback directories for October 2021. Close + ticket 40493. + + o Minor features (testing): +- On a testing network, relays can now use the + TestingMinTimeToReportBandwidth option to change the smallest + amount of time over which they're willing to report their observed + maximum bandwidth. Previously, this was fixed at 1 day. For + safety, values under 2 hours are only supported on testing + networks. Part of a fix for ticket 40337. +- Relays on testing networks no longer rate-limit how frequently + they are willing to report new bandwidth measurements. Part of a + fix for ticket 40337. +- Relays on testing networks now report their observed bandwidths + immediately from startup. Previously, they waited until they had + been running for a full day. Closes ticket 40337. + + o Minor bugfix (onion service): +- Do not flag an HSDir as non-running in case the descriptor upload + or fetch fails. An onion service closes pending directory + connections before uploading a new descriptor which can thus lead + to wrongly flagging many relays and thus affecting circuit building + path selection. Fixes bug 40434; bugfix on 0.2.0.13-alpha. +- Improve logging when a bad HS version is given. Fixes bug 40476; + bugfix on 0.4.6.1-alpha. + + o Minor bugfixes (compatibility): +- Fix compatibility with the most recent Libevent versions, which no + longer have an evdns_set_random_bytes() function. Because this + function has been a no-op since Libevent 2.0.4-alpha, it is safe + for us to just stop calling it. Fixes bug 40371; bugfix + on 0.2.1.7-alpha. + + o Minor bugfixes (onion service, TROVE-2021-008): +- Only log once any v2 access attempts in order to not pollute the + logs with warnings and avoid recording the times on disk when v2 + access was attempted. Important to note that the onion address was + _never_ logged. That is a Low security issue. Fixes bug 40474; + bugfix on 0.4.5.8. + + Changes in version 0.4.6.7 - 2021-08-16 This version fixes several bugs from earlier versions of Tor, including one that could lead to a denial-of-service attack. Everyone diff --git a/ReleaseNotes b/ReleaseNotes index aa54953aa7..425ee565ad 100644 --- a/ReleaseNotes +++ b/ReleaseNotes @@ -2,6 +2,68 @@ This document summarizes new features and bugfixes in each stable release of Tor. If you want to see more detailed descriptions of the changes in each development snapshot, see the ChangeLog file. +Changes in version 0.4.6.8 - 2021-10-26 + This version fixes several bugs from earlier versions of Tor. Worth + noting is a fix on how we use DNS timeout to report general overload. + Everyone running an earlier version, whether as a client, a relay, or + an onion service, should upgrade to Tor 0.3.5.17, 0.4.5.11, + or 0.4.6.8. + + o Major bugfixes (relay, overload state): +- Report the general overload state for DNS timeout errors only if + X% of all DNS queries over Y seconds are errors. Before that, it + only took 1 timeout to report the overload state which was just + too low of a threshold. The X and Y values are 1% and 10 minutes + respectively but they are also controlled by consensus parameters. + Fixes bug 40491; bugfix on 0.4.6.1-alpha. + + o Minor features (bridge): +- We now announce the URL to Tor's
[tor-commits] [tor/release-0.3.5] changelog: Changelog for 0.3.5.17
commit 5aa7bd43080ffeb020944b2c0b1bc184c44f860b Author: David Goulet Date: Mon Oct 25 10:43:33 2021 -0400 changelog: Changelog for 0.3.5.17 Signed-off-by: David Goulet --- ChangeLog| 37 + ReleaseNotes | 37 + changes/bug40371 | 6 -- changes/ticket30477 | 4 changes/ticket40476 | 8 changes/ticket40493 | 2 -- scripts/maint/sortChanges.py | 10 +- 7 files changed, 79 insertions(+), 25 deletions(-) diff --git a/ChangeLog b/ChangeLog index ba5bb7ed53..d933b5e751 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,40 @@ +Changes in version 0.3.5.17 - 2021-10-26 + This version as a major change which is that v2 onion service are now + disabled at the client, service and relay meaning that any tor nodes + running this version and onward will stops supporting v2. This is the + last step into the long deprecation process of onion service version + 2. Everyone running an earlier version, whether as a client, a relay, + or an onion service, should upgrade to Tor 0.3.5.17, 0.4.5.11, or + 0.4.6.8. + + o Major feature (onion service v2, backport from 0.4.5.11): +- See https://blog.torproject.org/v2-deprecation-timeline for + details on how to transition from v2 to v3. +- The control port command HSFETCH and HSPOST don't allow version 2 + as well. It is also not possible to create a v2 service with + ADD_ONION. +- Tor does NOT allow anymore to create v2 services, to connect as a + client to a v2 service and for a relay to be a v2 HSDir or + introduction point. This effectively disable onion service version + 2 tor wide. Closes 40476. + + o Minor features (bridge, backport from 0.4.6.8): +- We now announce the URL to Tor's new bridge status at + https://bridges.torproject.org/ when Tor is configured to run as a + bridge relay. Closes ticket 30477. + + o Minor features (fallbackdir): +- Regenerate fallback directories for October 2021. Close + ticket 40493. + + o Minor bugfixes (compatibility, backport from 0.4.6.8): +- Fix compatibility with the most recent Libevent versions, which no + longer have an evdns_set_random_bytes() function. Because this + function has been a no-op since Libevent 2.0.4-alpha, it is safe + for us to just stop calling it. Fixes bug 40371; bugfix on + 0.2.1.7-alpha. + + Changes in version 0.3.5.16 - 2021-08-16 This version fixes several bugs from earlier versions of Tor, including one that could lead to a denial-of-service attack. Everyone diff --git a/ReleaseNotes b/ReleaseNotes index 77b9047761..4044390c58 100644 --- a/ReleaseNotes +++ b/ReleaseNotes @@ -2,6 +2,43 @@ This document summarizes new features and bugfixes in each stable release of Tor. If you want to see more detailed descriptions of the changes in each development snapshot, see the ChangeLog file. +Changes in version 0.3.5.17 - 2021-10-26 + This version as a major change which is that v2 onion service are now + disabled at the client, service and relay meaning that any tor nodes + running this version and onward will stops supporting v2. This is the + last step into the long deprecation process of onion service version + 2. Everyone running an earlier version, whether as a client, a relay, + or an onion service, should upgrade to Tor 0.3.5.17, 0.4.5.11, or + 0.4.6.8. + + o Major feature (onion service v2, backport from 0.4.5.11): +- See https://blog.torproject.org/v2-deprecation-timeline for + details on how to transition from v2 to v3. +- The control port command HSFETCH and HSPOST don't allow version 2 + as well. It is also not possible to create a v2 service with + ADD_ONION. +- Tor does NOT allow anymore to create v2 services, to connect as a + client to a v2 service and for a relay to be a v2 HSDir or + introduction point. This effectively disable onion service version + 2 tor wide. Closes 40476. + + o Minor features (bridge, backport from 0.4.6.8): +- We now announce the URL to Tor's new bridge status at + https://bridges.torproject.org/ when Tor is configured to run as a + bridge relay. Closes ticket 30477. + + o Minor features (fallbackdir): +- Regenerate fallback directories for October 2021. Close + ticket 40493. + + o Minor bugfixes (compatibility, backport from 0.4.6.8): +- Fix compatibility with the most recent Libevent versions, which no + longer have an evdns_set_random_bytes() function. Because this + function has been a no-op since Libevent 2.0.4-alpha, it is safe + for us to just stop calling it. Fixes bug 40371; bugfix on + 0.2.1.7-alpha. + + Changes in version 0.3.5.16 - 2021-08-16 This version fixes several bugs from earlier versions of Tor, including one that could lead to a denial-of-service
[tor-commits] [tor/release-0.4.5] changelog: Changelog for 0.4.5.11
commit 0c9e27ddbef4c9f46b45c76d5c829f87ade740b7 Author: David Goulet Date: Mon Oct 25 10:43:42 2021 -0400 changelog: Changelog for 0.4.5.11 Signed-off-by: David Goulet --- ChangeLog | 77 + ReleaseNotes| 77 + changes/bug40175| 5 changes/bug40371| 6 - changes/bug40375| 5 changes/ticket30477 | 4 --- changes/ticket40337 | 16 --- changes/ticket40434 | 6 - changes/ticket40474 | 5 changes/ticket40476 | 8 -- changes/ticket40493 | 2 -- 11 files changed, 154 insertions(+), 57 deletions(-) diff --git a/ChangeLog b/ChangeLog index c60d9fa7b2..618da8ee3c 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,80 @@ +Changes in version 0.4.5.11 - 2021-10-26 + This version fixes several bugs from earlier versions of Tor. A major + change is that v2 onion service are now disabled at the client, + service and relay meaning that any tor nodes running this version and + onward will stops supporting v2. This is the last step into the long + deprecation process of onion service version 2. Everyone running an + earlier version, whether as a client, a relay, or an onion service, + should upgrade to Tor 0.3.5.17, 0.4.5.11, or 0.4.6.8. + + o Major feature (onion service v2): +- See https://blog.torproject.org/v2-deprecation-timeline for + details on how to transition from v2 to v3. +- The control port command HSFETCH and HSPOST don't allow version 2 + as well. It is also not possible to create a v2 service + with ADD_ONION. +- Tor does NOT allow anymore to create v2 services, to connect as a + client to a v2 service and for a relay to be a v2 HSDir or + introduction point. This effectively disable onion service version + 2 tor wide. Closes 40476. + + o Minor features (bridge, backport from 0.4.6.8): +- We now announce the URL to Tor's new bridge status at + https://bridges.torproject.org/ when Tor is configured to run as a + bridge relay. Closes ticket 30477. + + o Minor features (fallbackdir): +- Regenerate fallback directories for October 2021. Close + ticket 40493. + + o Minor features (logging, diagnostic, backport from 0.4.6.5): +- Log decompression failures at a higher severity level, since they + can help provide missing context for other warning messages. We + rate-limit these messages, to avoid flooding the logs if they + begin to occur frequently. Closes ticket 40175. + + o Minor features (testing, backport from 0.4.6.8): +- On a testing network, relays can now use the + TestingMinTimeToReportBandwidth option to change the smallest + amount of time over which they're willing to report their observed + maximum bandwidth. Previously, this was fixed at 1 day. For + safety, values under 2 hours are only supported on testing + networks. Part of a fix for ticket 40337. +- Relays on testing networks no longer rate-limit how frequently + they are willing to report new bandwidth measurements. Part of a + fix for ticket 40337. +- Relays on testing networks now report their observed bandwidths + immediately from startup. Previously, they waited until they had + been running for a full day. Closes ticket 40337. + + o Minor bugfix (onion service, backport from 0.4.6.8): +- Do not flag an HSDir as non-running in case the descriptor upload + or fetch fails. An onion service closes pending directory + connections before uploading a new descriptor which can thus lead + to wrongly flagging many relays and thus affecting circuit building + path selection. Fixes bug 40434; bugfix on 0.2.0.13-alpha. + + o Minor bugfixes (compatibility, backport from 0.4.6.8): +- Fix compatibility with the most recent Libevent versions, which no + longer have an evdns_set_random_bytes() function. Because this + function has been a no-op since Libevent 2.0.4-alpha, it is safe + for us to just stop calling it. Fixes bug 40371; bugfix + on 0.2.1.7-alpha. + + o Minor bugfixes (consensus handling, backport from 0.4.6.4-rc): +- Avoid a set of bugs that could be caused by inconsistently + preferring an out-of-date consensus stored in a stale directory + cache over a more recent one stored on disk as the latest + consensus. Fixes bug 40375; bugfix on 0.3.1.1-alpha. + + o Minor bugfixes (onion service, TROVE-2021-008, backport from 0.4.6.8): +- Only log once any v2 access attempts in order to not pollute the + logs with warnings and avoid recording the times on disk when v2 + access was attempted. Important to note that the onion address was + _never_ logged. That is a Low security issue. Fixes bug 40474; + bugfix on 0.4.5.8. + + Changes in version 0.4.5.10 - 2021-08-16 This version fixes several bugs from earlier
[tor-commits] [tor/main] changelog: ChangeLog for 0.4.7.2-alpha release
commit 78f5c96272bba39a9bd43944e588ced4728266ae
Author: David Goulet
Date: Mon Oct 25 10:13:46 2021 -0400
changelog: ChangeLog for 0.4.7.2-alpha release
Signed-off-by: David Goulet
---
ChangeLog | 153 +
changes/bug40400 | 6 --
changes/bug40400_part2 | 5 --
changes/bug40400_part3 | 7 ---
changes/bug40465 | 3 -
changes/bug40471 | 4 --
changes/bug40486 | 5 --
changes/bug40488 | 4 --
changes/issue11477 | 8 ---
changes/issue16803 | 2 -
changes/prop335| 11
changes/ticket30477| 4 --
changes/ticket34083| 5 --
changes/ticket40182| 4 --
changes/ticket40450| 3 -
changes/ticket40469| 4 --
changes/ticket40474| 5 --
changes/ticket40476| 7 ---
changes/ticket40480| 3 -
changes/ticket40484| 5 --
changes/ticket40485| 3 -
changes/ticket40490| 5 --
changes/ticket40491| 7 ---
changes/ticket40493| 2 -
24 files changed, 153 insertions(+), 112 deletions(-)
diff --git a/ChangeLog b/ChangeLog
index 2340716696..6d3d8f8700 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,156 @@
+Changes in version 0.4.7.2-alpha - 2021-10-26
+ This version is the second alpha release of the 0.4.7.x series. Two
+ major features were added which are congestion control (prop334) for
+ network performance and the MiddleOnly flag (prop335) voted by the
+ authorities used to pin relays to the middle position for various
+ network health reasons. This version also fixes numerous bugfixes.
+
+ The congestion control feature, detailed in proposal 324, still needs
+ more work before we can enabled it by default. It is currently in its
+ testing and tuning phase which means that you should expect more
+ 0.4.7.x alphas as congestion control gets stabilized and tuned for
+ optimal performance. And so, at this release, it can not be used
+ without a custom patch.
+
+ o Major features (congestion control):
+- Implement support for flow control over congestion controlled
+ circuits. This work comes from proposal 324. Closes ticket 40450.
+
+ o Major features (directory authority):
+- Add a new consensus method to handle MiddleOnly specially. When
+ enough authorities are using this method, then any relay tagged
+ with the MiddleOnly flag will have its Exit, Guard, HSDir, and
+ V2Dir flags automatically cleared, and will have its BadExit flag
+ automatically set. Implements part of proposal 335.
+- Authorities can now be configured to label relays as "MiddleOnly".
+ When voting for this flag, authorities automatically vote against
+ Exit, Guard, HSDir, and V2Dir; and in favor of BadExit. Implements
+ part of proposal 335. Based on a patch from Neel Chauhan.
+
+ o Major bugfix (relay, metrics):
+- On the MetricsPort, the DNS error statistics are not reported by
+ record type ("record=...") anymore due to a libevent bug
+ (https://github.com/libevent/libevent/issues/1219). Fixes bug
+ 40490; bugfix on 0.4.7.1-alpha.
+
+ o Major bugfixes (relay, overload state):
+- Report the general overload state for DNS timeout errors only if
+ X% of all DNS queries over Y seconds are errors. Before that, it
+ only took 1 timeout to report the overload state which was just
+ too low of a threshold. The X and Y values are 1% and 10 minutes
+ respectively but they are also controlled by consensus parameters.
+ Fixes bug 40491; bugfix on 0.4.6.1-alpha.
+
+ o Minor feature (authority, relay):
+- Reject End-Of-Life relays running version 0.4.2.x, 0.4.3.x,
+ 0.4.4.x and 0.4.5 alphas/rc. Closes ticket 40480.
+
+ o Minor feature (onion service v2):
+- Onion service v2 addresses are now not recognized anymore by tor
+ meaning a bad hostname is returned when attempting to pass it on a
+ SOCKS connection. No more deprecation log is emitted client side.
+ Closes ticket 40476.
+- See https://blog.torproject.org/v2-deprecation-timeline for
+ details on how to transition from v2 to v3.
+
+ o Minor features (bridge):
+- We now announce the URL to Tor's new bridge status at
+ https://bridges.torproject.org/ when Tor is configured to run as a
+ bridge relay. Closes ticket 30477.
+
+ o Minor features (fallbackdir):
+- Regenerate fallback directories for October 2021. Close
+ ticket 40493.
+
+ o Minor features (logging, heartbeat):
+- When a relay receives a cell that isn't encrypted properly for it,
+ but the relay is the last hop on the circuit, the relay now counts
+ how many cells of this kind it receives, on how many circuits, and
+ reports this information in the log. Previously, we'd log each
+ cell at PROTOCOL_WARN level, which is far too verbose to be
+ useful. Fixes part of ticket 40400.
+
+ o Minor features (testing):
+- We now have
[tor-commits] [community/master] Add backslashes to the /etc/login.conf snippet
commit 6397c477fa080d74b4e747eed0e148f46830e80b Author: Douglas Silva Date: Sun Oct 24 14:16:26 2021 -0300 Add backslashes to the /etc/login.conf snippet --- content/relay/setup/guard/openbsd/contents.lr | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/relay/setup/guard/openbsd/contents.lr b/content/relay/setup/guard/openbsd/contents.lr index 232a2fe..d7cc1ce 100644 --- a/content/relay/setup/guard/openbsd/contents.lr +++ b/content/relay/setup/guard/openbsd/contents.lr @@ -59,8 +59,8 @@ By default, OpenBSD maintains a rather low limit on the maximum number of open f Append the following section to `/etc/login.conf`: ``` -tor: -:openfiles-max=13500: +tor:\ +:openfiles-max=13500:\ :tc=daemon: ``` ___ tor-commits mailing list tor-commits@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits
[tor-commits] [translation/tbmanual-contentspot] https://gitweb.torproject.org/translation.git/commit/?h=tbmanual-contentspot
commit bf385208c72e77e62a78f960f8af2b2643224e29 Author: Translation commit bot Date: Mon Oct 25 12:46:56 2021 + https://gitweb.torproject.org/translation.git/commit/?h=tbmanual-contentspot --- contents+pt-PT.po | 19 ++- 1 file changed, 10 insertions(+), 9 deletions(-) diff --git a/contents+pt-PT.po b/contents+pt-PT.po index aab12d9ed2..3217f0f51d 100644 --- a/contents+pt-PT.po +++ b/contents+pt-PT.po @@ -8,6 +8,7 @@ # Hugo Costa , 2021 # Rui , 2021 # Manuela Silva , 2021 +# Gonçalo Gonçalves, 2021 # msgid "" msgstr "" @@ -15,7 +16,7 @@ msgstr "" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2021-10-07 17:29+CET\n" "PO-Revision-Date: 2018-11-14 12:31+\n" -"Last-Translator: Manuela Silva , 2021\n" +"Last-Translator: Gonçalo Gonçalves, 2021\n" "Language-Team: Portuguese (Portugal) (https://www.transifex.com/otf/teams/1519/pt_PT/)\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" @@ -147,7 +148,7 @@ msgstr "Desinstalação" #: https//tb-manual.torproject.org/known-issues/ #: (content/known-issues/contents+en.lrtopic.description) msgid "Known Issues" -msgstr "" +msgstr "Problemas conhecidos" #: https//tb-manual.torproject.org/menu/ #: (content/menu/contents+en.lrtopic.body) @@ -419,7 +420,7 @@ msgstr "Instalar o Tor Browser" #: https//tb-manual.torproject.org/installation/ #: (content/installation/contents+en.lrtopic.body) msgid "## For Windows" -msgstr "" +msgstr "## Para Windows" #: https//tb-manual.torproject.org/installation/ #: (content/installation/contents+en.lrtopic.body) @@ -433,7 +434,7 @@ msgstr "" #: https//tb-manual.torproject.org/installation/ #: (content/installation/contents+en.lrtopic.body) msgid "2. Download the Windows `.exe` file." -msgstr "" +msgstr "2. Transfira o ficheiro `.exe` do Windows." #: https//tb-manual.torproject.org/installation/ #: (content/installation/contents+en.lrtopic.body) @@ -456,12 +457,12 @@ msgstr "" #: https//tb-manual.torproject.org/installation/ #: (content/installation/contents+en.lrtopic.body) msgid "## For macOS" -msgstr "" +msgstr "## Para o macOS" #: https//tb-manual.torproject.org/installation/ #: (content/installation/contents+en.lrtopic.body) msgid "2. Download the macOS `.dmg` file." -msgstr "" +msgstr "2. Transfira o ficheiro `.dmg` do macOS." #: https//tb-manual.torproject.org/installation/ #: (content/installation/contents+en.lrtopic.body) @@ -475,12 +476,12 @@ msgstr "" #: https//tb-manual.torproject.org/installation/ #: (content/installation/contents+en.lrtopic.body) msgid "## For GNU/Linux" -msgstr "" +msgstr "## Para o GNU/Linux" #: https//tb-manual.torproject.org/installation/ #: (content/installation/contents+en.lrtopic.body) msgid "2. Download the GNU/Linux `.tar.xz` file." -msgstr "" +msgstr "2. Transfira o ficheiro `.tar.xz` do GNU/Linux." #: https//tb-manual.torproject.org/installation/ #: (content/installation/contents+en.lrtopic.body) @@ -490,7 +491,7 @@ msgstr "" #: https//tb-manual.torproject.org/installation/ #: (content/installation/contents+en.lrtopic.body) msgid " Graphical method" -msgstr "" +msgstr " Método gráfico" #: https//tb-manual.torproject.org/installation/ #: (content/installation/contents+en.lrtopic.body) ___ tor-commits mailing list tor-commits@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits
[tor-commits] [translation/support-portal] https://gitweb.torproject.org/translation.git/commit/?h=support-portal
commit c13726e89d03878cd00b72eab021a73403ffc7dd Author: Translation commit bot Date: Mon Oct 25 11:17:55 2021 + https://gitweb.torproject.org/translation.git/commit/?h=support-portal --- contents+ar.po | 16 1 file changed, 12 insertions(+), 4 deletions(-) diff --git a/contents+ar.po b/contents+ar.po index 0ebd10019b..93168aa73e 100644 --- a/contents+ar.po +++ b/contents+ar.po @@ -8757,6 +8757,9 @@ msgid "" "short-lived proxies on their regular browsers. Check, [how can I use " "Snowflake?](../how-can-i-use-snowflake/)" msgstr "" +"ÙÙ ÙÙ ÙÙ٠تطÙعÙ٠اÙراغبÙÙ Ù٠٠ساعدة اÙ٠ستخد٠Ù٠عÙ٠اÙشبÙات اÙخاضعة ÙÙرÙابة Ø£Ù " +"ÙساعدÙا Ù Ù Ø®Ùا٠تدÙÙر اÙبرÙÙسÙات ÙصÙرة اÙع٠ر عÙ٠٠تصÙØاتÙ٠اÙعادÙØ©. تØÙÙØ " +"[ÙÙÙ ÙÙ ÙÙÙ٠استخدا٠SnowflakeØ](../ how-can-i-use-snowflake /)" #: https//support.torproject.org/censorship/what-is-snowflake/ #: (content/censorship/what-is-snowflake/contents+en.lrquestion.description) @@ -8765,6 +8768,9 @@ msgid "" "fronting/) technique to make a connection to one of the thousands of " "snowflake proxies run by volunteers." msgstr "" +"Ùستخد٠Snowflake تÙÙÙØ© [domain-fronting](../../ glossary/domain-fronting /) " +"عاÙÙØ© اÙÙعاÙÙØ© ÙØ¥Ùشاء اتصا٠بÙاØد ٠٠آÙا٠اÙبرÙÙسÙات ÙدÙØ© اÙØ«Ùج اÙت٠ÙدÙرÙا " +"٠تطÙعÙÙ." #: https//support.torproject.org/censorship/what-is-snowflake/ #: (content/censorship/what-is-snowflake/contents+en.lrquestion.description) @@ -9176,7 +9182,7 @@ msgstr "باÙÙسبة Ù٠عظ٠اÙ٠ستخد٠ÙÙ Ø ÙعتÙد Ø£ÙÙا Ø® #: https//support.torproject.org/relay-operators/change-bridge-distribution/ #: (content/relay-operators/change-bridge-distribution/contents+en.lrquestion.title) msgid "How do I change my bridge distribution method?" -msgstr "" +msgstr "ÙÙ٠أÙÙ٠بتغÙÙر طرÙÙØ© تÙزÙع اÙجسر اÙخاصة بÙØ" #: https//support.torproject.org/relay-operators/change-bridge-distribution/ #: (content/relay-operators/change-bridge-distribution/contents+en.lrquestion.description) @@ -9201,7 +9207,7 @@ msgstr "" #: https//support.torproject.org/relay-operators/change-bridge-distribution/ #: (content/relay-operators/change-bridge-distribution/contents+en.lrquestion.description) msgid "Operators can also choose which distribution method their bridge uses." -msgstr "" +msgstr "ÙÙ ÙÙ ÙÙ٠شغÙÙ٠أÙضÙا اختÙار طرÙÙØ© اÙتÙزÙع اÙت٠Ùستخد٠Ùا اÙجسر." #: https//support.torproject.org/relay-operators/change-bridge-distribution/ #: (content/relay-operators/change-bridge-distribution/contents+en.lrquestion.description) @@ -10396,11 +10402,13 @@ msgid "" "Sets the amount of time the resolver will wait for a response from a " "remote" msgstr "" +"Ùضبط Ù Ùدار اÙÙÙت اÙذ٠سÙÙتظر٠اÙÙ ØÙÙ ÙÙØصÙ٠عÙ٠استجابة ٠٠جÙاز اÙتØÙ٠ع٠" +"بÙعد" #: https//support.torproject.org/relay-operators/relay-bridge-overloaded/ #: (content/relay-operators/relay-bridge-overloaded/contents+en.lrquestion.description) msgid "name server before retrying the query via a different name server." -msgstr "" +msgstr "Ùب٠إعادة Ù ØاÙÙØ© اÙاستعÙا٠عبر خاد٠أس٠اء ٠ختÙÙ." #: https//support.torproject.org/relay-operators/relay-bridge-overloaded/ #: (content/relay-operators/relay-bridge-overloaded/contents+en.lrquestion.description) @@ -10412,7 +10420,7 @@ msgstr "" #: https//support.torproject.org/relay-operators/relay-bridge-overloaded/ #: (content/relay-operators/relay-bridge-overloaded/contents+en.lrquestion.description) msgid "that a single resolver API call maps to a single timeout." -msgstr "" +msgstr "أ٠استدعاء API ÙÙØدة اÙØ٠اÙÙردÙØ© Ùت٠تعÙÙÙ٠إÙÙ Ù ÙÙØ© ÙاØدة." #: https//support.torproject.org/relay-operators/relay-bridge-overloaded/ #: (content/relay-operators/relay-bridge-overloaded/contents+en.lrquestion.description) ___ tor-commits mailing list tor-commits@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits
[tor-commits] [translation/support-portal] https://gitweb.torproject.org/translation.git/commit/?h=support-portal
commit 9d786db272ac6c07872085a2ff4b8cd800a8502e Author: Translation commit bot Date: Mon Oct 25 10:47:55 2021 + https://gitweb.torproject.org/translation.git/commit/?h=support-portal --- contents+ar.po | 37 +++-- 1 file changed, 35 insertions(+), 2 deletions(-) diff --git a/contents+ar.po b/contents+ar.po index cfaa7d4169..0ebd10019b 100644 --- a/contents+ar.po +++ b/contents+ar.po @@ -610,6 +610,8 @@ msgid "" "Fore more information see this [blogpost about domain " "fronting](https://blog.torproject.org/domain-fronting-critical-open-web)." msgstr "" +"Ù٠زÙد ٠٠اÙ٠عÙÙÙ Ø§ØªØ Ø±Ø§Ø¬Ø¹ Ùذا [Ù ÙØ´Ùر ٠دÙÙØ© ØÙÙ ÙاجÙØ© " +"اÙ٠جاÙ](https://blog.torproject.org/domain-fronting-critical-open-web)." #: https//support.torproject.org/glossary/domain-fronting/ #: (content/glossary/domain-fronting/contents+en.lrword.spelling) @@ -3878,6 +3880,8 @@ msgid "" "When we distribute the source code or a package, we digitally sign it with " "[GNU Privacy Guard](https://www.gnupg.org/)." msgstr "" +"عÙد٠ا ÙÙزع اÙÙÙد اÙ٠صدر٠أ٠اÙØØ²Ù Ø©Ø ÙØ¥ÙÙا ÙÙÙعÙا رÙÙ ÙÙا باستخدا٠[Øارس " +"خصÙصÙØ© جÙÙ](https://www.gnupg.org/)." #: https//support.torproject.org/about/key-management/ #: (content/about/key-management/contents+en.lrquestion.description) @@ -3885,6 +3889,8 @@ msgid "" "See the [instructions on how to check Tor Browser's signature](../../tbb" "/how-to-verify-signature/)." msgstr "" +"راجع [اÙتعÙÙ٠ات اÙخاصة بÙÙÙÙØ© اÙتØÙ٠٠٠تÙÙÙع ٠تصÙØ Tor](../../tbb/how-to-" +"verify-signature/)." #: https//support.torproject.org/about/key-management/ #: (content/about/key-management/contents+en.lrquestion.description) @@ -8357,7 +8363,7 @@ msgstr "" #: (content/censorship/connecting-from-china/contents+en.lrquestion.description) msgid "" "Therefore, the second step will be to obtain a bridge that works in China." -msgstr "" +msgstr "ÙØ°ÙÙ, Ùإ٠اÙخطÙØ© اÙثاÙÙØ© ستÙÙ٠اÙØصÙ٠عÙ٠جسر Ùع٠٠Ù٠اÙصÙÙ." #: https//support.torproject.org/censorship/connecting-from-china/ #: (content/censorship/connecting-from-china/contents+en.lrquestion.description) @@ -8370,11 +8376,13 @@ msgid "" "1. **[Snowflake](../what-is-snowflake/):** uses ephemeral proxies to connect" " to the Tor network." msgstr "" +"1. **[ÙدÙØ© اÙØ«Ùج](../what-is-snowflake/):** Ùستخد٠ÙÙÙاء سرÙع اÙزÙا٠ÙÙاتصاÙ" +" بشبÙØ© Tor." #: https//support.torproject.org/censorship/connecting-from-china/ #: (content/censorship/connecting-from-china/contents+en.lrquestion.description) msgid "It's available in Tor Browser stable version (Desktop and Android)." -msgstr "" +msgstr "Ø¥Ù٠٠تÙÙر Ù٠إصدار ٠ستÙر ٠٠٠تصÙØ Tor (Desktop and Android)." #: https//support.torproject.org/censorship/connecting-from-china/ #: (content/censorship/connecting-from-china/contents+en.lrquestion.description) @@ -8382,6 +8390,8 @@ msgid "" "You can select Snowflake from Tor Browser's [built-in bridge dropdown" "](../how-can-i-use-snowflake/)." msgstr "" +"ÙÙ ÙÙ٠تØدÙد Snowflake ٠٠٠تصÙØ Tor [اÙÙائ٠ة اÙÙ ÙسدÙØ© ÙÙجسر اÙ٠د٠ج](../how-" +"can-i-use-snowflake/)." #: https//support.torproject.org/censorship/connecting-from-china/ #: (content/censorship/connecting-from-china/contents+en.lrquestion.description) @@ -8394,6 +8404,11 @@ msgid "" "bridge](https://community.torproject.org/relay/setup/bridge/) from outside " "China." msgstr "" +"1. ** جسÙر obfs4 اÙخاصة ÙغÙر اÙ٠درجة: ** سÙØتاج اÙ٠ستخد٠Ù٠إÙÙ Ø·Ùب جسر خاص " +"Ø¥ÙÙ [frontd...@torproject.org](mailto: frontd...@torproject.org) ٠ع عبارة " +"\"جسر خاص\" ÙÙ Ù ÙضÙع اÙبرÙد اÙØ¥ÙÙترÙÙ٠أÙØ Ø¥Ø°Ø§ ÙاÙÙا خبراء Ù٠اÙتÙÙÙÙÙجÙØ§Ø " +"ÙÙ ÙÙÙ٠تشغÙÙ [جسر obfs4] " +"(https://community.torproject.org/relay/setup/bridge/) ٠٠خارج اÙصÙÙ." #: https//support.torproject.org/censorship/connecting-from-china/ #: (content/censorship/connecting-from-china/contents+en.lrquestion.description) @@ -8402,6 +8417,9 @@ msgid "" "([HTTPS](https://bridges.torproject.org), email), and built-in obfs4 bridges" " bundled in Tor Browser most likely won't work." msgstr "" +"٠٠اÙÙ ÙÙ Ù ÙاØظة أ٠اÙجسÙر اÙÙ Ùزعة بÙاسطة BridgeDB " +"([HTTPS](https://bridges.torproject.org) ÙاÙبرÙد اÙØ¥ÙÙترÙÙÙ) ÙجسÙر obfs4 " +"اÙ٠د٠جة اÙ٠ج٠عة Ù٠٠تصÙØ Tor Ù٠تع٠٠عÙ٠اÙأرجØ." #: https//support.torproject.org/censorship/connecting-from-china/ #: (content/censorship/connecting-from-china/contents+en.lrquestion.description) @@ -8409,6 +8427,8 @@ msgid "" "1. **meek-azure:** it looks like you are browsing a
[tor-commits] [translation/gettor-website-contentspot] https://gitweb.torproject.org/translation.git/commit/?h=gettor-website-contentspot
commit 6b1b5c9988e5096309a74273acff823dc8c595dd Author: Translation commit bot Date: Mon Oct 25 09:15:26 2021 + https://gitweb.torproject.org/translation.git/commit/?h=gettor-website-contentspot --- contents+tr.po | 7 +-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/contents+tr.po b/contents+tr.po index 428828ba5b..6b583fcdaf 100644 --- a/contents+tr.po +++ b/contents+tr.po @@ -1,9 +1,9 @@ # # Translators: -# Kaya Zeren , 2021 # erinm, 2021 # Emma Peel, 2021 # dersteppenwolfx, 2021 +# Kaya Zeren , 2021 # msgid "" msgstr "" @@ -11,7 +11,7 @@ msgstr "" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2021-10-22 09:52+CET\n" "PO-Revision-Date: 2021-03-24 14:33+\n" -"Last-Translator: dersteppenwolfx, 2021\n" +"Last-Translator: Kaya Zeren , 2021\n" "Language-Team: Turkish (https://www.transifex.com/otf/teams/1519/tr/)\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" @@ -184,6 +184,9 @@ msgid "" "bridge.' Click on the drop-down menu and select the pluggable transport " "you'd like to use." msgstr "" +"'Köprüler' bölümünden 'Bir köprü kullanılsın' seçeneÄine tıklayın ve 'Hazır " +"köprülerden seçilsin' seçeneÄini iÅaretleyin. Yandaki açılan kutuya " +"tıklayarak kullanmak istediÄiniz deÄiÅtirilebilir taÅıyıcıyı seçin." #: https//gettor.torproject.org/ (content/contents+en.lrpage.body) msgid "Click 'OK' to save your settings." ___ tor-commits mailing list tor-commits@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits
