The Tor Project issueshttps://gitlab.torproject.org/groups/tpo/-/issues2020-06-27T13:53:56Zhttps://gitlab.torproject.org/tpo/core/tor/-/issues/25502Report intermediate PT bootstrapping status2020-06-27T13:53:56ZAlexander Færøyahf@torproject.orgReport intermediate PT bootstrapping statusParent ticket for all tickets about reporting intermediate PT bootstrap progress.Parent ticket for all tickets about reporting intermediate PT bootstrap progress.Tor: 0.4.0.x-finalAlexander Færøyahf@torproject.orgAlexander Færøyahf@torproject.orghttps://gitlab.torproject.org/tpo/core/tor/-/issues/27104report intermediate status when building application circuits2020-07-28T22:41:58ZTaylor Yureport intermediate status when building application circuitsDuring bootstrap, some minimum number of application circuits must be established before bootstrapping will complete. Right now, the user will receive no feedback of intermediate progress as a bootstrap circuit is being built. We shoul...During bootstrap, some minimum number of application circuits must be established before bootstrapping will complete. Right now, the user will receive no feedback of intermediate progress as a bootstrap circuit is being built. We should make this more granular, probably with intermediate progress at each EXTEND, to make visible when Tor is being slow to build circuits.Tor: unspecifiedhttps://gitlab.torproject.org/tpo/team/-/issues/200report on s145 for July2023-08-07T18:36:14ZGabagaba@torproject.orgreport on s145 for July2023-08-07https://gitlab.torproject.org/tpo/anti-censorship/censorship-analysis/-/issues/25966Report on Tor in the UAE (and question about Snowflake)2021-03-10T14:18:04ZTracReport on Tor in the UAE (and question about Snowflake)Early in '17, Tor stopped working. Turned out, they'd turned on blocking, but obfs4 worked. Then obfs4 stopped, and someone suggested I try Snowflake, which worked back then. But Snowflake stopped working one day, and I learned it was al...Early in '17, Tor stopped working. Turned out, they'd turned on blocking, but obfs4 worked. Then obfs4 stopped, and someone suggested I try Snowflake, which worked back then. But Snowflake stopped working one day, and I learned it was alpha, and not well supported, so I switched to meek. Now I can't get Snowflake to work at all (Tor doesn't even load), but obfs4 is working again, and seems to work much better than meek.
**Trac**:
**Username**: mwolfeDavid Fifielddcf@torproject.orgDavid Fifielddcf@torproject.orghttps://gitlab.torproject.org/tpo/core/arti/-/issues/1083Report onion service status2024-02-19T17:19:39ZNick MathewsonReport onion service statusI've started working on a branch to report `OnionServiceStatus` events from an onion service. But before I get too much farther I'd like to figure out what we actually want the status object to look like.
As far as I can tell, this mig...I've started working on a branch to report `OnionServiceStatus` events from an onion service. But before I get too much farther I'd like to figure out what we actually want the status object to look like.
As far as I can tell, this might be as simple as:
```
enum State {
/// We have been offline, or we just initialized. We are trying to publish
/// and haven't hit any significant problems yet.
Bootstrapping,
/// Publication has been successful
Running,
/// We have encountered a problem (like a dead intro point) and are recovering
/// from it and have not yet failed.
Recovering, // <--- not sure about this one.
/// There is a problem with this onion service from which we have not been
/// able to recover
Broken,
}
impl OnionServiceStatus {
pub fn state(&self) -> State;
pub fn current_problem(&self) -> Option<&tor_hsservice::Error>
}
```
@gabi-250 @diziet Please refine?
----
Also, once we have support externally provisioned keys, we will want to have a way to tell the user, "We are not yet in trouble because of missing key X, but we will need it soon." I am not sure if that is a new `State`, or if it is orthogonal.
----
(Also: There is other data we might want to eventually expose from an onion service, like: the total number of incoming connections received, the fraction of incoming connections rejected, the number of active introduction points, the fraction of directories we've been able to publish to, how many active blinded identities we have, etc. I suggest that we should _not_ include these in `OnionServiceStatus`.)
----
Also see `TODO (#1083)` comments in the code!Arti: Onion service supportgabi-250gabi-250https://gitlab.torproject.org/tpo/network-health/metrics/relay-search/-/issues/40005Report overload descriptor line information on relay search2021-09-23T14:06:05ZGeorg KoppenReport overload descriptor line information on relay searchWith the [overload part of prop 328 implemented](https://gitlab.torproject.org/tpo/core/tor/-/issues/40222) we start to get information about various relay overload situations. We should decide which we want to make visible on relay sear...With the [overload part of prop 328 implemented](https://gitlab.torproject.org/tpo/core/tor/-/issues/40222) we start to get information about various relay overload situations. We should decide which we want to make visible on relay search and then implement that.
- metrics-lib support for overload-ratelimits
- onionoo support for overload-ratelimits line
- overload-ratelimits line parsing in metrics codeHiroHirohttps://gitlab.torproject.org/tpo/network-health/sbws/-/issues/28566Report relays that sbws sees in the consensus, but never chooses to test2020-06-27T13:41:30ZteorReport relays that sbws sees in the consensus, but never chooses to testWe should count:
* the number of consensuses that sbws has seen a relay in the consensus
* the number of times sbws chooses to test a relay
* the number of times sbws chooses to exclude a relay (for example, because it's an authority)
I...We should count:
* the number of consensuses that sbws has seen a relay in the consensus
* the number of times sbws chooses to test a relay
* the number of times sbws chooses to exclude a relay (for example, because it's an authority)
If there are a large number of exclusions, we should split the exclusions into subcategories.sbws: 1.1.x-finaljugajugahttps://gitlab.torproject.org/tpo/network-health/sbws/-/issues/28567Report relays that sbws wants to test, but the test doesn't work2020-06-27T13:41:30ZteorReport relays that sbws wants to test, but the test doesn't workWe should count:
* the number of times sbws tries to test a relay
* the number of times the test works and fails
If there is a high number of failures, we should also count:
* the number of times that pair selection works and fails
* th...We should count:
* the number of times sbws tries to test a relay
* the number of times the test works and fails
If there is a high number of failures, we should also count:
* the number of times that pair selection works and fails
* the number of times that connecting works and fails
* if there are a lot of these, count the hop that fails
* the number of times that data transfer works and failssbws: 1.1.x-finaljugajugahttps://gitlab.torproject.org/tpo/network-health/sbws/-/issues/30728Report the time of the earliest eligible bandwidth measurement for each relay2022-02-17T10:40:25ZteorReport the time of the earliest eligible bandwidth measurement for each relayWe have "time=" for the latest measurement, but it would also be helpful to know the earliest measurement.We have "time=" for the latest measurement, but it would also be helpful to know the earliest measurement.sbws: unspecifiedhttps://gitlab.torproject.org/tpo/core/tor/-/issues/3723Report version of bwscanners in votes2020-06-27T14:07:56ZMike PerryReport version of bwscanners in votesEach directory authority should list the git version of the bandwidth scanners in their votes. This ticket has two parts:
1. Edit aggregate.py to output a line with the git commit that it is from.
2. Alter the tor voting to add an "opt...Each directory authority should list the git version of the bandwidth scanners in their votes. This ticket has two parts:
1. Edit aggregate.py to output a line with the git commit that it is from.
2. Alter the tor voting to add an "opt" line or other ignored keyword that lists the version from the bwscan file.
There should be no consensus process for this. We just want a comment in the vote documents, basically.Tor: 0.3.5.x-finalhttps://gitlab.torproject.org/tpo/core/tor/-/issues/1564Reported dirreq-v3-stats are 0.00%2020-06-27T14:09:25ZKarsten LoesingReported dirreq-v3-stats are 0.00%Since late May 2010, the dirreq-v3-stats that directory mirrors report are very low or even 0.00%. Mike has identified the cause for this bug:
> For the love of Chaos, router_get_my_share_of_directory_requests() is
> the dirtiest hack I...Since late May 2010, the dirreq-v3-stats that directory mirrors report are very low or even 0.00%. Mike has identified the cause for this bug:
> For the love of Chaos, router_get_my_share_of_directory_requests() is
> the dirtiest hack I've seen in a while, no wonder it broke :)
>
> Your problem is that the global variables you rely on are not set by
> smartlist_choose_by_bandwidth_weights(), which is the new
> implementation of the weighted selection algorithm. They are only set
> by smartlist_choose_by_bandwidth(). You could update
> smartlist_choose_by_bandwidth_weights() to set those variables, but
> man, there's got to be a better way :)
We should investigate new approaches to calculate directory request shares from the descriptor archives instead of believing in what directories tell us. Afterwards, we can decide whether to fix dirreq-v3-stats in Tor, or to take them out entirely.Karsten LoesingKarsten Loesinghttps://gitlab.torproject.org/tpo/network-health/metrics/tor-check/-/issues/40010Reported issue onion log not loading2022-09-28T08:48:07ZHiroReported issue onion log not loadingWe have received a report of an issue where the onion logo doesn't always work on tor check depending on the circuit used to display the page. See https://forum.torproject.net/t/tor-check-image-doesnt-always-load/4048We have received a report of an issue where the onion logo doesn't always work on tor check depending on the circuit used to display the page. See https://forum.torproject.net/t/tor-check-image-doesnt-always-load/4048https://gitlab.torproject.org/tpo/anti-censorship/censorship-analysis/-/issues/40025Reported MITM on gitlab.torproject.org on Megafon in Russia2022-04-07T16:12:27ZNick MathewsonReported MITM on gitlab.torproject.org on Megafon in RussiaOn tor-security, a user reports:
```
ISP Megafon uses the attached cert.
gitlab.torproject.org uses an invalid security certificate. The certificate is not trusted because it is self-signed. The certificate is only valid for 10.83.250....On tor-security, a user reports:
```
ISP Megafon uses the attached cert.
gitlab.torproject.org uses an invalid security certificate. The certificate is not trusted because it is self-signed. The certificate is only valid for 10.83.250.4 (Error code: sec_error_unknown_issuer)
```
[certificate.crt](/uploads/1c747beb2071b18e7c52d1ded48c9e80/certificate.crt)
And then they reported:
```
GET / HTTP/1.1
Host: torproject.org
User-Agent:
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-US,en;q=0.5
Accept-Encoding: gzip, deflate, br
DNT: 1
Connection: keep-alive
HTTP/1.1 302 Found
Location: http://m.megafonpro.ru/rkn?channel=2m
```
I don't know how useful this is, so I'm passing it on. I'm not sure how sensitive this is, so I'm marking it confidential. Feel free to make it public if you determine that there's nothing private in the cert. I can give you the user's email on request offline, if you want to reach out to them.
Cheers!https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/41701Reporting an extension does not work2023-04-17T20:28:39ZrichardReporting an extension does not workIn about:addons the report extension button results in an HTTP 400 error, presumaby because we are claiming to be tor-browser rather than firefox.
This button can be disabled with the `extensions.abuseReport.enabled` pref to `false`.In about:addons the report extension button results in an HTTP 400 error, presumaby because we are claiming to be tor-browser rather than firefox.
This button can be disabled with the `extensions.abuseReport.enabled` pref to `false`.richardrichardhttps://gitlab.torproject.org/tpo/applications/mullvad-browser/-/issues/127Reporting an extension doesn't work2023-03-29T14:20:28ZruihildtReporting an extension doesn't work1. the title of the report box is `Report This Extension to Mullvad`, which is incorrect
1. it's not working anyway :dancer:
1. do we need reporting?
I checked on Tor Browser, and 1) is also an issue, even though the reporting function...1. the title of the report box is `Report This Extension to Mullvad`, which is incorrect
1. it's not working anyway :dancer:
1. do we need reporting?
I checked on Tor Browser, and 1) is also an issue, even though the reporting function seems to work.
![report-extension](/uploads/f635a1c0d35c83c5585da3d5e43712fd/report-extension.mp4)https://gitlab.torproject.org/tpo/core/tor/-/issues/10673Reporting Error Msgs2020-06-27T14:03:31ZTracReporting Error Msgs[Mon Jan 20 04:17:56 2014] Tor Software Error - The Tor software encountered an internal bug. Please report the following error message to the Tor developers at bugs.torproject.org: "microdesc_free(): Bug: microdesc_free() called, but md...[Mon Jan 20 04:17:56 2014] Tor Software Error - The Tor software encountered an internal bug. Please report the following error message to the Tor developers at bugs.torproject.org: "microdesc_free(): Bug: microdesc_free() called, but md was still referenced 1 node(s); held_by_nodes == 1
"
[Mon Jan 20 04:17:56 2014] Tor Software Error - The Tor software encountered an internal bug. Please report the following error message to the Tor developers at bugs.torproject.org: "microdesc_free(): Bug: microdesc_free() called, but md was still referenced 1 node(s); held_by_nodes == 1
"
[Mon Jan 20 04:17:56 2014] Tor Software Error - The Tor software encountered an internal bug. Please report the following error message to the Tor developers at bugs.torproject.org: "microdesc_free(): Bug: microdesc_free() called, but md was still referenced 1 node(s); held_by_nodes == 1
"
**Trac**:
**Username**: Cheerful1https://gitlab.torproject.org/tpo/team/-/issues/64Reports for funders for Q2 20222022-07-27T22:30:03ZGabagaba@torproject.orgReports for funders for Q2 2022- Sponsor 28
- [x] Start pad
- [x] Review
- [x] Send to Bekeela
- Sponsor 30
- [x] Start pad
- [x] Review
- [x] Send to Bekeela
- Sponsor 61
- [x] Start pad
- [x] Review
- [x] Send to Bekeela
- Sponsor 96
- [x] Start ...- Sponsor 28
- [x] Start pad
- [x] Review
- [x] Send to Bekeela
- Sponsor 30
- [x] Start pad
- [x] Review
- [x] Send to Bekeela
- Sponsor 61
- [x] Start pad
- [x] Review
- [x] Send to Bekeela
- Sponsor 96
- [x] Start pad
- [x] Review
- [x] Send to Bekeela
- Sponsor 101
- [x] Start pad
- [x] Review
- [x] Send to Bekeela
- Sponsor 123
- [x] Review
- [x] Send to Bekeela
- Sponsor 125
- [x] Start pad
- [x] Review
- [x] Send to BekeelaGabagaba@torproject.orgGabagaba@torproject.org2022-07-25https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/issues/33038Represent timeouts using time.Duration2020-06-27T13:40:16ZDavid Fifielddcf@torproject.orgRepresent timeouts using time.DurationRepresenting these constants in `time.Duration` form is more semantic, and allows rewriting
```
if time.Since(start).Seconds() > myTimeout {
```
as
```
if time.Since(start) > myTimeout {
```
One side effect is that `Printf` formatting [...Representing these constants in `time.Duration` form is more semantic, and allows rewriting
```
if time.Since(start).Seconds() > myTimeout {
```
as
```
if time.Since(start) > myTimeout {
```
One side effect is that `Printf` formatting [renders](https://golang.org/pkg/time/#Duration.String) a `time.Duration` as a string like `10s` or `100ms`, which changes some log messages slightly. If we need compatibility of log message formats, we could use `.Seconds()` in those places.David Fifielddcf@torproject.orgDavid Fifielddcf@torproject.orghttps://gitlab.torproject.org/tpo/core/arti/-/issues/378repro build sometime gives wrong branch and commit id in build summary2022-03-04T19:52:19Ztrinity-1686arepro build sometime gives wrong branch and commit id in build summaryfor instance, see the result of [this job](https://gitlab.torproject.org/tpo/core/arti/-/jobs/105570#L1191)
This branch and commit are actually from osxcross. I think when we build the cross toolchain, we cd in, but never out, of osxcr...for instance, see the result of [this job](https://gitlab.torproject.org/tpo/core/arti/-/jobs/105570#L1191)
This branch and commit are actually from osxcross. I think when we build the cross toolchain, we cd in, but never out, of osxcross, so git metadata are from this repository instead of being from arti.https://gitlab.torproject.org/tpo/network-health/metrics/website/-/issues/40068Reprocess metrics on the website for the clients stats module2022-10-28T15:38:31ZHiroReprocess metrics on the website for the clients stats moduleWhile deploying a fix for a few spikes "formed" in our metrics. These were probably due from having to reprocessing the data a few times for the same period of time.
The solution to this is:
1. Delete the data for the affected days.
2. ...While deploying a fix for a few spikes "formed" in our metrics. These were probably due from having to reprocessing the data a few times for the same period of time.
The solution to this is:
1. Delete the data for the affected days.
2. Re-parse the data for the missing and "spike" days for https://metrics.torproject.org/userstats-relay-country.html
The affected days are 29/30 30/09 01/10 02/10 03/10 04/10 05/10
https://metrics.torproject.org/userstats-relay-country.html?start=2022-09-25&end=2022-10-10&country=all&events=offHiroHiro