The Tor Project issueshttps://gitlab.torproject.org/groups/tpo/-/issues2024-02-13T16:04:39Zhttps://gitlab.torproject.org/tpo/tpa/team/-/issues/40421enhance incident response procedures2024-02-13T16:04:39Zanarcatenhance incident response procedurestoday we had an ... interesting situation with the puppet infrastructure. while we have actually recovered pretty well, all things considered, it would be important to enhance our response to such situation so that they are less stressfu...today we had an ... interesting situation with the puppet infrastructure. while we have actually recovered pretty well, all things considered, it would be important to enhance our response to such situation so that they are less stressful and why not, even more "fun", if i can be so daring.
some background reading:
* [Got game? Secrets of great incident management](https://bitfieldconsulting.com/blog/got-game-secrets-of-great-incident-management)
* [pager duty incident response documentation](https://response.pagerduty.com/)
some ideas:
* have an issue template for incidents (so, in git, which requires a git repository here, but maybe it's finally time to merge the wiki repo here anyways), available offline
* run simulations/games
* have post-mortem templates, here's the [pager duty template](https://response.pagerduty.com/after/post_mortem_template/)
* gitlab has some [incident management primitives](https://docs.gitlab.com/ee/operations/incident_management/) including aforementioned "[incidents](https://docs.gitlab.com/ee/operations/incident_management/incidents.html)" (which are really just issues)...
* ... but also [integrations](https://docs.gitlab.com/ee/operations/incident_management/integrations.html) which is especially interesting considering they have *native* Prometheus integration, which might require switching from nagios to prometheus (#29864)
anyways, the core idea here is:
1. have incident roles (note-taker, driver, comms, etc)
2. incident and post-mortem templates
3. run gameshttps://gitlab.torproject.org/tpo/tpa/gitlab/-/issues/56Packages wiki page getting discontinued2021-10-21T15:17:20ZGabagaba@torproject.orgPackages wiki page getting discontinuedAtagar is not going to keep maintaining https://trac.torproject.org/projects/tor/wiki/doc/packages
I'm opening this ticket to make a decision if it needs to be moved into gitlab and continue to exist.
https://gitweb.torproject.org/doct...Atagar is not going to keep maintaining https://trac.torproject.org/projects/tor/wiki/doc/packages
I'm opening this ticket to make a decision if it needs to be moved into gitlab and continue to exist.
https://gitweb.torproject.org/doctor.git/tree/package_versions.py would have to get adapted to gitlab.https://gitlab.torproject.org/tpo/core/chutney/-/issues/22376Make the chutney README less scary2022-02-07T19:26:22ZteorMake the chutney README less scaryChutney works decently well now.
We should edit the README intro to reflect that.Chutney works decently well now.
We should edit the README intro to reflect that.https://gitlab.torproject.org/tpo/network-health/exitmap/-/issues/6Fix and document exitmap related bad relay tests2024-01-17T09:19:34ZGeorg KoppenFix and document exitmap related bad relay testsThis ticket is a placeholder for going over other exitmap related tests (for `checktest.py` see legacy/trac#33663) and document them while we are at it.This ticket is a placeholder for going over other exitmap related tests (for `checktest.py` see legacy/trac#33663) and document them while we are at it.https://gitlab.torproject.org/tpo/core/chutney/-/issues/17282Chutney could use a HOWTO for writing new test cases, network tests, etc2022-02-07T19:32:12ZNick MathewsonChutney could use a HOWTO for writing new test cases, network tests, etcDue April 2016Due April 2016https://gitlab.torproject.org/tpo/community/support/-/issues/40004[RT] Create a new article to say that YouTube is unhappy with Tor Browser and...2020-10-07T12:52:38ZGus[RT] Create a new article to say that YouTube is unhappy with Tor Browser and what users can doAfter Tor Browser 10.0 release, we're receiving some emails from users reporting that YouTube is not working, see https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/40140. We need to create a new RT article to answer the...After Tor Browser 10.0 release, we're receiving some emails from users reporting that YouTube is not working, see https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/40140. We need to create a new RT article to answer these users.GusGushttps://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/web/manual/-/issues/105Document TB specific flags available with the start-tor-browser.desktop file ...2021-09-03T19:44:36Zchampionquizzerchampionquizzer@torproject.orgDocument TB specific flags available with the start-tor-browser.desktop file on linuxDocument all of the useful Tor Browser specific flags that are available with the `start-tor-browser.desktop` file in GNU/Linux. Maybe this can be filed under something like 'Post-Installation'.
```
$ ./start-tor-browser.desktop --help
L...Document all of the useful Tor Browser specific flags that are available with the `start-tor-browser.desktop` file in GNU/Linux. Maybe this can be filed under something like 'Post-Installation'.
```
$ ./start-tor-browser.desktop --help
Launching './Browser/start-tor-browser --detach --help'...
.....
Tor Browser Script Options
--verbose Display Tor and Firefox output in the terminal
--log [file] Record Tor and Firefox output in file (default: tor-browser.log)
--detach Detach from terminal and run Tor Browser in the background.
--register-app Register Tor Browser as a desktop app for this user
--unregister-app Unregister Tor Browser as a desktop app for this user
```championquizzerchampionquizzer@torproject.orgchampionquizzerchampionquizzer@torproject.orghttps://gitlab.torproject.org/tpo/anti-censorship/rdsys/-/issues/31Document how rdsys tests bridges2021-01-08T19:32:22ZPhilipp Winterphw@torproject.orgDocument how rdsys tests bridgesLet's work on a new piece of documentation that details how rdsys tests bridges. In particular, the documentation should talk about the interaction between rdsys and bridgestrap.Let's work on a new piece of documentation that details how rdsys tests bridges. In particular, the documentation should talk about the interaction between rdsys and bridgestrap.Sponsor 30 - Objective 2.3Philipp Winterphw@torproject.orgPhilipp Winterphw@torproject.orghttps://gitlab.torproject.org/tpo/web/support/-/issues/133Removed space before and after slash (/)2020-11-18T19:40:55ZGoodness ChrisugariRemoved space before and after slash (/)Space before or after a slash should be avoided, they can be used that way when quoting a poem in which case the slash indicates a line break. They should be removed since the slash is used to indicate the word "or" here.Space before or after a slash should be avoided, they can be used that way when quoting a poem in which case the slash indicates a line break. They should be removed since the slash is used to indicate the word "or" here.GusGushttps://gitlab.torproject.org/tpo/web/support/-/issues/140[Connecting to Tor] Add the command line option to view logs2020-12-28T16:43:02Zchampionquizzerchampionquizzer@torproject.org[Connecting to Tor] Add the command line option to view logsAn user reported on the #tor IRC channel that they couldn't launch the Tor Browser and couldn't obtain the logs either. Currently, we direct users to two ways of getting the Tor logs in the ['Connecting to Tor'](https://support.torprojec...An user reported on the #tor IRC channel that they couldn't launch the Tor Browser and couldn't obtain the logs either. Currently, we direct users to two ways of getting the Tor logs in the ['Connecting to Tor'](https://support.torproject.org/connecting/#connecting-2) support page, i.e. with the option to 'copy Tor log to Clipboard' or to navigate through the hamburger menu within the browser. We should add the option of launching the Tor Browser in terminal with the verbose flag, i.e. `./start-tor-browser.desktop --verbose` to get the logs right in the terminal (this is what helped the user to diagnose the problem in this case).championquizzerchampionquizzer@torproject.orgchampionquizzerchampionquizzer@torproject.orghttps://gitlab.torproject.org/tpo/network-health/team/-/issues/199Clarify the bandwidth authority spec to include client and server/service paths2022-03-11T18:19:35ZteorClarify the bandwidth authority spec to include client and server/service pathsIt's unclear whether the "average stream capacity regardless of path" includes the path from the client to the entry, and the exit to the internet server. Pragmatically, in the current design, it has to include client and internet server...It's unclear whether the "average stream capacity regardless of path" includes the path from the client to the entry, and the exit to the internet server. Pragmatically, in the current design, it has to include client and internet server. (Or, in the case of onion services, client and service.)
I don't know if this affects our design at all, but it should be clarified in the spec.https://gitlab.torproject.org/tpo/web/support/-/issues/146Update debian repository instructions2021-09-08T15:56:28ZGusUpdate debian repository instructionsFrom Frontdesk:
https://support.torproject.org/apt/#apt-1
As well as the 'deb.torproject.org-keyring' package to use the signing key in a more secure manner. the problem is that "apt-key add -" saves the key to
/etc/apt/trusted.gpg.d/,...From Frontdesk:
https://support.torproject.org/apt/#apt-1
As well as the 'deb.torproject.org-keyring' package to use the signing key in a more secure manner. the problem is that "apt-key add -" saves the key to
/etc/apt/trusted.gpg.d/, and apt tries all the keys stored there to verify signatures of all repos.
third party repos should use /usr/share/keyrings/ for (non-ASCII-armored) keyrings and explicitly pin their repo to their own keyring, e.g.
deb [arch=amd64 signed-by=/usr/share/keyrings/tor_keyring.gpg] https://...
more on this can be found here:
https://wiki.debian.org/DebianRepository/UseThirdPartyGusGushttps://gitlab.torproject.org/tpo/network-health/sbws/-/issues/40015Bandwidth file spec v1.5 adds Tor version but sbws adds Tor version with band...2020-12-07T11:12:02ZjugaBandwidth file spec v1.5 adds Tor version but sbws adds Tor version with bandwidth file spec as v1.4Reported by @atagar in irc #tor-dev:
```
22:53 <+ atagar> juga, karsten: Our bandwidth file spec says that the most recent version is 1.5.0 to add a tor_version attribute (https://gitweb.torproject.org/torspec.git/commit/?id=7d8b4bc)...Reported by @atagar in irc #tor-dev:
```
22:53 <+ atagar> juga, karsten: Our bandwidth file spec says that the most recent version is 1.5.0 to add a tor_version attribute (https://gitweb.torproject.org/torspec.git/commit/?id=7d8b4bc). However,
CollecTor's most recent bandwidth files (https://collector.torproject.org/recent/relay-descriptors/bandwidths/) say that they're version 1.4.0 yet include a tor_version. Maybe our bandwidth
scanners added this
22:53 <+ atagar> attribute without updating their version number?
22:54 <+ atagar> If so since this has been live for a while we should probably simply change the spec to say that tor_version is a 1.4.0 attribute, and that we don't have a version 1.5.0.
```
probably we forgot to update the bandwidth file spec in the sbws's generated bandwidth file.
I'm not sure whether we should change it in the bandwidth spec or in sbws, since bandwidth spec also says v1.5 adds other things.sbws: 1.1.x-finalhttps://gitlab.torproject.org/tpo/anti-censorship/bridgedb/-/issues/12507Automate BridgeDB documentation builds2022-03-01T17:35:40ZIsis LovecruftAutomate BridgeDB documentation buildsThe developer documentation for BridgeDB needs a place to live. Currently, Sphinx builds can be manually triggered to produce HTML documentation (as well as other types). I have been manually scp'ing it to https://para.noid.cat/bridgedb,...The developer documentation for BridgeDB needs a place to live. Currently, Sphinx builds can be manually triggered to produce HTML documentation (as well as other types). I have been manually scp'ing it to https://para.noid.cat/bridgedb, mostly because I had no idea where to put it, but wanted to put it somewhere.
So...
1. We should probably ask TPO's sysadmins to create something like https://docs.torproject.org/bridgedb, or wherever people want to use for keeping common developer documentation.
2. I think there was some sort of funding for this. I've just been doing this because I needed to understand how BridgeDB works and it was entirely undocumented when I started working on it. If someone knows who that funder is, please comment/tag this ticket as appropriate.
3. Documentation builds should probably be triggered automatically when a new signed tag is pushed to `git.torproject.org/bridgedb.git`.Developer portalhttps://gitlab.torproject.org/tpo/core/chutney/-/issues/30059Update chutney's README2020-06-27T13:18:41ZteorUpdate chutney's READMEIn legacy/trac#29729, I discovered some missing information in Chutney's README.In legacy/trac#29729, I discovered some missing information in Chutney's README.teorteorhttps://gitlab.torproject.org/tpo/network-health/metrics/website/-/issues/40004Write 'survival guide' for keeping metrics website up2023-01-23T14:53:51ZRoger DingledineWrite 'survival guide' for keeping metrics website upopara pointed out today that metrics.torproject.org was returning 503's.
I logged in to the server, saw that the server and apache were working fine, found a proxypass stanza in the apache config, noticed that there was a /home/metrics/...opara pointed out today that metrics.torproject.org was returning 503's.
I logged in to the server, saw that the server and apache were working fine, found a proxypass stanza in the apache config, noticed that there was a /home/metrics/, and looked through the end of /home/metrics/.bash_history to make some guesses about what to run to get things working again. It seems to be back and working (I did a "sudo -s -H -u metrics" because I saw karsten had run that, and then "./start-web.sh" and eventually decided to background it when it never exited.)
It would be great to make a 'survival guide' wiki page for it, like<br>
https://gitlab.torproject.org/tpo/metrics/team/-/wikis/Survival-Guides/Exit-Scanner
And then link to it from tpo/tpa/team#40045 so we can use it next time.
Thanks!https://gitlab.torproject.org/tpo/network-health/sbws/-/issues/29952Document that there is now stable branch2021-02-18T15:39:51ZjugaDocument that there is now stable branchAnd how bugfixes should be merged in the stable branch and this merged into masterAnd how bugfixes should be merged in the stable branch and this merged into mastersbws: 1.1.x-finalhttps://gitlab.torproject.org/tpo/network-health/sbws/-/issues/40001Change the references to Trac to Gitlab in the documentation2020-08-09T18:14:30ZjugaChange the references to Trac to Gitlab in the documentationsbws: 1.1.x-finaljugajugahttps://gitlab.torproject.org/tpo/network-health/sbws/-/issues/33473Document which branches developers should base their patches on2020-08-22T13:07:10ZjugaDocument which branches developers should base their patches onsbws: 1.1.x-finaljugajuga