Trac issueshttps://gitlab.torproject.org/legacy/trac/-/issues2020-06-13T17:41:30Zhttps://gitlab.torproject.org/legacy/trac/-/issues/34189tbb-testsuite: fix the settings test for 782020-06-13T17:41:30ZAlex Catarineutbb-testsuite: fix the settings test for 78We should fix the settings tests so that it passes with the preferences that we currently have.We should fix the settings tests so that it passes with the preferences that we currently have.https://gitlab.torproject.org/legacy/trac/-/issues/34188Cleanup extensions.* prefs2020-06-16T01:13:00ZAlex CatarineuCleanup extensions.* prefsThere are several `extensions.*` prefs that are not needed anymore, such as `extensions.enabledAddons`, `extensions.enabledItems` or `extensions.legacy.exceptions`. We should take a look and remove the ones we do not need anymore.There are several `extensions.*` prefs that are not needed anymore, such as `extensions.enabledAddons`, `extensions.enabledItems` or `extensions.legacy.exceptions`. We should take a look and remove the ones we do not need anymore.https://gitlab.torproject.org/legacy/trac/-/issues/34187Update zlib build script to pick up new android toolchain2020-06-16T01:26:25ZGeorg KoppenUpdate zlib build script to pick up new android toolchainIt seems in order to pick up the new android toolchain we need to update our `zlib` project as well.It seems in order to pick up the new android toolchain we need to update our `zlib` project as well.Georg KoppenGeorg Koppenhttps://gitlab.torproject.org/legacy/trac/-/issues/34186Clean up spam doc2020-06-13T17:37:33ZTracClean up spam dochttps://trac.torproject.org/projects/tor/wiki/.onion
What is this?
**Trac**:
**Username**: identicalhttps://trac.torproject.org/projects/tor/wiki/.onion
What is this?
**Trac**:
**Username**: identicalGusGushttps://gitlab.torproject.org/legacy/trac/-/issues/34185ganeti clusters don't like automatic upgrades2020-06-13T17:02:12Zanarcatganeti clusters don't like automatic upgradesthis weekend the ganeti cluster had a partial outage: nodes were reachable, but networking was broken on all instances.
this is, presumably, because of the Debian buster point release that occured on saturday (!). last time this happene...this weekend the ganeti cluster had a partial outage: nodes were reachable, but networking was broken on all instances.
this is, presumably, because of the Debian buster point release that occured on saturday (!). last time this happened, weasel identified openvswitch as the culprit, and hiro deployed a fix that would make it survive such situations. but either something else came up or the fix didn't work, because the problem happened again this weekend.
i fixed it by rebooting all nodes forcibly (without migrating first).HiroHirohttps://gitlab.torproject.org/legacy/trac/-/issues/34184Deploy notifications for auto-rebasing failures2020-06-16T01:12:59ZMatthew FinkelDeploy notifications for auto-rebasing failuresConfigure alerts to notify the Tor Browser team when automatic rebasing of patches failsConfigure alerts to notify the Tor Browser team when automatic rebasing of patches failshttps://gitlab.torproject.org/legacy/trac/-/issues/34183Implement auto-rebasing tooling2020-06-16T01:12:59ZMatthew FinkelImplement auto-rebasing toolingImplement tooling, (e.g. quilt, gbp-pq) that similar projects (e.g., Tails) use to automate these kinds of code rebase tasks.Implement tooling, (e.g. quilt, gbp-pq) that similar projects (e.g., Tails) use to automate these kinds of code rebase tasks.https://gitlab.torproject.org/legacy/trac/-/issues/34182Write new integration tests for Tor Browser based on Fenix based on O1.22020-06-13T17:41:30ZMatthew FinkelWrite new integration tests for Tor Browser based on Fenix based on O1.2Add new tests.Add new tests.cypherpunkscypherpunkshttps://gitlab.torproject.org/legacy/trac/-/issues/34181Fix broken Fenix tests2020-06-15T23:01:25ZMatthew FinkelFix broken Fenix testshttps://gitlab.torproject.org/legacy/trac/-/issues/34180Add support for Fenix into existing Tor Browser regression and integration tests2020-06-16T01:12:59ZMatthew FinkelAdd support for Fenix into existing Tor Browser regression and integration testsIntegrate Fenix into test suiteIntegrate Fenix into test suitehttps://gitlab.torproject.org/legacy/trac/-/issues/34179Test migration logic from Fennec to Fenix2020-06-15T23:01:24ZMatthew FinkelTest migration logic from Fennec to FenixImplement and test migration logic to allow users to seamlessly upgrade from Tor Browser for Android based on Gecko to Tor Browser for Android based on Fenix.Implement and test migration logic to allow users to seamlessly upgrade from Tor Browser for Android based on Gecko to Tor Browser for Android based on Fenix.https://gitlab.torproject.org/legacy/trac/-/issues/34178Implement new UI changes as determined in O2.12020-06-16T01:12:58ZMatthew FinkelImplement new UI changes as determined in O2.1Update the Tor Browser for Android codebase to use Fenix instead of Fennec.Update the Tor Browser for Android codebase to use Fenix instead of Fennec.https://gitlab.torproject.org/legacy/trac/-/issues/34177Audit Fenix code for tracking, fingerprintability, and safety features2020-07-19T04:47:38ZMatthew FinkelAudit Fenix code for tracking, fingerprintability, and safety featuresAudit Fenix code for tracking, fingerprintability, and Tor safety features in relation to various known attacks.
- Audit code changes since last audit for proxy bypass bugs, following our audit procedure.Audit Fenix code for tracking, fingerprintability, and Tor safety features in relation to various known attacks.
- Audit code changes since last audit for proxy bypass bugs, following our audit procedure.https://gitlab.torproject.org/legacy/trac/-/issues/34176Tor Browser Nightly external server support2020-06-13T17:02:11ZMatthew FinkelTor Browser Nightly external server supportRelated to #33948 and (tangentially) #34122: we'll rent an external server until the technical blockers of #34122 are resolved. Should I work directly with accounting on obtaining this server and managing it? Or should TPA be involved in...Related to #33948 and (tangentially) #34122: we'll rent an external server until the technical blockers of #34122 are resolved. Should I work directly with accounting on obtaining this server and managing it? Or should TPA be involved in this process and help manage/maintain the OS?
Thankshttps://gitlab.torproject.org/legacy/trac/-/issues/34175spam attack on trac2020-06-13T17:02:10Zanarcatspam attack on traca few tickets from the cypherpunks account are being vandalized with obscene content and spam.a few tickets from the cypherpunks account are being vandalized with obscene content and spam.Jens KubiezielJens Kubiezielhttps://gitlab.torproject.org/legacy/trac/-/issues/34174Update majus errors recipient2020-06-13T17:02:09ZAntonelaantonela@torproject.orgUpdate majus errors recipientWe got some outage this weekend and I got a dozen errors from Transifex. Emmapeel kindly checked if someone was receiving the server error messages for those alerts.
Could we update the recipient of this alert so someone that can take a...We got some outage this weekend and I got a dozen errors from Transifex. Emmapeel kindly checked if someone was receiving the server error messages for those alerts.
Could we update the recipient of this alert so someone that can take action and also remove emmapeel?
---
Asunto: Cron <translation@majus> /srv/translation.torproject.org/tools/update_translations
Fecha: Mon, 11 May 2020 11:47:16 +0000 (UTC)
De: Cron Daemon <root@majus.torproject.org>
Para: emmapeel@torproject.org
---
Asunto: PROBLEM Service Alert: majus/translation cron - stuck is CRITICAL
Fecha: Mon, 11 May 2020 08:10:10 +0000 (UTC)
De: nagios@hetzner-hel1-01.torproject.org
Para: emmapeel@torproject.organarcatanarcathttps://gitlab.torproject.org/legacy/trac/-/issues/34173prevent cypherpunks from editing old comments2020-06-13T17:02:09Zcypherpunksprevent cypherpunks from editing old commentsSomeone is using the cypherpunks account to edit old comments from other cypherpunks.
Please remove this possibility, and disable cypherpunks account until this is done.Someone is using the cypherpunks account to edit old comments from other cypherpunks.
Please remove this possibility, and disable cypherpunks account until this is done.Jens KubiezielJens Kubiezielhttps://gitlab.torproject.org/legacy/trac/-/issues/34171possible single circuit maximum transfer rate regression in typical circuit p...2020-06-13T15:53:31Zstarlightpossible single circuit maximum transfer rate regression in typical circuit path casesIn late 2018 at the time 0.3.4 phased in the maximum transfer rate for single circuits dropped sharply. A performance regression appears likely imo.In late 2018 at the time 0.3.4 phased in the maximum transfer rate for single circuits dropped sharply. A performance regression appears likely imo.https://gitlab.torproject.org/legacy/trac/-/issues/34169alert Trac abuse2020-06-13T17:02:08Zcypherpunksalert Trac abuseTickets. I do not want to link. Attention **Please turn off images in your browser!** Before!
Qbi. Sorry to need notice again. You job is hard :( This cat and mouse bullshit just trying to steal time and trying to lead our attention fro...Tickets. I do not want to link. Attention **Please turn off images in your browser!** Before!
Qbi. Sorry to need notice again. You job is hard :( This cat and mouse bullshit just trying to steal time and trying to lead our attention from something away. I believe.Jens KubiezielJens Kubiezielhttps://gitlab.torproject.org/legacy/trac/-/issues/34167PublishServerDescriptor via IPv62020-06-13T15:53:30ZTracPublishServerDescriptor via IPv6let my relay node configurable by what protocol the upload to authorities is done. similiar to
```
PublishServerDescriptor
```
option.
perhaps add option like
```
PublishServerDescriptorProtocol auto|4|6|or
# This option specifi...let my relay node configurable by what protocol the upload to authorities is done. similiar to
```
PublishServerDescriptor
```
option.
perhaps add option like
```
PublishServerDescriptorProtocol auto|4|6|or
# This option specifies how descriptors Tor will publish when acting as
# a relay. You can
# choose multiple arguments, separated by commas.
#
# If this option is set to 4, Tor will publish its
# descriptors to any directories over IPv4. (This is useful if you're not IPv6 connectable
# out your server, or if you're using a IPv6 Translation Tunnel)
# Otherwise, Tor will publish its
# descriptors via IPv6. The default is "auto", which
# means "if running as a relay or bridge, publish descriptors to the
# appropriate authorities over what's reachable". Other possibilities are "or", meaning
# "publish as if you're a OnionService", "publish over onion circuit".
```
_may Sponsor55 or prop311-prop313 already covered if i missed or could be relevant for_
**Trac**:
**Username**: ϲypherpunksTor: unspecified