The Tor Project issueshttps://gitlab.torproject.org/groups/tpo/-/issues2021-06-29T14:01:39Zhttps://gitlab.torproject.org/tpo/web/community/-/issues/205Broken link at relay/community-resources/2021-06-29T14:01:39ZemmapeelBroken link at relay/community-resources/On our website, at https://community.torproject.org/relay/community-resources/ on the section "At your university" there is a link to **"EFF's resources: Tor on campus."**.
This link is broken.
I tried to find something similar at the ...On our website, at https://community.torproject.org/relay/community-resources/ on the section "At your university" there is a link to **"EFF's resources: Tor on campus."**.
This link is broken.
I tried to find something similar at the EFF's page but I could not find those 'resources'.https://gitlab.torproject.org/tpo/web/team/-/issues/6Document the process to edit and test the CSS in lektor websites2021-09-08T19:50:35ZemmapeelDocument the process to edit and test the CSS in lektor websitesWe need a clear set of instructions for contributors to be able to help with CSS problems.
Maybe we should add them to the wiki at https://gitlab.torproject.org/tpo/web/wiki
```
22:18 < rotationmatrix> If I recall correctly, you'll need...We need a clear set of instructions for contributors to be able to help with CSS problems.
Maybe we should add them to the wiki at https://gitlab.torproject.org/tpo/web/wiki
```
22:18 < rotationmatrix> If I recall correctly, you'll need the sass compiler installed and then you should be able to
compile with:
22:18 < rotationmatrix> $ sass lego/assets/scss:lego/assets/static/css
22:18 < rotationmatrix> from the root of the project
22:19 < rotationmatrix> https://sass-lang.com/install
```https://gitlab.torproject.org/tpo/anti-censorship/team/-/issues/8Create and document our commit workflow2023-04-11T18:29:51ZCecylia BocovichCreate and document our commit workflowAt the moment, each project has been maintained slightly differently, but with the branch changes we're taking the opportunity to document and consolidate our workflows on each of these projects. They don't all need to be handled the sam...At the moment, each project has been maintained slightly differently, but with the branch changes we're taking the opportunity to document and consolidate our workflows on each of these projects. They don't all need to be handled the same, but we should definitely document the different workflows and point out projects that have exceptions. This workflow should include the following:
- which repositories to push to and where our mirrors are pointing
- do we introduce merge commits or do we rebase branches before merging?
- do we use the gitlab interface or merge things locally?
- how many reviews do we need and who maintains/has access to which repository?
- we had some discussion over on #7 about signing commits
- which projects have releases and what is the release workflow?
This is generally a good idea, and something we should work into our workflow. Let's use this ticket to document a proposal for different workflows. Again, some repositories for our team are maintained by people outside TPI so the focus should be on documentation and best practices, not necessarily in making everything the same.meskiomeskio@torproject.orgmeskiomeskio@torproject.orghttps://gitlab.torproject.org/tpo/anti-censorship/team/-/issues/7Set up gitolite <--> gitlab mirrors2022-03-01T17:19:09ZCecylia BocovichSet up gitolite <--> gitlab mirrorsSince our branch name change in #6, we'll have to update our mirrors and we might as well be consistent this time.
I'm proposing a one way mirror from Gitlab to git.tpo because it means we can use the gitlab merge feature. This would ma...Since our branch name change in #6, we'll have to update our mirrors and we might as well be consistent this time.
I'm proposing a one way mirror from Gitlab to git.tpo because it means we can use the gitlab merge feature. This would make git.tpo mostly read only except for the repositories that have not yet been migrated to gitlab.
However, I'm open to feedback. My only strong preference is that we're consistent.https://gitlab.torproject.org/tpo/web/support/-/issues/203add explanation about disabled Master Password, on support portal or ideally ...2023-11-13T13:44:30Zemmapeeladd explanation about disabled Master Password, on support portal or ideally in tor browser itselfA user entered today on the irc asking how could they add a master password to the Tor Browser. It seems a common doubt for new users.
Proposal:
- Maybe it will be good to have an official explanation on our Support portal about why the...A user entered today on the irc asking how could they add a master password to the Tor Browser. It seems a common doubt for new users.
Proposal:
- Maybe it will be good to have an official explanation on our Support portal about why there is no master password in Tor Browser?
From the Tor Browser Design Draft (https://2019.www.torproject.org/projects/torbrowser/design/):
We disable the password saving functionality in the browser as part of our Disk Avoidance requirement. However, since users may decide to re-enable disk history records and password saving, we also set the signon.autofillForms preference to false to prevent saved values from immediately populating fields upon page load. Since JavaScript can read these values as soon as they appear, setting this preference prevents automatic linkability from stored passwords.
(we should write a more simple answer)https://gitlab.torproject.org/tpo/ux/research/-/issues/40Add a persona who uses a public computer2023-08-08T18:55:10ZcypherpunksAdd a persona who uses a public computerFrom the blog:
https://blog.torproject.org/comment/291342#comment-291342
https://blog.torproject.org/comment/291422#comment-291422
> [The commenter] then said, "this could be a problem in a public computer, when many persons want to use...From the blog:
https://blog.torproject.org/comment/291342#comment-291342
https://blog.torproject.org/comment/291422#comment-291422
> [The commenter] then said, "this could be a problem in a public computer, when many persons want to use same account." It sounds like a kiosk or an Internet café. That is an interesting new persona to study, Community Team!! (to Gus, et al.) Usually though, public computers are configured for a guest account and/or to automatically log out after a period of time and delete the guest account's files.
It could be any shared device. A neighbor's laptop, phone, etc. If the device is public, then it isn't managed by a neighbor but by an administrator.
I guess this issue should be moved to tpo/ux/research. I wrote it in tpo/web/community because cypherpunks such as myself are not allowed to post in ux/research.https://gitlab.torproject.org/tpo/applications/tor-browser-build/-/issues/40286Add Burmese as supported language in Windows installer2022-12-22T10:52:50ZMatthew FinkelAdd Burmese as supported language in Windows installerThis should be added in tbb-windows-installer, but I'm not sure a patch will be accepted right now.This should be added in tbb-windows-installer, but I'm not sure a patch will be accepted right now.https://gitlab.torproject.org/tpo/web/manual/-/issues/89Deploy Tor Browser User Manual on Gitlab.com2022-07-08T14:04:50ZGusDeploy Tor Browser User Manual on Gitlab.comAt the moment, the Tor Browser User Manual is only accessible on the subdomain: tb-manual.torproject.org. But, thinking about users living in countries that are blocking the torproject.org main domain, they can't access this documentatio...At the moment, the Tor Browser User Manual is only accessible on the subdomain: tb-manual.torproject.org. But, thinking about users living in countries that are blocking the torproject.org main domain, they can't access this documentation. Since Lektor is a static generator site, it's possible to host this documentation on gitlab.com, which isn't censored (in most cases).
Tasks
* [x] Write a CI/CD and deploy this manual on gitlab.com pages. See: https://gitlab.torproject.org/tpo/web/team/-/issues/4Sponsor 96: Rapid Expansion of Access to the Uncensored Internet through Tor in China, Hong Kong, & Tibethttps://gitlab.torproject.org/tpo/web/manual/-/issues/88How to install Tor Browser on Linux is not working or clear enough2021-09-04T13:26:17ZGusHow to install Tor Browser on Linux is not working or clear enoughToday on #tor channel we had a Ubuntu user that couldn't start Tor Browser.
We need to update our instructions on Tor Browser User Manual to make it more clear how they can launch Tor Browser.
```
You'll need to tell your GNU/Linux that...Today on #tor channel we had a Ubuntu user that couldn't start Tor Browser.
We need to update our instructions on Tor Browser User Manual to make it more clear how they can launch Tor Browser.
```
You'll need to tell your GNU/Linux that you want the ability to execute shell scripts from the graphical interface or the command line. Navigate to the newly extracted Tor Browser directory. Right click on start-tor-browser.desktop, open Properties or Preferences and change the permission to allow executing file as program. Double-click the icon to start up Tor Browser for the first time.
Note: On Ubuntu and some other distros if you try to launch the start-tor-browser.desktop file a text file might open up. To change this behavior and launch Tor Browser instead, follow this: Open "Files" (GNOME Files/Nautilus) → open Preferences → go to the 'Behavior' Tab → Select "Run them" or "Ask what to do" under "Executable Text Files". If you choose the latter click on "Run" after launching the start-tor-browser.desktop file.
```
https://tb-manual.torproject.org/installation/
ps: This issue is not open for Outreachies.championquizzerchampionquizzer@torproject.orgchampionquizzerchampionquizzer@torproject.orghttps://gitlab.torproject.org/tpo/network-health/team/-/issues/75Merge exit scanner/TorDNSEL/check documentation2021-08-26T12:24:07ZirlMerge exit scanner/TorDNSEL/check documentationExit scanner documentation exists in its own wiki, to facilitate easier editing and maintenance of this it should get merged in here.Exit scanner documentation exists in its own wiki, to facilitate easier editing and maintenance of this it should get merged in here.irlirlhttps://gitlab.torproject.org/tpo/web/support/-/issues/181Add to FAQ section "Is it worth upgrading my Tor Relay"2023-11-13T05:22:53ZBurnleydevAdd to FAQ section "Is it worth upgrading my Tor Relay"Saw this question **"Is it worth upgrading my Tor Relay"** on reddit.com/r/Tor. It's worth adding it to the FAQ section to help others.Saw this question **"Is it worth upgrading my Tor Relay"** on reddit.com/r/Tor. It's worth adding it to the FAQ section to help others.https://gitlab.torproject.org/tpo/web/support/-/issues/180[Tor Browser] Add a note that there's currently no good way of exporting/impo...2021-06-29T18:43:57Zchampionquizzerchampionquizzer@torproject.org[Tor Browser] Add a note that there's currently no good way of exporting/importing bookmarks in TBAIn light of the discussion under the tickets: https://gitlab.torproject.org/tpo/web/support/-/issues/156 and https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/31617, we must add a short note that there's currently no go...In light of the discussion under the tickets: https://gitlab.torproject.org/tpo/web/support/-/issues/156 and https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/31617, we must add a short note that there's currently no good way of exporting/importing bookmarks in Tor Browser for Android under the response to the FAQ -- [How can I export and import bookmarks in Tor Browser?](https://support.torproject.org/tbb/export-and-import-bookmarks/)
We should also acknowledge https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/31617 and point readers to the discussion under that ticket.Sehrish AslamSehrish Aslamhttps://gitlab.torproject.org/tpo/web/support/-/issues/178Support Portal: How to Access an Onion Service2023-11-13T05:06:00ZSehrish AslamSupport Portal: How to Access an Onion ServiceNote: Came across a user asking for help on Reddit on "How to setup .onion website".
On [Support Portal](https://support.torproject.org/) under [Onion Services](https://support.torproject.org/onionservices/) two important titles must b...Note: Came across a user asking for help on Reddit on "How to setup .onion website".
On [Support Portal](https://support.torproject.org/) under [Onion Services](https://support.torproject.org/onionservices/) two important titles must be added.
1. How To Access an Onion Service with a brief introduction and link to [HOW TO ACCESS AN ONION SERVICE](https://tb-manual.torproject.org/onion-services/)
2. How to Configure Onion Services for Tor with link to [How to Configure Onion Services for Tor](https://2019.www.torproject.org/docs/tor-onion-service.html.en)
IMHO, in order to make website UX/UI friendly links must be added so users find required information without any trouble. Although there is a separate page under [User Manual](https://tb-manual.torproject.org/about/) about [Onion Services](https://tb-manual.torproject.org/onion-services/) but I believe these two must be linked together.
Additionally, [Onion Services](https://support.torproject.org/glossary/) entry in Glossary must also include link to detailed description on [Onion Services](https://tb-manual.torproject.org/onion-services/)
@gus if you approve these suggestion I can work on this.https://gitlab.torproject.org/tpo/community/l10n/-/issues/40030Document how to retire a translation resource2021-04-07T09:42:12ZemmapeelDocument how to retire a translation resourceThe process to stop translating a resource needs to be documentedThe process to stop translating a resource needs to be documentedemmapeelemmapeelhttps://gitlab.torproject.org/tpo/web/community/-/issues/193Past GSOC projects don't appear, but there is an empty section for them.2023-04-22T07:32:26ZemmapeelPast GSOC projects don't appear, but there is an empty section for them.at the bottom of https://community.torproject.org/gsoc/ there is a section only consisting of:
Past Projects
Here are some successful projects which have been implemented in the past by Google Summer of Code and Outreachy participants
...at the bottom of https://community.torproject.org/gsoc/ there is a section only consisting of:
Past Projects
Here are some successful projects which have been implemented in the past by Google Summer of Code and Outreachy participants
But the past projects are not there anymore.https://gitlab.torproject.org/tpo/web/community/-/issues/188[content][types of relays] Mentions to unexisting section are confusing2022-01-20T19:12:23Zemmapeel[content][types of relays] Mentions to unexisting section are confusingIn the page https://community.torproject.org/relay/types-of-relays/ , in the Exit relay section, we mention the 'legal considerations section' twice.
One is linked to https://community.torproject.org/relay/community-resources , but the ...In the page https://community.torproject.org/relay/types-of-relays/ , in the Exit relay section, we mention the 'legal considerations section' twice.
One is linked to https://community.torproject.org/relay/community-resources , but the other is unlinked, and there are no sections called 'legal considerations'.
> Exit relays have the greatest legal exposure and liability of all the relays. For example, if a user downloads copyrighted material while using your exit relay, you, the operator may receive a DMCA notice. Any abuse complaints about the exit will go directly to you (via your hoster, depending on the WHOIS records). Generally, most complaints can be handled pretty easily through template letters, which we'll discuss further in the **legal considerations section**.
> Because of the legal exposure that comes with running an exit relay, you should not run a Tor exit relay from your home. Ideal exit relay operators are affiliated with some institution, like a university, a library, a hackerspace or a privacy related organization. An institution can not only provide greater bandwidth for the exit, but is better positioned to handle abuse complaints or the rare law enforcement inquiry.
> If you are considering running an exit relay, please read the **section on legal considerations** for exit relay operators.
We should rephrase, mention the current name of the section, and also add a link where there is none.https://gitlab.torproject.org/tpo/core/tor/-/issues/40340Man tor - Option `ClientTransportPlugin` should move from `GENERAL OPTIONS` t...2023-04-03T16:38:12ZcypherpunksMan tor - Option `ClientTransportPlugin` should move from `GENERAL OPTIONS` to `CLIENT OPTIONS`For tor-0.4.6.0-alpha-dev.
ChangeLog :
```
o Documentation (man tor):
- Move option `ClientTransportPlugin` from `GENERAL OPTIONS` to `CLIENT OPTIONS`. Closes issue #40XXX
```
Output of `git diff HEAD` :
```
diff --git a/doc/...For tor-0.4.6.0-alpha-dev.
ChangeLog :
```
o Documentation (man tor):
- Move option `ClientTransportPlugin` from `GENERAL OPTIONS` to `CLIENT OPTIONS`. Closes issue #40XXX
```
Output of `git diff HEAD` :
```
diff --git a/doc/man/tor.1.txt b/doc/man/tor.1.txt
index f5dd1ec..308bf2d 100644
--- a/doc/man/tor.1.txt
+++ b/doc/man/tor.1.txt
@@ -334,20 +334,6 @@ forward slash (/) in the configuration file and on the command line.
as a float value. This is an advanced option; you generally shouldn't have
to mess with it. (Default: -1)
-[[ClientTransportPlugin]] **ClientTransportPlugin** __transport__ socks4|socks5 __IP__:__PORT__::
-**ClientTransportPlugin** __transport__ exec __path-to-binary__ [options]::
- In its first form, when set along with a corresponding Bridge line, the Tor
- client forwards its traffic to a SOCKS-speaking proxy on "IP:PORT".
- (IPv4 addresses should written as-is; IPv6 addresses should be wrapped in
- square brackets.) It's the
- duty of that proxy to properly forward the traffic to the bridge. +
- +
- In its second form, when set along with a corresponding Bridge line, the Tor
- client launches the pluggable transport proxy executable in
- __path-to-binary__ using __options__ as its command-line options, and
- forwards its traffic to it. It's the duty of that proxy to properly forward
- the traffic to the bridge. (Default: none)
-
[[ConnLimit]] **ConnLimit** __NUM__::
The minimum number of file descriptors that must be available to the Tor
process before it will start. Tor will ask the OS for as many file
@@ -1178,6 +1164,21 @@ The following options are useful only for clients (that is, if
controller request). If true, multicast DNS hostnames for machines on the
local network (of the form *.local) are also rejected. (Default: 1)
+[[ClientTransportPlugin1]] **ClientTransportPlugin** __transport__ socks4|socks5 __IP__:__PORT__ +
+
+[[ClientTransportPlugin2]] **ClientTransportPlugin** __transport__ exec __path-to-binary__ [options]::
+ In its first form, when set along with a corresponding Bridge line, the Tor
+ client forwards its traffic to a SOCKS-speaking proxy on "IP:PORT".
+ (IPv4 addresses should written as-is; IPv6 addresses should be wrapped in
+ square brackets.) It's the
+ duty of that proxy to properly forward the traffic to the bridge. +
+ +
+ In its second form, when set along with a corresponding Bridge line, the Tor
+ client launches the pluggable transport proxy executable in
+ __path-to-binary__ using __options__ as its command-line options, and
+ forwards its traffic to it. It's the duty of that proxy to properly forward
+ the traffic to the bridge. (Default: none)
+
[[ClientUseIPv4]] **ClientUseIPv4** **0**|**1**::
If this option is set to 0, Tor will avoid connecting to directory servers
and entry nodes over IPv4. Note that clients with an IPv4
```Tor: 0.4.8.x-freezeAlexander Færøyahf@torproject.orgAlexander Færøyahf@torproject.orghttps://gitlab.torproject.org/tpo/core/tor/-/issues/40339`make check-docs` return fake errors on tor-0.4.6.0-alpha-dev2022-07-21T19:19:42Zcypherpunks`make check-docs` return fake errors on tor-0.4.6.0-alpha-devRunning `make check-docs` on tor-0.4.6.0-alpha-dev generate some "missing anchor" :
```
make all-am
make[1]: Entering directory '[scrubbed]/tor-master'
make[1]: Leaving directory '[scrubbed]/tor-master'
perl ./scripts/maint/checkOption...Running `make check-docs` on tor-0.4.6.0-alpha-dev generate some "missing anchor" :
```
make all-am
make[1]: Entering directory '[scrubbed]/tor-master'
make[1]: Leaving directory '[scrubbed]/tor-master'
perl ./scripts/maint/checkOptionDocs.pl
Missing an anchor: ClientTransportPlugin
Missing an anchor: SocksPort
Missing an anchor: NATDPort
Missing an anchor: after
Orphaned in torrc.sample.in: SOCKSPolicy SOCKSPort
[...]
```
There is 4 missing anchor. They are false positifs. They are only options description text that are in bold and are at the beginning of a line. Here is `git diff HEAD` to solve those annoying false positives :
```
diff --git a/doc/man/tor.1.txt b/doc/man/tor.1.txt
index f5dd1ec..387ce82 100644
--- a/doc/man/tor.1.txt
+++ b/doc/man/tor.1.txt
@@ -61,8 +61,8 @@ NOTE: Configuration options on the command line override those in
configuration files. See **<<conf-format,THE CONFIGURATION FILE
FORMAT>>** for more information.
-The following options in this section are only recognized on the
-**`tor`** command line, not in a configuration file.
+The following options in this section are only recognized on the **`tor`**
+command line, not in a configuration file.
[[opt-h]] **`-h`**, **`--help`**::
Display a short help message and exit.
@@ -334,8 +334,9 @@ forward slash (/) in the configuration file and on the command line.
as a float value. This is an advanced option; you generally shouldn't have
to mess with it. (Default: -1)
-[[ClientTransportPlugin]] **ClientTransportPlugin** __transport__ socks4|socks5 __IP__:__PORT__::
-**ClientTransportPlugin** __transport__ exec __path-to-binary__ [options]::
+[[ClientTransportPlugin1]] **ClientTransportPlugin** __transport__ socks4|socks5 __IP__:__PORT__ +
+
+[[ClientTransportPlugin2]] **ClientTransportPlugin** __transport__ exec __path-to-binary__ [options]::
In its first form, when set along with a corresponding Bridge line, the Tor
client forwards its traffic to a SOCKS-speaking proxy on "IP:PORT".
(IPv4 addresses should written as-is; IPv6 addresses should be wrapped in
@@ -1043,9 +1044,8 @@ forward slash (/) in the configuration file and on the command line.
// These options are in alphabetical order, with exceptions as noted.
// Please keep them that way!
-The following options are useful only for clients (that is, if
-**SocksPort**, **HTTPTunnelPort**, **TransPort**, **DNSPort**, or
-**NATDPort** is non-zero):
+The following options are useful only for clients (that is, if **SocksPort**, **HTTPTunnelPort**, **TransPort**, **DNSPort**,
+or **NATDPort** is non-zero):
[[AllowNonRFC953Hostnames]] **AllowNonRFC953Hostnames** **0**|**1**::
When this option is disabled, Tor blocks hostnames containing illegal
@@ -3224,8 +3224,8 @@ on the public Tor network.
The following options are used to configure a hidden service. Some options
apply per service and some apply for the whole tor instance.
-The next section describes the per service options that can only be set
-**after** the **HiddenServiceDir** directive
+The next section describes the per service options that can only be set **after**
+the **HiddenServiceDir** directive
**PER SERVICE OPTIONS:**
```https://gitlab.torproject.org/tpo/community/relays/-/issues/16Review and incorporate Torservers.net abuse templates to the relay documentation2022-03-16T20:23:36ZGusReview and incorporate Torservers.net abuse templates to the relay documentationBrabo let us know that:
The torservers.net wiki which hosts https://www.torservers.net/wiki/abuse/templates which https://community.torproject.org/relay/community-resources/tor-abuse-templates/ links to will go defunct at some point in ...Brabo let us know that:
The torservers.net wiki which hosts https://www.torservers.net/wiki/abuse/templates which https://community.torproject.org/relay/community-resources/tor-abuse-templates/ links to will go defunct at some point in the future. It may be good to see which templates are useful to add to the tor project template set.https://gitlab.torproject.org/tpo/anti-censorship/team/-/issues/22Get more private bridges2023-08-07T11:18:19ZCecylia BocovichGet more private bridgesWe maintain a list of private bridges that we distribute to NGOs and individuals in places that block most of our other distribution methods. BridgeDB sets aside some bridges for private distribution in the "unallocated" or "reserved" po...We maintain a list of private bridges that we distribute to NGOs and individuals in places that block most of our other distribution methods. BridgeDB sets aside some bridges for private distribution in the "unallocated" or "reserved" pool.
At the end of March we are losing some private bridges that volunteers run so we need a few actions to get more private (stable if possible) bridges:
- [ ] Create and document a pipeline for distributing "unallocated" bridges as private bridges. We should document a pipeline for taking bridges the reserved this pool and getting them into the hands of users. (meskio)
- [x] Ask organizations to run obfs4 bridges (gus)
- [x] Check with the donated hw we may get (gaba)
_Update on October 12th: Documentation is the only issue missing here._Sponsor 96: Rapid Expansion of Access to the Uncensored Internet through Tor in China, Hong Kong, & Tibetmeskiomeskio@torproject.orgmeskiomeskio@torproject.org