The Tor Project issueshttps://gitlab.torproject.org/groups/tpo/-/issues2020-06-23T09:46:38Zhttps://gitlab.torproject.org/tpo/tpa/team/-/issues/40015moly should be upgraded to buster(Debian 10) or retired2020-06-23T09:46:38Zweasel (Peter Palfrader)moly should be upgraded to buster(Debian 10) or retiredhttps://gitlab.torproject.org/tpo/tpa/team/-/issues/40018vineale should be upgraded to buster(Debian 10) or retired2020-06-23T16:05:03Zweasel (Peter Palfrader)vineale should be upgraded to buster(Debian 10) or retiredhttps://gitlab.torproject.org/tpo/tpa/team/-/issues/40019scw-arm-par-01 should be upgraded to buster(Debian 10) or retired2020-06-23T19:32:59Zweasel (Peter Palfrader)scw-arm-par-01 should be upgraded to buster(Debian 10) or retiredweasel (Peter Palfrader)weasel (Peter Palfrader)https://gitlab.torproject.org/tpo/tpa/team/-/issues/40020Please refresh sysrqb's pgp key2020-06-24T14:52:17ZMatthew FinkelPlease refresh sysrqb's pgp key```
$ gpg2 -k CE1782624600EE98764C6D9CCB8FC772D1AA1D30
pub rsa4096/0xCB8FC772D1AA1D30 2014-06-26 [SC] [expires: 2020-12-20]
Key fingerprint = CE17 8262 4600 EE98 764C 6D9C CB8F C772 D1AA 1D30
uid [ unknown] Mat...```
$ gpg2 -k CE1782624600EE98764C6D9CCB8FC772D1AA1D30
pub rsa4096/0xCB8FC772D1AA1D30 2014-06-26 [SC] [expires: 2020-12-20]
Key fingerprint = CE17 8262 4600 EE98 764C 6D9C CB8F C772 D1AA 1D30
uid [ unknown] Matthew Finkel <sysrqb@torproject.org>
uid [ unknown] Matthew Finkel <Matthew.Finkel@gmail.com>
uid [ unknown] Matthew Finkel <sysrqb@protonmail.com>
uid [ unknown] Matthew Finkel <sysrqb@riseup.net>
sub rsa2048/0x0282E4E0C8F56C94 2020-06-23 [S] [expires: 2020-12-20]
sub rsa2048/0x44ADFA83E76BD9F5 2020-06-23 [E] [expires: 2020-12-20]
sub rsa2048/0xCA1E0E95A87E21A2 2020-06-23 [A] [expires: 2020-12-20]
```
[CE1782624600EE98764C6D9CCB8FC772D1AA1D30](/uploads/43e2879bc78397b19fb560f2b967e485/CE1782624600EE98764C6D9CCB8FC772D1AA1D30)
Thanks.anarcatanarcathttps://gitlab.torproject.org/tpo/tpa/team/-/issues/40032Community Guideline reminders on our mailing lists2020-09-28T18:34:49ZAlexander Færøyahf@torproject.orgCommunity Guideline reminders on our mailing listsIn the Community Council, we have discussed whether it could make sense to send an automated email every 3/6 months with a reminder on CoC/Social Contract/etc. This is inspired by our friends from the Tails project.
How would we go abou...In the Community Council, we have discussed whether it could make sense to send an automated email every 3/6 months with a reminder on CoC/Social Contract/etc. This is inspired by our friends from the Tails project.
How would we go about implementing this with our mailing lists? It's our understanding that each email list has its own set of "owners", so we would need to talk to them individually as they are the "service admins" of the given list? Once they approve, we could set up a cronjob somewhere that writes some standard text out?
How do we learn who owns which mailing lists?anarcatanarcathttps://gitlab.torproject.org/tpo/tpa/team/-/issues/40037git: Commit access for entire network team to all tpo/core repositories2020-07-22T14:19:20ZDavid Gouletdgoulet@torproject.orggit: Commit access for entire network team to all tpo/core repositoriesSince for the moment, we mirror git.tpo to Gitlab, the network team (4 people) need commit access to all tpo/core git repository. We know make it that every current member has access to these repositories.
Individuals are: `ahf, asn, dg...Since for the moment, we mirror git.tpo to Gitlab, the network team (4 people) need commit access to all tpo/core git repository. We know make it that every current member has access to these repositories.
Individuals are: `ahf, asn, dgoulet, nickm`
Repositories:
- torspec.git
- pytorctl.git
- trunnel.git
- torsocks.git
- tordnsel.git
- rpm-package.git
- fallback-scripts.git
- chutney.git
- tor.git
Some of them have all the right access for us 4 already.Alexander Færøyahf@torproject.orgAlexander Færøyahf@torproject.orghttps://gitlab.torproject.org/tpo/tpa/team/-/issues/40045Make (and update) a services table, with pointers to survival guides for each...2020-09-23T15:15:25ZRoger DingledineMake (and update) a services table, with pointers to survival guides for each serviceWe should make a table of what our services are, and which teams / people are running them.
Here's the original table:
https://trac.torproject.org/projects/tor/wiki/org/operations/services
ahf imported this table into gitlab, but it d...We should make a table of what our services are, and which teams / people are running them.
Here's the original table:
https://trac.torproject.org/projects/tor/wiki/org/operations/services
ahf imported this table into gitlab, but it doesn't seem to display:
https://gitlab.torproject.org/legacy/trac/-/wikis/org/operations/Infrastructure
I'll start with: phw just made a survival guide for check, and it is at:
https://gitlab.torproject.org/tpo/metrics/team/-/wikis/Survival-Guides/Checkanarcatanarcathttps://gitlab.torproject.org/tpo/tpa/team/-/issues/40047Please set up a new host for serving OnionPerf measurement data tarballs2020-09-28T17:50:57ZKarsten LoesingPlease set up a new host for serving OnionPerf measurement data tarballsWe'll need a host for serving OnionPerf measurement data tarballs. It should have something like 300G disk capacity. If we only have less disk capacity available, starting with 150G or 100G would be okay, if there's the option to grow th...We'll need a host for serving OnionPerf measurement data tarballs. It should have something like 300G disk capacity. If we only have less disk capacity available, starting with 150G or 100G would be okay, if there's the option to grow the disk at a later point. The disk can be slow. We're only going to store a few dozen large tarballs there. In fact, if there's an existing host with a similar purpose, we could as well store the tarballs there, in a subdirectory. All we need is links to these tarballs. Thank you!HiroHirohttps://gitlab.torproject.org/tpo/tpa/team/-/issues/40049Write access to research repository2020-10-19T16:09:07ZGusWrite access to research repositoryHi, I need write access to this repository:
https://gitweb.torproject.org/research-web.git/Hi, I need write access to this repository:
https://gitweb.torproject.org/research-web.git/Alexander Færøyahf@torproject.orgAlexander Færøyahf@torproject.orghttps://gitlab.torproject.org/tpo/tpa/team/-/issues/40113Pull Prometheus metrics from rdsys's backend process2020-12-21T15:51:17ZPhilipp Winterphw@torproject.orgPull Prometheus metrics from rdsys's backend processI just deployed the metrics of rdsys's backend and it's now time for our Prometheus instance to scrape them. As with bridgestrap, these metrics can be public.
I suggest we first add a ProxyPass directive to make them available:
```
Prox...I just deployed the metrics of rdsys's backend and it's now time for our Prometheus instance to scrape them. As with bridgestrap, these metrics can be public.
I suggest we first add a ProxyPass directive to make them available:
```
ProxyPass /rdsys-backend-metrics http://127.0.0.1:7100/metrics
ProxyPass /rdsys-backend-metrics/ http://127.0.0.1:7100/metrics
```
Once that is done, please make our Prometheus instance scrape https://bridges.torproject.org/rdsys-backend-metricsHiroHirohttps://gitlab.torproject.org/tpo/community/team/-/issues/29[Outreachy] mid-point feedback requested for Joydeep Sen Gupta2021-01-12T03:13:36ZGus[Outreachy] mid-point feedback requested for Joydeep Sen GuptaOutreachy mentors need to fill mid-point feedback.
Feedback is completely private, and will only be seen by Outreachy Organizers and Software Freedom Conservancy accounting staff. Outreachy organizers will discuss your feedback with yo...Outreachy mentors need to fill mid-point feedback.
Feedback is completely private, and will only be seen by Outreachy Organizers and Software Freedom Conservancy accounting staff. Outreachy organizers will discuss your feedback with you and draft a response with you before contacting the other person about any issues.GusGus2021-01-12https://gitlab.torproject.org/tpo/community/team/-/issues/32[Outreachy] Submit Community Team project (May - August 2021)2021-03-01T14:54:56ZGus[Outreachy] Submit Community Team project (May - August 2021)Write and submit Outreachy project to work on user documentation, user feedback, and support.
https://www.outreachy.org/communities/cfp/tor-project/
Our initial idea is to re-submit "Help Tor users" project. We should review and remove...Write and submit Outreachy project to work on user documentation, user feedback, and support.
https://www.outreachy.org/communities/cfp/tor-project/
Our initial idea is to re-submit "Help Tor users" project. We should review and remove outdated instructions.GusGus2021-03-01https://gitlab.torproject.org/tpo/tpa/team/-/issues/40063howto/gitlab: change "How to get an account?"2020-10-19T16:07:40Ztorrrrrrrrrrrrrrrrhowto/gitlab: change "How to get an account?"https://gitlab.torproject.org/tpo/tpa/team/-/wikis/howto/gitlab/#how-to-get-an-account
You should link https://gitlab.onionize.space for account requestshttps://gitlab.torproject.org/tpo/tpa/team/-/wikis/howto/gitlab/#how-to-get-an-account
You should link https://gitlab.onionize.space for account requestsanarcatanarcathttps://gitlab.torproject.org/tpo/tpa/team/-/issues/40069setup reverse DNS zonefile for new cymru PoP2021-09-16T19:36:12Zanarcatsetup reverse DNS zonefile for new cymru PoPwe have a new address space to allocate machines into. set it up properly as per https://gitlab.torproject.org/tpo/tpa/team/-/wikis/howto/dns (which also need an update)we have a new address space to allocate machines into. set it up properly as per https://gitlab.torproject.org/tpo/tpa/team/-/wikis/howto/dns (which also need an update)anarcatanarcathttps://gitlab.torproject.org/tpo/community/team/-/issues/34Community, l10n and web repositories on AnonTicket2021-04-12T13:20:37ZGusCommunity, l10n and web repositories on AnonTicketWe're testing this new fantastic tool, [Anonymous GitLab Ticketing](https://blog.torproject.org/anonymous-gitlab).
Let's list on this ticket all the repositories that we want to integrate there.
(cc. @emmapeel, @gaba)We're testing this new fantastic tool, [Anonymous GitLab Ticketing](https://blog.torproject.org/anonymous-gitlab).
Let's list on this ticket all the repositories that we want to integrate there.
(cc. @emmapeel, @gaba)GusGushttps://gitlab.torproject.org/tpo/tpa/team/-/issues/40070Create/provide access to a VM for running Tor Browser integration tests2020-11-08T20:43:46ZGeorg KoppenCreate/provide access to a VM for running Tor Browser integration testsacat recently finished fixing our Tor Browser integration tests so that
they are running properly for Linux bundles again. We contacted boklm
but the old VM he was using is not available anymore. So, we either need
a new one or just use ...acat recently finished fixing our Tor Browser integration tests so that
they are running properly for Linux bundles again. We contacted boklm
but the old VM he was using is not available anymore. So, we either need
a new one or just use an existing one as the requirements for running
our tests are not particularly high. What we need:
1. acat, sysrqb, and gk would need access to that VM to be able to
update tests, debug issues etc.
1. Our tests are in our `tor-browser-bundle-testsuite` repository. So,
we would need to clone that one and then someone with sudo powers need
to install packages as specified in `install-deps`
1. As to RAM and CPU requirements I think essentially anything might do it
1. OS should be Debian stable, 64bit.
1. Hard disk requirements are low, too. 5GiB should be plenty in
particular as we would start with running the tests for en-US bundles
only in the beginning anyway and the test reports are not large.
1. The system should be able to send mail to acat, sysrqb, and gk for
test result notifications.
cc @acat, @sysrqb, @boklmanarcatanarcathttps://gitlab.torproject.org/tpo/tpa/team/-/issues/40067install chi-node-03 at cymru2021-09-16T19:35:23Zanarcatinstall chi-node-03 at cymruby now this is routine: merge the cluster with the other two nodes.by now this is routine: merge the cluster with the other two nodes.anarcatanarcathttps://gitlab.torproject.org/tpo/tpa/team/-/issues/34436document the static mirror network and onionbalance system better2020-12-01T15:31:36Zanarcatdocument the static mirror network and onionbalance system betterwe have some documentation on the static mirroring system here:
https://help.torproject.org/tsa/howto/static-component/
it's mostly procedural and minimal: add a component, remove a component and that's it. it doesn't explain at all ho...we have some documentation on the static mirroring system here:
https://help.torproject.org/tsa/howto/static-component/
it's mostly procedural and minimal: add a component, remove a component and that's it. it doesn't explain at all how the system works, how to create or remove a new node in the network, how onion services interact with it, and how it actually works in puppet.
all this should be better documented. for example, I should be able to resolve legacy/trac#34396 without asking weasel. :)anarcatanarcathttps://gitlab.torproject.org/tpo/tpa/team/-/issues/40068install chi-node-04 at cymru2021-09-16T19:35:28Zanarcatinstall chi-node-04 at cymruanarcatanarcathttps://gitlab.torproject.org/tpo/tpa/team/-/issues/40065install chi-node-01 at cymru2021-09-16T19:35:08Zanarcatinstall chi-node-01 at cymruthis involves fixing borrowing from the new-machine-hetzner-robot install procedures and fixing our fabric installer to support it.
setting up the ganeti cluster will come later, first we just want a machine already.this involves fixing borrowing from the new-machine-hetzner-robot install procedures and fixing our fabric installer to support it.
setting up the ganeti cluster will come later, first we just want a machine already.anarcatanarcat