The Tor Project issueshttps://gitlab.torproject.org/groups/tpo/-/issues2020-07-24T13:39:18Zhttps://gitlab.torproject.org/tpo/core/tor/-/issues/6504Support Windows environment variables in HiddenServiceDir2020-07-24T13:39:18ZTracSupport Windows environment variables in HiddenServiceDirExpansion should be done each time the hidden service dir is opened, and stored unexpanded. Actually, my impression is that if you use the right Win32 API calls to open the location, tor itself doesn't need to worry about expansion. Win3...Expansion should be done each time the hidden service dir is opened, and stored unexpanded. Actually, my impression is that if you use the right Win32 API calls to open the location, tor itself doesn't need to worry about expansion. Win32 will take care of any necessary.
One direct benefit to you devs is that you could then use '%UserProfile%' in the HiddenServiceDir examples for Windows in your documentation, such as the one discussed in !legacy/trac#4798, yielding the appropriate location in every version that Tor supports.
This behavior could/should eventually broadened to all options for which a path can be specified (e.g. DataDirectory, GeoIPFile, PidFile), so if the fix would affect the opening of other paths (I haven't looked through the source code), all the better. If the fix isn't in a core function, I'd be happy to add a new, broader, ticket.
P.S. The version I'm using is actually 0.2.2.37, but I don't see it in the list.
**Trac**:
**Username**: criticoderTor: unspecifiedhttps://gitlab.torproject.org/tpo/core/tor/-/issues/3943self-test the socks port before bootstrapping is complete?2020-06-27T14:07:46ZRoger Dingledineself-test the socks port before bootstrapping is complete?Some users (e.g. those in legacy/trac#3941) have local firewalls that will let them open a high numbered port, but not let any applications connect to it. When we set 'socksport auto' for them, they can end up in this situation.
One opt...Some users (e.g. those in legacy/trac#3941) have local firewalls that will let them open a high numbered port, but not let any applications connect to it. When we set 'socksport auto' for them, they can end up in this situation.
One option would be for Tor to make a socks connection to itself on the socksport it just opened, and make a connection to .noconnect or the equivalent (which I believe we disabled for no good reason, but that's a separate issue). If that test fails, log a more useful error and prevent bootstrapping from reaching 100%.
(The socksport test can happen in parallel to the rest of bootstrapping, so in all reasonable cases it shouldn't be holding anything up.)
It's unclear to me how often this feature will be useful in practice -- for example, perhaps the firewalls that prevent apps from reaching these ports would still allow the app that bound the port to reach it.
But it seems like the sort of feature that will come in handy down the road when debugging weird firewall situations. And the weird firewalls sure aren't going to go away anytime soon.Tor: unspecifiedhttps://gitlab.torproject.org/tpo/core/tor/-/issues/3266gabelmoo publishes only 1 extra-info descriptor per week2020-06-27T14:08:16ZKarsten Loesinggabelmoo publishes only 1 extra-info descriptor per weekI noticed that gabelmoo started publishing exactly 1 extra-info descriptor per **week** a couple of weeks ago. Here are the number of server descriptors and extra-info descriptors that gabelmoo published per day in 2011:
```
date ...I noticed that gabelmoo started publishing exactly 1 extra-info descriptor per **week** a couple of weeks ago. Here are the number of server descriptors and extra-info descriptors that gabelmoo published per day in 2011:
```
date | platform | serverdescs | extrainfos
------------+-----------------------------------------------------------+-------------+------------
2011-01-01 | Tor 0.2.2.20-alpha (git-aae58deb2cdcaad0) on Linux x86_64 | 2 | 2
2011-01-02 | Tor 0.2.2.20-alpha (git-aae58deb2cdcaad0) on Linux x86_64 | 1 | 1
2011-01-03 | Tor 0.2.2.20-alpha (git-aae58deb2cdcaad0) on Linux x86_64 | 1 | 1
2011-01-04 | Tor 0.2.2.20-alpha (git-aae58deb2cdcaad0) on Linux x86_64 | 2 | 2
2011-01-05 | Tor 0.2.2.20-alpha (git-aae58deb2cdcaad0) on Linux x86_64 | 1 | 1
2011-01-06 | Tor 0.2.2.20-alpha (git-aae58deb2cdcaad0) on Linux x86_64 | 1 | 1
2011-01-07 | Tor 0.2.2.20-alpha (git-aae58deb2cdcaad0) on Linux x86_64 | 1 | 1
2011-01-08 | Tor 0.2.2.20-alpha (git-aae58deb2cdcaad0) on Linux x86_64 | 2 | 2
2011-01-09 | Tor 0.2.2.20-alpha (git-aae58deb2cdcaad0) on Linux x86_64 | 1 | 1
2011-01-10 | Tor 0.2.2.20-alpha (git-aae58deb2cdcaad0) on Linux x86_64 | 1 | 1
2011-01-11 | Tor 0.2.2.20-alpha (git-aae58deb2cdcaad0) on Linux x86_64 | 2 | 2
2011-01-12 | Tor 0.2.2.20-alpha (git-aae58deb2cdcaad0) on Linux x86_64 | 2 | 2
2011-01-13 | Tor 0.2.2.20-alpha (git-aae58deb2cdcaad0) on Linux x86_64 | 1 | 1
2011-01-14 | Tor 0.2.2.20-alpha (git-aae58deb2cdcaad0) on Linux x86_64 | 1 | 1
2011-01-15 | Tor 0.2.2.20-alpha (git-aae58deb2cdcaad0) on Linux x86_64 | 2 | 2
2011-01-16 | Tor 0.2.2.20-alpha (git-aae58deb2cdcaad0) on Linux x86_64 | 1 | 3
2011-01-16 | Tor 0.2.2.21-alpha (git-5f63f0d6312d9f0d) on Linux x86_64 | 2 | 3
2011-01-17 | Tor 0.2.2.21-alpha (git-5f63f0d6312d9f0d) on Linux x86_64 | 2 | 2
2011-01-18 | Tor 0.2.2.21-alpha (git-5f63f0d6312d9f0d) on Linux x86_64 | 4 | 3
2011-01-19 | Tor 0.2.2.21-alpha (git-5f63f0d6312d9f0d) on Linux x86_64 | 2 | 2
2011-01-20 | Tor 0.2.2.21-alpha (git-5f63f0d6312d9f0d) on Linux x86_64 | 1 | 1
2011-01-21 | Tor 0.2.2.21-alpha (git-5f63f0d6312d9f0d) on Linux x86_64 | 1 | 3
2011-01-21 | Tor 0.2.2.19-alpha (git-13e9a2b19d4a65d9) on Linux x86_64 | 2 | 3
2011-01-22 | Tor 0.2.2.19-alpha (git-13e9a2b19d4a65d9) on Linux x86_64 | 2 | 2
2011-01-23 | Tor 0.2.2.19-alpha (git-13e9a2b19d4a65d9) on Linux x86_64 | 1 | 1
2011-01-24 | Tor 0.2.2.19-alpha (git-13e9a2b19d4a65d9) on Linux x86_64 | 1 | 1
2011-01-25 | Tor 0.2.2.19-alpha (git-13e9a2b19d4a65d9) on Linux x86_64 | 2 | 2
2011-01-26 | Tor 0.2.2.19-alpha (git-13e9a2b19d4a65d9) on Linux x86_64 | 2 | 2
2011-01-27 | Tor 0.2.2.19-alpha (git-13e9a2b19d4a65d9) on Linux x86_64 | 1 | 1
2011-01-28 | Tor 0.2.2.19-alpha (git-13e9a2b19d4a65d9) on Linux x86_64 | 1 | 1
2011-01-29 | Tor 0.2.2.19-alpha (git-13e9a2b19d4a65d9) on Linux x86_64 | 2 | 2
2011-01-30 | Tor 0.2.2.19-alpha (git-13e9a2b19d4a65d9) on Linux x86_64 | 1 | 1
2011-01-31 | Tor 0.2.2.19-alpha (git-13e9a2b19d4a65d9) on Linux x86_64 | 1 | 1
2011-02-01 | Tor 0.2.2.19-alpha (git-13e9a2b19d4a65d9) on Linux x86_64 | 2 | 2
2011-02-02 | Tor 0.2.2.19-alpha (git-13e9a2b19d4a65d9) on Linux x86_64 | 2 | 2
2011-02-03 | Tor 0.2.2.19-alpha (git-13e9a2b19d4a65d9) on Linux x86_64 | 1 | 5
2011-02-03 | Tor 0.2.2.22-alpha (git-e5e38e55b33b2cc0) on Linux x86_64 | 13 | 5
2011-02-04 | Tor 0.2.2.22-alpha (git-e5e38e55b33b2cc0) on Linux x86_64 | 24 | 5
2011-02-05 | Tor 0.2.2.22-alpha (git-e5e38e55b33b2cc0) on Linux x86_64 | 23 | 7
2011-02-06 | Tor 0.2.2.22-alpha (git-e5e38e55b33b2cc0) on Linux x86_64 | 24 | 6
2011-02-07 | Tor 0.2.2.22-alpha (git-e5e38e55b33b2cc0) on Linux x86_64 | 24 | 9
2011-02-08 | Tor 0.2.2.22-alpha (git-e5e38e55b33b2cc0) on Linux x86_64 | 25 | 12
2011-02-09 | Tor 0.2.2.22-alpha (git-e5e38e55b33b2cc0) on Linux x86_64 | 23 | 13
2011-02-10 | Tor 0.2.2.22-alpha (git-e5e38e55b33b2cc0) on Linux x86_64 | 24 | 13
2011-02-11 | Tor 0.2.2.22-alpha (git-e5e38e55b33b2cc0) on Linux x86_64 | 24 | 11
2011-02-12 | Tor 0.2.2.22-alpha (git-e5e38e55b33b2cc0) on Linux x86_64 | 24 | 11
2011-02-13 | Tor 0.2.2.22-alpha (git-e5e38e55b33b2cc0) on Linux x86_64 | 23 | 12
2011-02-14 | Tor 0.2.2.22-alpha (git-e5e38e55b33b2cc0) on Linux x86_64 | 24 | 11
2011-02-15 | Tor 0.2.2.22-alpha (git-e5e38e55b33b2cc0) on Linux x86_64 | 25 | 10
2011-02-16 | Tor 0.2.2.22-alpha (git-e5e38e55b33b2cc0) on Linux x86_64 | 23 | 12
2011-02-17 | Tor 0.2.2.22-alpha (git-e5e38e55b33b2cc0) on Linux x86_64 | 24 | 12
2011-02-18 | Tor 0.2.2.22-alpha (git-e5e38e55b33b2cc0) on Linux x86_64 | 24 | 11
2011-02-19 | Tor 0.2.2.22-alpha (git-e5e38e55b33b2cc0) on Linux x86_64 | 24 | 9
2011-02-20 | Tor 0.2.2.22-alpha (git-e5e38e55b33b2cc0) on Linux x86_64 | 24 | 14
2011-02-21 | Tor 0.2.2.22-alpha (git-e5e38e55b33b2cc0) on Linux x86_64 | 24 | 9
2011-02-22 | Tor 0.2.2.22-alpha (git-e5e38e55b33b2cc0) on Linux x86_64 | 25 | 11
2011-02-23 | Tor 0.2.2.22-alpha (git-e5e38e55b33b2cc0) on Linux x86_64 | 24 | 12
2011-02-24 | Tor 0.2.2.22-alpha (git-e5e38e55b33b2cc0) on Linux x86_64 | 24 | 9
2011-02-25 | Tor 0.2.2.22-alpha (git-e5e38e55b33b2cc0) on Linux x86_64 | 26 | 13
2011-02-26 | Tor 0.2.2.22-alpha (git-e5e38e55b33b2cc0) on Linux x86_64 | 25 | 11
2011-02-27 | Tor 0.2.2.22-alpha (git-e5e38e55b33b2cc0) on Linux x86_64 | 28 | 12
2011-02-28 | Tor 0.2.2.22-alpha (git-e5e38e55b33b2cc0) on Linux x86_64 | 25 | 12
2011-03-01 | Tor 0.2.2.22-alpha (git-e5e38e55b33b2cc0) on Linux x86_64 | 26 | 6
2011-03-02 | Tor 0.2.2.22-alpha (git-e5e38e55b33b2cc0) on Linux x86_64 | 24 | 5
2011-03-03 | Tor 0.2.2.22-alpha (git-e5e38e55b33b2cc0) on Linux x86_64 | 24 | 7
2011-03-04 | Tor 0.2.2.22-alpha (git-e5e38e55b33b2cc0) on Linux x86_64 | 24 | 5
2011-03-05 | Tor 0.2.2.22-alpha (git-e5e38e55b33b2cc0) on Linux x86_64 | 24 | 9
2011-03-06 | Tor 0.2.2.22-alpha (git-e5e38e55b33b2cc0) on Linux x86_64 | 10 | 4
2011-03-06 | Tor 0.2.2.19-alpha (git-35fcec38809f9805) on Linux x86_64 | 2 | 4
2011-03-07 | Tor 0.2.2.22-alpha (git-20569f9297fad087) on Linux x86_64 | 15 | 8
2011-03-08 | Tor 0.2.2.22-alpha (git-20569f9297fad087) on Linux x86_64 | 26 | 14
2011-03-09 | Tor 0.2.2.22-alpha (git-20569f9297fad087) on Linux x86_64 | 23 | 11
2011-03-10 | Tor 0.2.2.22-alpha (git-20569f9297fad087) on Linux x86_64 | 24 | 13
2011-03-11 | Tor 0.2.2.22-alpha (git-20569f9297fad087) on Linux x86_64 | 24 | 13
2011-03-12 | Tor 0.2.2.22-alpha (git-20569f9297fad087) on Linux x86_64 | 24 | 12
2011-03-13 | Tor 0.2.2.22-alpha (git-20569f9297fad087) on Linux x86_64 | 24 | 10
2011-03-14 | Tor 0.2.2.22-alpha (git-20569f9297fad087) on Linux x86_64 | 26 | 15
2011-03-15 | Tor 0.2.2.22-alpha (git-20569f9297fad087) on Linux x86_64 | 28 | 17
2011-03-16 | Tor 0.2.2.22-alpha (git-20569f9297fad087) on Linux x86_64 | 24 | 12
2011-03-17 | Tor 0.2.2.22-alpha (git-20569f9297fad087) on Linux x86_64 | 24 | 13
2011-03-18 | Tor 0.2.2.22-alpha (git-20569f9297fad087) on Linux x86_64 | 24 | 11
2011-03-19 | Tor 0.2.2.22-alpha (git-20569f9297fad087) on Linux x86_64 | 24 | 10
2011-03-20 | Tor 0.2.2.22-alpha (git-20569f9297fad087) on Linux x86_64 | 24 | 10
2011-03-21 | Tor 0.2.2.22-alpha (git-20569f9297fad087) on Linux x86_64 | 24 | 10
2011-03-22 | Tor 0.2.2.22-alpha (git-20569f9297fad087) on Linux x86_64 | 25 | 10
2011-03-23 | Tor 0.2.2.22-alpha (git-20569f9297fad087) on Linux x86_64 | 24 | 10
2011-03-24 | Tor 0.2.2.22-alpha (git-20569f9297fad087) on Linux x86_64 | 24 | 9
2011-03-25 | Tor 0.2.2.22-alpha (git-20569f9297fad087) on Linux x86_64 | 24 | 10
2011-03-26 | Tor 0.2.2.22-alpha (git-20569f9297fad087) on Linux x86_64 | 24 | 10
2011-03-27 | Tor 0.2.2.22-alpha (git-20569f9297fad087) on Linux x86_64 | 24 | 9
2011-03-28 | Tor 0.2.2.22-alpha (git-20569f9297fad087) on Linux x86_64 | 24 | 12
2011-03-29 | Tor 0.2.2.22-alpha (git-20569f9297fad087) on Linux x86_64 | 26 | 7
2011-03-30 | Tor 0.2.2.22-alpha (git-20569f9297fad087) on Linux x86_64 | 24 | 5
2011-03-31 | Tor 0.2.2.22-alpha (git-20569f9297fad087) on Linux x86_64 | 22 | 5
2011-04-01 | Tor 0.2.2.22-alpha (git-20569f9297fad087) on Linux x86_64 | 24 | 8
2011-04-02 | Tor 0.2.2.22-alpha (git-20569f9297fad087) on Linux x86_64 | 22 | 9
2011-04-03 | Tor 0.2.2.22-alpha (git-20569f9297fad087) on Linux x86_64 | 24 | 12
2011-04-04 | Tor 0.2.2.22-alpha (git-20569f9297fad087) on Linux x86_64 | 24 | 11
2011-04-05 | Tor 0.2.2.22-alpha (git-20569f9297fad087) on Linux x86_64 | 25 | 10
2011-04-06 | Tor 0.2.2.22-alpha (git-20569f9297fad087) on Linux x86_64 | 24 | 13
2011-04-07 | Tor 0.2.2.22-alpha (git-20569f9297fad087) on Linux x86_64 | 24 | 11
2011-04-08 | Tor 0.2.2.22-alpha (git-20569f9297fad087) on Linux x86_64 | 24 | 12
2011-04-09 | Tor 0.2.2.22-alpha (git-20569f9297fad087) on Linux x86_64 | 24 | 15
2011-04-10 | Tor 0.2.2.22-alpha (git-20569f9297fad087) on Linux x86_64 | 24 | 11
2011-04-11 | Tor 0.2.2.22-alpha (git-20569f9297fad087) on Linux x86_64 | 24 | 11
2011-04-12 | Tor 0.2.2.22-alpha (git-20569f9297fad087) on Linux x86_64 | 25 | 11
2011-04-13 | Tor 0.2.2.22-alpha (git-20569f9297fad087) on Linux x86_64 | 22 | 12
2011-04-14 | Tor 0.2.2.22-alpha (git-20569f9297fad087) on Linux x86_64 | 24 | 13
2011-04-15 | Tor 0.2.2.22-alpha (git-20569f9297fad087) on Linux x86_64 | 7 | 4
2011-04-16 | Tor 0.2.2.22-alpha (git-20569f9297fad087) on Linux x86_64 | 18 | 6
2011-04-17 | Tor 0.2.2.22-alpha (git-20569f9297fad087) on Linux x86_64 | 24 | 6
2011-04-18 | Tor 0.2.2.22-alpha (git-20569f9297fad087) on Linux x86_64 | 24 | 8
2011-04-19 | Tor 0.2.2.22-alpha (git-20569f9297fad087) on Linux x86_64 | 25 | 11
2011-04-20 | Tor 0.2.2.22-alpha (git-20569f9297fad087) on Linux x86_64 | 24 | 12
2011-04-21 | Tor 0.2.2.22-alpha (git-20569f9297fad087) on Linux x86_64 | 24 | 10
2011-04-22 | Tor 0.2.2.22-alpha (git-20569f9297fad087) on Linux x86_64 | 24 | 11
2011-04-23 | Tor 0.2.2.22-alpha (git-20569f9297fad087) on Linux x86_64 | 24 | 11
2011-04-24 | Tor 0.2.2.22-alpha (git-20569f9297fad087) on Linux x86_64 | 24 | 10
2011-04-25 | Tor 0.2.2.22-alpha (git-20569f9297fad087) on Linux x86_64 | 24 | 10
2011-04-26 | Tor 0.2.2.22-alpha (git-20569f9297fad087) on Linux x86_64 | 25 | 8
2011-04-27 | Tor 0.2.2.22-alpha (git-20569f9297fad087) on Linux x86_64 | 23 |
2011-04-28 | Tor 0.2.2.22-alpha (git-20569f9297fad087) on Linux x86_64 | 23 |
2011-04-29 | Tor 0.2.2.22-alpha (git-20569f9297fad087) on Linux x86_64 | 19 |
2011-04-30 | Tor 0.2.2.22-alpha (git-20569f9297fad087) on Linux x86_64 | 22 |
2011-05-01 | Tor 0.2.2.22-alpha (git-20569f9297fad087) on Linux x86_64 | 23 |
2011-05-02 | Tor 0.2.2.22-alpha (git-20569f9297fad087) on Linux x86_64 | 24 |
2011-05-03 | Tor 0.2.2.22-alpha (git-20569f9297fad087) on Linux x86_64 | 25 | 1
2011-05-04 | Tor 0.2.2.22-alpha (git-20569f9297fad087) on Linux x86_64 | 23 |
2011-05-05 | Tor 0.2.2.22-alpha (git-20569f9297fad087) on Linux x86_64 | 24 |
2011-05-06 | Tor 0.2.2.22-alpha (git-20569f9297fad087) on Linux x86_64 | 24 |
2011-05-07 | Tor 0.2.2.22-alpha (git-20569f9297fad087) on Linux x86_64 | 24 |
2011-05-08 | Tor 0.2.2.22-alpha (git-20569f9297fad087) on Linux x86_64 | 24 |
2011-05-09 | Tor 0.2.2.22-alpha (git-20569f9297fad087) on Linux x86_64 | 24 |
2011-05-10 | Tor 0.2.2.22-alpha (git-20569f9297fad087) on Linux x86_64 | 25 | 1
2011-05-11 | Tor 0.2.2.22-alpha (git-20569f9297fad087) on Linux x86_64 | 24 |
2011-05-12 | Tor 0.2.2.22-alpha (git-20569f9297fad087) on Linux x86_64 | 23 |
2011-05-13 | Tor 0.2.2.22-alpha (git-20569f9297fad087) on Linux x86_64 | 24 |
2011-05-14 | Tor 0.2.2.22-alpha (git-20569f9297fad087) on Linux x86_64 | 24 |
2011-05-15 | Tor 0.2.2.22-alpha (git-20569f9297fad087) on Linux x86_64 | 24 |
2011-05-16 | Tor 0.2.2.22-alpha (git-20569f9297fad087) on Linux x86_64 | 24 |
2011-05-17 | Tor 0.2.2.22-alpha (git-20569f9297fad087) on Linux x86_64 | 25 | 1
2011-05-18 | Tor 0.2.2.22-alpha (git-20569f9297fad087) on Linux x86_64 | 24 |
2011-05-19 | Tor 0.2.2.22-alpha (git-20569f9297fad087) on Linux x86_64 | 24 |
2011-05-20 | Tor 0.2.2.22-alpha (git-20569f9297fad087) on Linux x86_64 | 24 |
2011-05-21 | Tor 0.2.2.22-alpha (git-20569f9297fad087) on Linux x86_64 | 24 |
2011-05-22 | Tor 0.2.2.22-alpha (git-20569f9297fad087) on Linux x86_64 | 17 |
```
There are a few irregularities in this table; see also legacy/trac#3265. In this ticket, I'm mostly worried why gabelmoo started publishing only a single extra-info descriptor per week from May 3 on. The exact publication times of the last extra-info descriptors are:
```
gabelmoo | 2011-04-25 15:11:50
gabelmoo | 2011-04-25 18:11:27
gabelmoo | 2011-04-25 20:10:54
gabelmoo | 2011-04-26 03:10:27
gabelmoo | 2011-04-26 04:10:44
gabelmoo | 2011-04-26 05:12:30
gabelmoo | 2011-04-26 08:11:24
gabelmoo | 2011-04-26 08:42:22
gabelmoo | 2011-04-26 10:12:09
gabelmoo | 2011-04-26 13:11:09
gabelmoo | 2011-04-26 14:11:11
gabelmoo | 2011-05-03 08:42:15
gabelmoo | 2011-05-10 08:41:46
gabelmoo | 2011-05-17 08:41:47
```
Note the almost exact 1-week interval at the end.
It looks like gabelmoo is not the only affected relay, but it's the one with the clearest pattern.
Any idea what's going on?Tor: unspecifiedhttps://gitlab.torproject.org/tpo/core/tor/-/issues/2077Overwriting files can fail on Windows2020-07-24T12:27:48ZTracOverwriting files can fail on WindowsUsing Firefox 3.6.10, Vista x64 hm prem, SP2.
Crashes w/ older Tor versions were rare for me. Since installing alpha ver listed, several crashes in 2 days. Doing nothing diff (except later ver of Firefox). No warning / signs of thing...Using Firefox 3.6.10, Vista x64 hm prem, SP2.
Crashes w/ older Tor versions were rare for me. Since installing alpha ver listed, several crashes in 2 days. Doing nothing diff (except later ver of Firefox). No warning / signs of things going bad before get crash notice (Tor has stopped working).
These seem to be main warnings from log:
Vidala log errors:
Oct 15 12:59:21.741 [Warning] Error replacing "C:\Users\<user name>\AppData\Roaming\tor\state": File exists
Oct 15 12:59:21.743 [Warning] Unable to write state to file "C:\Users\<user name>\AppData\Roaming\tor\state"
Note: the user\AppData path is not protected - the acct I was running in Vista at time of Tor crash has full access to the paths \ files mentioned above.
The file: state.tmp DOES exist in the location mentioned.
I can open / read - state.tmp - (after Tor crash & Tor is shut down). Has no obvious errors msgs in the file.
There's another file: "lock" (w/ 0 bytes) in same folder as state.tmp (after crash & Tor / Vidalia are shut down).
Properties of the "lock" file show was created yesterday 10/14, & last mod 10/15. Its file attribs are "AN" - archived, not indexed? Other than that, no real info on it.
Err Rpt from Windows Vista x64 prepared to send to MS:
Problem signature:
Problem Event Name: APPCRASH
Application Name: tor.exe
Application Version: 0.0.0.0
Application Timestamp: 4ca65e57
Fault Module Name: tor.exe
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 4ca65e57
Exception Code: c0000005
Exception Offset: 000c3bf9
OS Version: 6.0.6002.2.2.0.768.3
Locale ID: 1033
Additional Information 1: fd00
Additional Information 2: ea6f5fe8924aaa756324d57f87834160
Additional Information 3: fd00
Additional Information 4: ea6f5fe8924aaa756324d57f87834160
**Trac**:
**Username**: joebtTor: unspecifiedhttps://gitlab.torproject.org/tpo/tpa/team/-/issues/41558grafana2.tpo: Templating [query0] Error updating options: error when executin...2024-03-19T14:06:16Zjugagrafana2.tpo: Templating [query0] Error updating options: error when executing the sql queryi'm trying to create a variable (https://grafana2.torproject.org/d/inflation-observed-gt-weight/inflation-detection-observed-gt-weight?orgId=1&from=now-30d&to=now&editview=templating&editIndex=0) from this query:
```sql
select distinct ...i'm trying to create a variable (https://grafana2.torproject.org/d/inflation-observed-gt-weight/inflation-detection-observed-gt-weight?orgId=1&from=now-30d&to=now&editview=templating&editIndex=0) from this query:
```sql
select distinct node_id from bandwidth_record group by node_id, bw, bw_mean having max(bw_mean) < max(bw * 1000.0) / 200 and bw_mean > -1
```
but i can't run the query or it returns the error.
In a local grafana instance with same datasource, the variable (and query) works
Update: typoanarcatanarcathttps://gitlab.torproject.org/tpo/network-health/tor-weather/-/issues/91Old logs should be deleted from the weather setup on weather-012024-02-21T20:38:55ZHiroOld logs should be deleted from the weather setup on weather-01Old logs should be deleted from our current deployment. Currenlty we have logs for each day the service has been running and we probably do not need that.Old logs should be deleted from our current deployment. Currenlty we have logs for each day the service has been running and we probably do not need that.https://gitlab.torproject.org/tpo/tpa/team/-/issues/41508Export rdsys based HTTPS distributor as HTTPS service at rdsys-test-01 with a...2024-02-01T14:02:40ZshelikhooExport rdsys based HTTPS distributor as HTTPS service at rdsys-test-01 with an non-production domain nameI would like to request exporting service hosted at `http://127.0.0.1:7200` at rdsys-test-01 as a https website with an non-production domain name.
Ideally, it should sanitize and supply `X-Forwarded-For` to reflect client IP address.
...I would like to request exporting service hosted at `http://127.0.0.1:7200` at rdsys-test-01 as a https website with an non-production domain name.
Ideally, it should sanitize and supply `X-Forwarded-For` to reflect client IP address.
See also: https://gitlab.torproject.org/tpo/anti-censorship/rdsys/-/issues/191 as a part of S150.anarcatanarcathttps://gitlab.torproject.org/tpo/tpa/team/-/issues/41507ExoneraTor suffering from possible denial of service2024-03-07T14:22:30ZJérôme Charaouilavamind@torproject.orgExoneraTor suffering from possible denial of serviceSince approximately the new year, it seems like ExoneraTor (hosted on `materculae`) is suffering from an unusually high load:
![Capture_d_écran_du_2024-01-30_18-26-01](/uploads/6d9c76f835b53626b2d6cb0b13628ee0/Capture_d_écran_du_2024-01...Since approximately the new year, it seems like ExoneraTor (hosted on `materculae`) is suffering from an unusually high load:
![Capture_d_écran_du_2024-01-30_18-26-01](/uploads/6d9c76f835b53626b2d6cb0b13628ee0/Capture_d_écran_du_2024-01-30_18-26-01.png)
Many requests appear to be timing out with a 502 error.HiroHirohttps://gitlab.torproject.org/tpo/tpa/team/-/issues/41493Stripe and Paypal API keys for Stephen2024-02-12T18:23:07ZKezStripe and Paypal API keys for Stephen@stephen emailed me asking for Tor's Paypal client_ID, Paypal app_secret, and Stripe API key. He'll need these to properly develop and test donate-neo. For now he's just requested the sandboxed versions of these, which can't be used inte...@stephen emailed me asking for Tor's Paypal client_ID, Paypal app_secret, and Stripe API key. He'll need these to properly develop and test donate-neo. For now he's just requested the sandboxed versions of these, which can't be used interact with our production environment or payment data at all.
The Paypal client ID and Stripe PK are public and not sensitive, but we'll need to take care with the paypal app secret. In particular, I'd like to get permission from @anarcat to give Stephen our sandboxed Paypal app secret.https://gitlab.torproject.org/tpo/applications/tor-browser-build/-/issues/41068Build error Tor Browser Android for F-Droid: printf2024-01-26T17:00:01ZMynacolBuild error Tor Browser Android for F-Droid: printfI try to compile Tor Browser Android with F-Droid, but hit a hard wall. Compiling according to the docs and without containers works in a fresh Debian 11 container.
Running about the same commands with F-Droid build leads to a curious er...I try to compile Tor Browser Android with F-Droid, but hit a hard wall. Compiling according to the docs and without containers works in a fresh Debian 11 container.
Running about the same commands with F-Droid build leads to a curious error message while trying to compile node. I tried the build process multiple times, even on a fresh bare-metal Debian 11 installation, with always the same error message. Here it is:
```
make[1]: printf: Argument list too long
```
The full logs can be found [here](https://nowtransfer.de/acf4781c8d68) (GitLab was not happy about the file size).
And the F-Droid build script for these logs is [here](https://gitlab.com/Mynacol/fdroiddata/-/blob/9637d788d272b4c827e5225d5806a7c9f19b96d1/metadata/org.torproject.torbrowser.yml) while the newest build script might be found [in the branch](https://gitlab.com/Mynacol/fdroiddata/-/blob/add-torbrowser/metadata/org.torproject.torbrowser.yml).
My suspicion is that make calls the printf program and either make, the shell or printf is unhappy about the argument size. And the argument size might be bigger, because the absolute paths are in the F-Droid build longer, as they are done in `/fdroiddata/build/org.torproject.torbrowser/...`.
Ping to https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/27539MynacolMynacolhttps://gitlab.torproject.org/tpo/tpa/team/-/issues/41480Is matt@tpo available?2024-01-22T16:23:05ZHiroIs matt@tpo available?I will be proposing a new core contributor and he would like to ask for the uid matt@tpo. I have checked ldap and it seems available. Could you confirm if this uid can be assigned?I will be proposing a new core contributor and he would like to ask for the uid matt@tpo. I have checked ldap and it seems available. Could you confirm if this uid can be assigned?https://gitlab.torproject.org/tpo/applications/tor-browser-build/-/issues/41060tor browser memory leak2024-01-09T15:00:34Zcypherpunkstor browser memory leakWhen I leave tor browser running its using all the memory like a memory leak.
Im just displaying https://myip.wtf/ so its not the website itself.
It was a huge problem 2021 or 2022.
After a while I noticed that it got fixed.... Im not s...When I leave tor browser running its using all the memory like a memory leak.
Im just displaying https://myip.wtf/ so its not the website itself.
It was a huge problem 2021 or 2022.
After a while I noticed that it got fixed.... Im not sure exactly when.
But now the problem is back again.
And this time Im making a proper bugreport.
Im using 13.0.8 and have following extentions installed:
* Adblock Plus - Free AD blocker
* Bookmark Tab Here
* NoScript
And no not running these extentions is not an alternative.
Im using Linux.
I really want to have this solved and can be of help to solve it.cypherpunkscypherpunkshttps://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/issues/40314Consider rendezvous via available peers when possible2024-03-07T15:24:04ZcypherpunksConsider rendezvous via available peers when possibleConsider rendezvous via available peers when possible
This make sense when the peers multiplex option(-max) specified, also when domain front or similar primary rendezvous ways are very slow or poor connectivity.Consider rendezvous via available peers when possible
This make sense when the peers multiplex option(-max) specified, also when domain front or similar primary rendezvous ways are very slow or poor connectivity.https://gitlab.torproject.org/tpo/tpa/team/-/issues/41439Logging into forum with 2FA leads to "UnknownError: The operation failed for ...2023-12-12T15:32:45ZGeorg KoppenLogging into forum with 2FA leads to "UnknownError: The operation failed for an unknown transient reason"For a while now I always get "UnknownError: The operation failed for an unknown transient reason" when I try to use my Yuikey Security Key as a second factor. I am living on backup codes right now. :) I remember transitioning to the self...For a while now I always get "UnknownError: The operation failed for an unknown transient reason" when I try to use my Yuikey Security Key as a second factor. I am living on backup codes right now. :) I remember transitioning to the self-hosted forum worked which is why I have now two keys registered in my user profile. The setup broke later for me.
Trying to register yet another key fails as I get asked for a PIN which I don't have.
Needless to say that the same key is working fine as an U2F means for Gitlab and our NextCloud instance using the same Tor Browser.
I got reminded here by https://forum.torproject.org/t/please-recover-my-account-2-factor-auth-broken/10434/4 although I am not sure whether the problem mentioned there is exactly the same to mine.https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/42312Restore theme options on Android2024-01-09T14:26:56Zcypherpunks1Restore theme options on AndroidThere seems to have been some misunderstanding on #42076 as other than the browser's color the theme also changes the colors of the tab manager, error pages, reader view, view-source: pages and the background color while connecting to we...There seems to have been some misunderstanding on #42076 as other than the browser's color the theme also changes the colors of the tab manager, error pages, reader view, view-source: pages and the background color while connecting to websites.cypherpunks1cypherpunks1https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/42296Sudden disconnection from gateway2024-01-15T20:23:20ZcypherpunksSudden disconnection from gatewayInformations:
Android version: 13
TorBrowser version string:
115.2.1-release (13.0.3) (Build #2015982211), 127b6bbf8069
GV: 115.4.0-20231101155823
AS: 115.0
Issue description:
Even with a good internet connection, TorBrowser fo...Informations:
Android version: 13
TorBrowser version string:
115.2.1-release (13.0.3) (Build #2015982211), 127b6bbf8069
GV: 115.4.0-20231101155823
AS: 115.0
Issue description:
Even with a good internet connection, TorBrowser for Android is keeping to disconnect me in short period of time from the Tor gateway without any notification or errorcypherpunkscypherpunkshttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/42294Empty/Blank CAPTCHA2024-01-09T13:59:31ZZarko_GjurovEmpty/Blank CAPTCHAIn: Settings-\>Connection-\>Bridges-\>Add a new Bridge, Request a Bridge CAPTCHA that needs to be solved is empty/blank.
### Environment
Windows 7 SP1 Official setup exe version 13.0.5 from Tor Project website.
https://i.ibb.co/GPTpZF...In: Settings-\>Connection-\>Bridges-\>Add a new Bridge, Request a Bridge CAPTCHA that needs to be solved is empty/blank.
### Environment
Windows 7 SP1 Official setup exe version 13.0.5 from Tor Project website.
https://i.ibb.co/GPTpZFD/empty-CAPTCHA.png
![empty-CAPTCHA.png](/uploads/87047b27eb4933f6cadce9018143b20d/empty-CAPTCHA.png)https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/42282"Tor Browser" entry created in registry Editor under HKLM and HKCR2024-01-09T13:58:23Zcypherpunks"Tor Browser" entry created in registry Editor under HKLM and HKCR"Tor Browser" entry created in registry Editor under HKLM and HKCR"Tor Browser" entry created in registry Editor under HKLM and HKCRcypherpunkscypherpunkshttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/42281Stop creation attempt of Launcher2024-01-09T13:57:33ZcypherpunksStop creation attempt of LauncherWindows Logs > Application Error
The description for Event ID 5 from source Tor Browser Launcher cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You ...Windows Logs > Application Error
The description for Event ID 5 from source Tor Browser Launcher cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:cypherpunkscypherpunkshttps://gitlab.torproject.org/tpo/tpa/team/-/issues/41391Install libssl-dev on rdsys-frontend-012023-11-19T17:20:34ZCecylia BocovichInstall libssl-dev on rdsys-frontend-01After an udpate to our deployed distributor, I see this in the logs:
```
/srv/rdsys.torproject.org/bin/lox-distributor: error while loading shared libraries: libssl.so.1: cannot open shared object file: No such file or directory
```After an udpate to our deployed distributor, I see this in the logs:
```
/srv/rdsys.torproject.org/bin/lox-distributor: error while loading shared libraries: libssl.so.1: cannot open shared object file: No such file or directory
```Cecylia BocovichCecylia Bocovich