tor-commits June 2021

tor-commits@lists.torproject.org

17 participants
1287 discussions

[community/master] Updated content in technicalSetup/bridge
by emmapeel＠torproject.org 29 Jun '21

29 Jun '21

commit 500137c61c3ea17b3713da6d44bef5332e7401d6 Author: Udoka <udokakuugochukwu(a)gmail.com> Date: Fri Apr 23 18:32:32 2021 +0100 Updated content in technicalSetup/bridge Updated content in technicalSetup/bridge Updated content in technicalSetup/bridge --- .../setup/bridge/centos-rhel-opensuse/contents.lr | 48 ++++++++++----------- .../relay/setup/bridge/debian-ubuntu/contents.lr | 4 +- content/relay/setup/bridge/docker/contents.lr | 16 ++----- .../relay/setup/bridge/dragonflybsd/contents.lr | 49 ++++++++++------------ content/relay/setup/bridge/fedora/contents.lr | 16 +++---- content/relay/setup/bridge/freebsd/contents.lr | 22 ++++------ content/relay/setup/bridge/netbsd/contents.lr | 22 ++++------ content/relay/setup/bridge/openbsd/contents.lr | 20 ++++----- content/relay/setup/bridge/windows/contents.lr | 2 +- 9 files changed, 82 insertions(+), 117 deletions(-) diff --git a/content/relay/setup/bridge/centos-rhel-opensuse/contents.lr b/content/relay/setup/bridge/centos-rhel-opensuse/contents.lr index f31d12e..8a75476 100644 --- a/content/relay/setup/bridge/centos-rhel-opensuse/contents.lr +++ b/content/relay/setup/bridge/centos-rhel-opensuse/contents.lr @@ -6,13 +6,11 @@ title: CentOS / RHEL / OpenSUSE --- body: -### 1. Install tor and dependencies +### 1. Install Tor and dependencies * CentOS / RHEL: -``` -yum install epel-release -y -``` +`# yum install epel-release -y` Then add the following to the `/etc/yum.repos.d/tor.repo` file. @@ -27,15 +25,11 @@ cost=100 ``` And then install the following packages. -``` -yum install git golang tor policycoreutils-python-utils -``` +`# yum install git golang tor policycoreutils-python-utils` * OpenSUSE: -``` -zypper install tor go git -``` +`# zypper install tor go git` ### 2. Build obfs4proxy and move it into place. @@ -43,20 +37,21 @@ Heavily outdated versions of git can make `go get` fail, so try upgrading to a m * CentOS / RHEL: -``` -export GOPATH=`mktemp -d` -go get gitlab.com/yawning/obfs4.git/obfs4proxy -sudo cp $GOPATH/bin/obfs4proxy /usr/local/bin/ -chcon --reference=/usr/bin/tor /usr/local/bin/obfs4proxy -``` +`export GOPATH='mktemp -d'` + +`go get gitlab.com/yawning/obfs4.git/obfs4proxy` + +`sudo cp $GOPATH/bin/obfs4proxy /usr/local/bin/` + +`# chcon --reference=/usr/bin/tor /usr/local/bin/obfs4proxy` * OpenSUSE: -``` -export GOPATH=`mktemp -d` -go get gitlab.com/yawning/obfs4.git/obfs4proxy -sudo cp $GOPATH/bin/obfs4proxy /usr/local/bin/ -``` +`export GOPATH='mktemp -d'` + +`go get gitlab.com/yawning/obfs4.git/obfs4proxy` + +`sudo cp $GOPATH/bin/obfs4proxy /usr/local/bin/` ### 3. Edit your Tor config file, usually located at `/etc/tor/torrc` and replace its content with: @@ -96,18 +91,17 @@ Nickname PickANickname * Note that both Tor's OR port and its obfs4 port must be reachable. If your bridge is behind a firewall or NAT, make sure to open both ports. You can use [our reachability test](https://bridges.torproject.org/scan/) to see if your obfs4 port is reachable from the Internet. -### 4. Restart tor +### 4. Restart Tor * CentOS / RHEL: -``` -sudo semanage port -a -t tor_port_t -p tcp [OR port set earlier, in TODO1] -sudo semanage port -a -t tor_port_t -p tcp [obfs4 port set earlier, in TODO2] -``` +`sudo semanage port -a -t tor_port_t -p tcp [OR port set earlier, in TODO1]` + +`sudo semanage port -a -t tor_port_t -p tcp [obfs4 port set earlier, in TODO2]` * CentOS / RHEL / OpenSUSE: -`systemctl restart tor` +`sudo systemctl restart tor` ### 5. Monitor your logs (usually in your syslog) diff --git a/content/relay/setup/bridge/debian-ubuntu/contents.lr b/content/relay/setup/bridge/debian-ubuntu/contents.lr index 76926a9..9a8aff8 100644 --- a/content/relay/setup/bridge/debian-ubuntu/contents.lr +++ b/content/relay/setup/bridge/debian-ubuntu/contents.lr @@ -61,9 +61,9 @@ Don't forget to change the `ORPort`, `ServerTransportListenAddr`, `ContactInfo`, If your bridge is behind a firewall or NAT, make sure to open both ports. You can use [our reachability test](https://bridges.torproject.org/scan/) to see if your obfs4 port is reachable from the Internet. -### 4. Restart tor +### 4. Restart Tor -`systemctl restart tor` +`sudo systemctl restart tor` ### 5. Monitor your logs diff --git a/content/relay/setup/bridge/docker/contents.lr b/content/relay/setup/bridge/docker/contents.lr index 6d2d322..5cf2eb1 100644 --- a/content/relay/setup/bridge/docker/contents.lr +++ b/content/relay/setup/bridge/docker/contents.lr @@ -23,9 +23,7 @@ EMAIL=Z Replace `X` with your desired OR port, `Y` with your obfs4 port (make sure that **both** ports are forwarded in your firewall), and `Z` with your email address, which allows us to get in touch with you if there are problems with your bridge. With your bridge configuration in place, you can now deploy the container by running: -``` -docker-compose up -d obfs4-bridge -``` +`docker-compose up -d obfs4-bridge` This command will automatically load your `docker-compose.yml` file while considering the environment variables in `.env`. @@ -41,9 +39,7 @@ That's it! Your container is now bootstrapping your new obfs4 bridge. Upgrading to the latest version of our image is as simple as running: -``` -docker-compose up -d obfs4-bridge -``` +`docker-compose up -d obfs4-bridge` Note that your bridge's data directory (which includes its key material) is stored in a docker volume, so you won't lose your bridge's identity when upgrading to the latest docker image. If you are running multiple bridges on your computer, you need to repeat this step for each bridge. @@ -53,16 +49,12 @@ We will announce new image versions on the [tor-dev](https://lists.torproject.or You can inspect your bridge's logs by running: -``` -docker logs CONTAINER_ID -``` +`docker logs CONTAINER_ID` To use your new bridge in Tor Browser, you need its "bridge line". Here's how you can get your bridge line: -``` -docker exec CONTAINER_ID get-bridge-line -``` +`docker exec CONTAINER_ID get-bridge-line` This will return a string similar to the following: diff --git a/content/relay/setup/bridge/dragonflybsd/contents.lr b/content/relay/setup/bridge/dragonflybsd/contents.lr index 1027a79..0d449f8 100644 --- a/content/relay/setup/bridge/dragonflybsd/contents.lr +++ b/content/relay/setup/bridge/dragonflybsd/contents.lr @@ -16,13 +16,15 @@ DragonFlyBSD's daily snapshots and releases (starting with 3.4) come with `pkg` 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` @@ -30,9 +32,7 @@ Here, it will be similar to what we have on a **FreeBSD** system, and we are goi 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. @@ -45,25 +45,20 @@ We can simply edit the **URL** used to point to 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. Install `tor` and `obfs4proxy` DragonflyBSD's Package Here we can choose to install the latest stable version, like: -``` -pkg install tor obfs4proxy-tor -``` +`# pkg install tor obfs4proxy-tor` ... or install an alpha release: -``` -pkg install tor-devel obfs4proxy-tor -``` +`# pkg install tor-devel obfs4proxy-tor` ### 3. Configure `/usr/local/etc/tor/torrc` to run **Tor** as a Bridge @@ -109,19 +104,17 @@ Don't forget to change the `ORPort`, `ServerTransportListenAddr`, `ContactInfo`, Here we set `tor` to start at boot time and use the setuid feature, in order to bind to lower ports like 443 (the daemon itself will still run as a regular non-privileged user). -``` -echo "tor_setuid=YES" >> /etc/rc.conf -echo "tor_enable=YES" >> /etc/rc.conf -service tor start -``` +`# echo "tor_setuid=YES" >> /etc/rc.conf` + +`# echo "tor_enable=YES" >> /etc/rc.conf` + +`# service tor start` ### 5. Monitor your logs To confirm your bridge is running with no issues, you should see something like this in `/var/log/tor/notices.log`: -``` -tail /var/log/tor/notices.log -``` +`# tail /var/log/tor/notices.log` ``` [notice] Your Tor server's identity key fingerprint is '<NICKNAME> <FINGERPRINT>' diff --git a/content/relay/setup/bridge/fedora/contents.lr b/content/relay/setup/bridge/fedora/contents.lr index 11113ba..bd953f4 100644 --- a/content/relay/setup/bridge/fedora/contents.lr +++ b/content/relay/setup/bridge/fedora/contents.lr @@ -6,9 +6,9 @@ title: Fedora --- body: -### 1. Install tor and dependencies +### 1. Install Tor and dependencies -Add the following to /etc/yum.repos.d/tor.repo +Add the following to `/etc/yum.repos.d/tor.repo` ``` [tor] @@ -63,13 +63,13 @@ Nickname PickANickname If your bridge is behind a firewall or NAT, make sure to open both ports. You can use [our reachability test](https://bridges.torproject.org/scan/) to see if your obfs4 port is reachable from the Internet. -### 3. Restart tor +### 4. Restart Tor -``` -sudo semanage port -a -t tor_port_t -p tcp [OR port set earlier, in TODO1] -sudo semanage port -a -t tor_port_t -p tcp [obfs4 port set earlier, in TODO2] -systemctl restart tor -``` +`sudo semanage port -a -t tor_port_t -p tcp [OR port set earlier, in TODO1]` + +`sudo semanage port -a -t tor_port_t -p tcp [obfs4 port set earlier, in TODO2]` + +`sudo systemctl restart tor` ### 4. Monitor your logs (usually in your syslog) diff --git a/content/relay/setup/bridge/freebsd/contents.lr b/content/relay/setup/bridge/freebsd/contents.lr index 5d182d8..d954e06 100644 --- a/content/relay/setup/bridge/freebsd/contents.lr +++ b/content/relay/setup/bridge/freebsd/contents.lr @@ -12,9 +12,7 @@ body: ### 1. Install packages -``` -pkg install obfs4proxy-tor tor ca_root_nss -``` +`# pkg install obfs4proxy-tor tor ca_root_nss` ### 2. Edit your Tor config file, usually located at `/usr/local/etc/tor` and replace its content with: @@ -58,17 +56,15 @@ Don't forget to change the `ORPort`, `ServerTransportListenAddr`, `ContactInfo`, ### 3. Ensure that the `random_id` sysctl setting is enabled: -``` -echo "net.inet.ip.random_id=1" >> /etc/sysctl.conf -sysctl net.inet.ip.random_id=1 -``` +`# echo "net.inet.ip.random_id=1" >> /etc/sysctl.conf` + +`# sysctl net.inet.ip.random_id=1` ### 4. Start the tor daemon and make sure it starts at boot: -``` -sysrc tor_enable=YES -service tor start -``` +`# sysrc tor_enable=YES` + +`# service tor start` ### 5. Monitor your logs @@ -89,9 +85,7 @@ To confirm your bridge is running with no issues, you should see something like Create the following folder: -``` -mkdir -p /usr/local/etc/pkg/repos -``` +`# mkdir -p /usr/local/etc/pkg/repos` Create the file `/usr/local/etc/pkg/repos/FreeBSD.conf` with the following content: diff --git a/content/relay/setup/bridge/netbsd/contents.lr b/content/relay/setup/bridge/netbsd/contents.lr index c681497..f81e965 100644 --- a/content/relay/setup/bridge/netbsd/contents.lr +++ b/content/relay/setup/bridge/netbsd/contents.lr @@ -12,15 +12,11 @@ body: ### 1. Setup `pkg_add` -``` -echo "PKG_PATH=http://cdn.netbsd.org/pub/pkgsrc/packages/NetBSD/$(uname -m)/$(uname -r)/All" > /etc/pkg_install.conf -``` +`# echo "PKG_PATH=http://cdn.netbsd.org/pub/pkgsrc/packages/NetBSD/$(uname -m)/$(uname -r)/All" > /etc/pkg_install.conf` 2. Install `obfs4proxy` and `tor` NetBSD's package -``` -pkg_add obfs4proxy tor -``` +`# pkg_add obfs4proxy tor` ### 2. Configure `/usr/pkg/etc/tor/torrc` to run **Tor** as a Bridge @@ -64,19 +60,17 @@ Don't forget to change the `ORPort`, `ServerTransportListenAddr`, `ContactInfo`, ### 3. Start `tor`: -``` -ln -sf /usr/pkg/share/examples/rc.d/tor /etc/rc.d/tor -echo "tor=YES" >> /etc/rc.conf -/etc/rc.d/tor start -``` +`# ln -sf /usr/pkg/share/examples/rc.d/tor /etc/rc.d/tor` + +`# echo "tor=YES" >> /etc/rc.conf` + +`# /etc/rc.d/tor start` ### 4. Monitor your logs To confirm your bridge is running with no issues, you should see something like this: -``` -tail /var/log/messages -``` +`# tail /var/log/messages` ``` [notice] Your Tor server's identity key fingerprint is '<NICKNAME> <FINGERPRINT>' diff --git a/content/relay/setup/bridge/openbsd/contents.lr b/content/relay/setup/bridge/openbsd/contents.lr index 0a60051..4fc5f65 100644 --- a/content/relay/setup/bridge/openbsd/contents.lr +++ b/content/relay/setup/bridge/openbsd/contents.lr @@ -11,9 +11,8 @@ key: 8 body: ### 1. Install packages -``` -pkg_add tor obfs4proxy -``` + +`# pkg_add tor obfs4proxy` ### 2. Edit your Tor config file @@ -60,17 +59,16 @@ Don't forget to change the `ORPort`, `ServerTransportListenAddr`, `ContactInfo`, ### 3. Create the tor log directory and give it the correct permissions: -``` -mkdir /var/log/tor -chown _tor /var/log/tor -``` +`# mkdir /var/log/tor` + +`# chown _tor /var/log/tor` ### 4. Start the tor daemon and make sure it starts at boot: -``` -rcctl enable tor -rcctl start tor -``` +`# rcctl enable tor` + +`# rcctl start tor` + ### 5. Monitor your logs To confirm your bridge is running with no issues, you should see something like this (`/var/log/tor/notices.log`): diff --git a/content/relay/setup/bridge/windows/contents.lr b/content/relay/setup/bridge/windows/contents.lr index 7bf3ddc..26e8789 100644 --- a/content/relay/setup/bridge/windows/contents.lr +++ b/content/relay/setup/bridge/windows/contents.lr @@ -75,7 +75,7 @@ Don't forget to change the `ORPort`, `ServerTransportListenAddr`, `ContactInfo`, If your bridge is behind a firewall or NAT, make sure to open both ports. You can use [our reachability test](https://bridges.torproject.org/scan/) to see if your obfs4 port is reachable from the Internet. -### 4. Start tor +### 4. Start Tor Open up the Command Prompt App. Change your directory with: `cd C:\Users\<user>\AppData\Roaming\tor\`. Type: `tor.exe -f torrc`.

1 0

[tpo/master] Add new Tor Browser version 10.5a17
by sysrqb＠torproject.org 29 Jun '21

29 Jun '21

commit 6eefb47d90c9008d1edf26696f43012d149cfd80 Author: Matthew Finkel <sysrqb(a)torproject.org> Date: Tue Jun 29 00:55:07 2021 +0000 Add new Tor Browser version 10.5a17 --- databags/versions.ini | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/databags/versions.ini b/databags/versions.ini index b1d61dd4..485c30e6 100644 --- a/databags/versions.ini +++ b/databags/versions.ini @@ -12,13 +12,13 @@ version = 10.0.18 version = 10.0.18 [torbrowser-alpha] -version = 10.5a16 +version = 10.5a17 [torbrowser-android-alpha] -version = 10.5a16 +version = 10.5a17 [torbrowser-win-alpha] -version = 10.5a16 +version = 10.5a17 [tor-stable] version = 0.4.6.5

1 0

[community/master] Merge branch 'repair-brokenlink-eff-resource'
by gus＠torproject.org 28 Jun '21

28 Jun '21

commit 0b6f3cab9236aec5b5b1c1251f3da1263dc76cec Merge: da3a146 f4b04e3 Author: gus <gus(a)torproject.org> Date: Mon Jun 28 20:54:25 2021 -0300 Merge branch 'repair-brokenlink-eff-resource' content/relay/community-resources/contents.lr | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

1 0

[community/master] Add blog post title
by gus＠torproject.org 28 Jun '21

28 Jun '21

commit 071a13dacb12b96bbf71cc349888b06c199571ec Author: gus <gus(a)torproject.org> Date: Mon Jun 28 20:56:18 2021 -0300 Add blog post title --- content/relay/community-resources/contents.lr | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/relay/community-resources/contents.lr b/content/relay/community-resources/contents.lr index 6f1277e..30dbaaf 100644 --- a/content/relay/community-resources/contents.lr +++ b/content/relay/community-resources/contents.lr @@ -75,7 +75,7 @@ Many computer science departments, university libraries, and individual students These universities include the Massachusetts Institute of Technology (MIT CSAIL), Boston University, the University of Waterloo, the University of Washington, Northeastern University, Karlstad University, Universitaet Stuttgart, and Friedrich-Alexander University Erlangen-Nuremberg. -To learn more about how to get support for a relay on your university's network, check out EFF's resources: Tor on campus Part [I](https://www.eff.org/deeplinks/2014/08/tor-campus-part-i-its-been-done-an… and [II](https://www.eff.org/deeplinks/2014/08/tor-campus-part-ii-icebreakers-an…. +To learn more about how to get support for a relay on your university's network, check out EFF's resources: Tor on campus [Part 1 - It's Been Done Before and Should Happen Again](https://www.eff.org/deeplinks/2014/08/tor-campus-part-i-its-been-don… and [Part 2 - Icebreakers and Risk Mitigation Strategies](https://www.eff.org/deeplinks/2014/08/tor-campus-part-ii-icebre…. ## At your company or organization

1 0

[community/master] Update contents.lr
by gus＠torproject.org 28 Jun '21

28 Jun '21

commit f4b04e366837adc92092cecc0293670bc83d5812 Author: nyxnor <nyxnor(a)protonmail.com> Date: Sat Jun 26 01:03:01 2021 +0000 Update contents.lr --- content/relay/community-resources/contents.lr | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/relay/community-resources/contents.lr b/content/relay/community-resources/contents.lr index 667b241..6f1277e 100644 --- a/content/relay/community-resources/contents.lr +++ b/content/relay/community-resources/contents.lr @@ -75,7 +75,7 @@ Many computer science departments, university libraries, and individual students These universities include the Massachusetts Institute of Technology (MIT CSAIL), Boston University, the University of Waterloo, the University of Washington, Northeastern University, Karlstad University, Universitaet Stuttgart, and Friedrich-Alexander University Erlangen-Nuremberg. -To learn more about how to get support for a relay on your university's network, check out EFF's resources: [Tor on campus](https://www.eff.org/torchallenge/tor-on-campus.html). +To learn more about how to get support for a relay on your university's network, check out EFF's resources: Tor on campus Part [I](https://www.eff.org/deeplinks/2014/08/tor-campus-part-i-its-been-done-an… and [II](https://www.eff.org/deeplinks/2014/08/tor-campus-part-ii-icebreakers-an…. ## At your company or organization

1 0

[translation/tbmanual-contentspot] https://gitweb.torproject.org/translation.git/commit/?h=tbmanual-contentspot
by translation＠torproject.org 28 Jun '21

28 Jun '21

commit 6746577eaff21a3c7df7eccf5874daef5398bf42 Author: Translation commit bot <translation(a)torproject.org> Date: Mon Jun 28 21:46:47 2021 +0000 https://gitweb.torproject.org/translation.git/commit/?h=tbmanual-contentspot --- contents+fr.po | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/contents+fr.po b/contents+fr.po index 65e8823b77..f3ef835f12 100644 --- a/contents+fr.po +++ b/contents+fr.po @@ -1681,7 +1681,7 @@ msgid "" msgstr "" "Cliquez sur le menu (≡), allez dans Préférences (ou Options sur Windows), " "cliquez sur « Vie Privée et Sécurité », et dans la section des services " -"Onion cherchez « Prioriser les sites .onion s’ils sont connus » et cliquez " +"oignon cherchez « Prioriser les sites .onion s’ils sont connus » et cliquez " "sur « Toujours »." #: https//tb-manual.torproject.org/onion-services/ @@ -1697,7 +1697,7 @@ msgstr "" #: https//tb-manual.torproject.org/onion-services/ #: (content/onion-services/contents+en.lrtopic.body) msgid "## ONION SERVICE AUTHENTICATION" -msgstr "## SERVICE ONION D'AUTHENTIFICATION" +msgstr "## SERVICE OIGNON D'AUTHENTIFICATION" #: https//tb-manual.torproject.org/onion-services/ #: (content/onion-services/contents+en.lrtopic.body) @@ -1705,6 +1705,9 @@ msgid "" "An authenticated onion service is a service like an onion site that requires" " the client to provide an authentication token before accessing the service." msgstr "" +"Un service oignon authentifié est un service qui demande au client de " +"fournir un jeton d'authentification comme un site oignon avant d'accéder au " +"service." #: https//tb-manual.torproject.org/onion-services/ #: (content/onion-services/contents+en.lrtopic.body) @@ -1729,6 +1732,9 @@ msgid "" "When accessing an authenticated onion service, Tor Browser will show in the " "URL bar an icon of a little gray key, accompanied by a tooltip." msgstr "" +"Lorsque vous accèderez à un service oignon authentifié, le navigateur Tor " +"fera apparaître une petite clé grise accompagnée d'une infobulle dans la " +"barre d'URL." #: https//tb-manual.torproject.org/onion-services/ #: (content/onion-services/contents+en.lrtopic.body)

1 0

[translation/tails-misc_release] https://gitweb.torproject.org/translation.git/commit/?h=tails-misc_release
by translation＠torproject.org 28 Jun '21

28 Jun '21

commit b5809043e3644f4b342ee547bd04d7978a227226 Author: Translation commit bot <translation(a)torproject.org> Date: Mon Jun 28 21:46:27 2021 +0000 https://gitweb.torproject.org/translation.git/commit/?h=tails-misc_release --- nl.po | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/nl.po b/nl.po index 64a2e9d3b3..95dcb3eebd 100644 --- a/nl.po +++ b/nl.po @@ -24,7 +24,7 @@ # Meteor0id, 2019 # Nathan Follens, 2015 # Meteor0id, 2019-2020 -# Midgard, 2014 +# 8d98478d19376e343142c8c23c2a73b6_36c4a7f, 2014 # T. Des Maison <ton.siedsma(a)bof.nl>, 2014 # Thinkwell, 2018 # Thomas van Voorst <thomasv.voorst(a)hotmail.com>, 2017

1 0

[translation/tbmanual-contentspot] https://gitweb.torproject.org/translation.git/commit/?h=tbmanual-contentspot
by translation＠torproject.org 28 Jun '21

28 Jun '21

commit 91247f787e8614bd867ded3c3ccab001d8a7d009 Author: Translation commit bot <translation(a)torproject.org> Date: Mon Jun 28 21:17:02 2021 +0000 https://gitweb.torproject.org/translation.git/commit/?h=tbmanual-contentspot --- contents+fr.po | 12 ++++++++++-- 1 file changed, 10 insertions(+), 2 deletions(-) diff --git a/contents+fr.po b/contents+fr.po index b7cdea7831..65e8823b77 100644 --- a/contents+fr.po +++ b/contents+fr.po @@ -9,6 +9,7 @@ # Curtis Baltimore <curtisbaltimore(a)protonmail.com>, 2021 # AO <ao(a)localizationlab.org>, 2021 # Kingouin <tom.pons(a)hotmail.fr>, 2021 +# Matburnx <matboury(a)gmail.com>, 2021 # msgid "" msgstr "" @@ -16,7 +17,7 @@ msgstr "" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2021-06-22 19:43+CET\n" "PO-Revision-Date: 2018-11-14 12:31+0000\n" -"Last-Translator: Kingouin <tom.pons(a)hotmail.fr>, 2021\n" +"Last-Translator: Matburnx <matboury(a)gmail.com>, 2021\n" "Language-Team: French (https://www.transifex.com/otf/teams/1519/fr/)\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" @@ -1678,6 +1679,10 @@ msgid "" "entry \"Prioritize .onion sites when known.\" and check the option " "\"Always\"." msgstr "" +"Cliquez sur le menu (≡), allez dans Préférences (ou Options sur Windows), " +"cliquez sur « Vie Privée et Sécurité », et dans la section des services " +"Onion cherchez « Prioriser les sites .onion s’ils sont connus » et cliquez " +"sur « Toujours »." #: https//tb-manual.torproject.org/onion-services/ #: (content/onion-services/contents+en.lrtopic.body) @@ -1685,11 +1690,14 @@ msgid "" "Or, if you're already running Tor Browser, you can copy and paste this " "string in a new tab: `about:preferences#privacy` and change this setting." msgstr "" +"Ou, si vous être déjà en train d'utiliser le Navigateur Tor, vous pouvez " +"copier et coller ceci dans un nouvel onglet : `about:preferences#privacy` et" +" changez le paramètre." #: https//tb-manual.torproject.org/onion-services/ #: (content/onion-services/contents+en.lrtopic.body) msgid "## ONION SERVICE AUTHENTICATION" -msgstr "" +msgstr "## SERVICE ONION D'AUTHENTIFICATION" #: https//tb-manual.torproject.org/onion-services/ #: (content/onion-services/contents+en.lrtopic.body)

1 0

[donate-static/staging] Merge remote-tracking branch 'gitlab/kez-fix-footer-links-again' into staging
by gus＠torproject.org 28 Jun '21

28 Jun '21

commit 2811897c711db6db70282f4a2f640abd4ce8fc13 Merge: 3fc3ea26 cf0f3080 Author: gus <gus(a)torproject.org> Date: Mon Jun 28 17:16:38 2021 -0300 Merge remote-tracking branch 'gitlab/kez-fix-footer-links-again' into staging templates/footer.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

1 0

[donate-static/staging] Correctly fix the footer links linking to the wrong page
by gus＠torproject.org 28 Jun '21

28 Jun '21

commit cf0f308036072581f8180945159cbdadace6bf8e Author: kez <kez(a)torproject.org> Date: Thu Jun 24 13:55:47 2021 -0400 Correctly fix the footer links linking to the wrong page The previous solution was fragile and would most likely break in the future. This is the correct solution. See: tpo/web/donate-static!36 --- templates/footer.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/templates/footer.html b/templates/footer.html index a8b7d54e..1a45719b 100644 --- a/templates/footer.html +++ b/templates/footer.html @@ -42,7 +42,7 @@ <li{% if this.is_child_of(item.path) %} class="nav-item active" {% else %} class="nav-item"{% endif %}> {% set link = site.get(item.path) %} {% if link %} - <a class="nav-link text-light" href="/{{ item.path|url(alt=this.alt) }}"> + <a class="nav-link text-light" href="{{ ('/' + item.path)|url(alt=this.alt, absolute=True) }}"> {% else %} {% set local = bag('links', this.alt, id) %} {% if local %}

1 0

← Newer
1
...
7
8
9
10
11
12
13
...
129
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

tor-commits June 2021