Trac issueshttps://gitlab.torproject.org/legacy/trac/-/issues2020-06-13T15:53:33Zhttps://gitlab.torproject.org/legacy/trac/-/issues/34211Add support for control signals (ex. Ctrl+C) in Windows2020-06-13T15:53:33ZTracAdd support for control signals (ex. Ctrl+C) in WindowsHi everyone!
I am working on a [cross-platform Tor controller/wrapper](https://github.com/DcodingTheWeb/ProxAllium/tree/next-gen), and I encountered a minor inconvenience while writing code for stopping Tor in Windows.
Currently the on...Hi everyone!
I am working on a [cross-platform Tor controller/wrapper](https://github.com/DcodingTheWeb/ProxAllium/tree/next-gen), and I encountered a minor inconvenience while writing code for stopping Tor in Windows.
Currently the only way to gracefully terminate Tor in Windows is to use the control port to issue the `SIGINT` signal, it would be beneficial for 3rd party programs which work with Tor to be able to invoke this procedure by using the native "control signals" provided to console programs in Windows.
I have made a patch which implements this functionality, I will post it soon, I am creating this ticket so that I can create a corresponding file in the `changes` directory :)
Thanks to nickm for some pointers about using the libevent `event_active` function to trigger the event, I decided to use the `activate_signal` function as it internally calls the suggested function and simplifies the code.
**Trac**:
**Username**: TheDcoderTor: 0.4.4.x-finalhttps://gitlab.torproject.org/legacy/trac/-/issues/34210Allow TheDcoder to create tickets2020-06-13T17:02:13ZpastlyAllow TheDcoder to create ticketsThey are a real non-troll non-spammy person that I've seen be reasonable on both IRC and Reddit. The recent anti-spam changes we've made are impacting them such that they can't create their first little-t tor ticket.They are a real non-troll non-spammy person that I've seen be reasonable on both IRC and Reddit. The recent anti-spam changes we've made are impacting them such that they can't create their first little-t tor ticket.Jens KubiezielJens Kubiezielhttps://gitlab.torproject.org/legacy/trac/-/issues/34209about:tor and about:tbupdate fail to load in debug build of Tor Browser2020-06-16T01:13:03ZMark Smithabout:tor and about:tbupdate fail to load in debug build of Tor BrowserWhen using a debug build based on acat's 33533+5 branch, trying to open about:tor or about:tbupdate leads to an assertion failure and a tab crash:
Assertion failure: foundObjectSrc (about: page must contain a CSP denying object-src), at...When using a debug build based on acat's 33533+5 branch, trying to open about:tor or about:tbupdate leads to an assertion failure and a tab crash:
Assertion failure: foundObjectSrc (about: page must contain a CSP denying object-src), at /.../dom/security/nsContentSecurityUtils.cpp:818
We need to add `object-src 'none'` to the CSP for those pages.Mark SmithMark Smithhttps://gitlab.torproject.org/legacy/trac/-/issues/34208Onionperf errors when no subcommand is given (python3)2020-06-13T18:04:35ZAna CusturaOnionperf errors when no subcommand is given (python3)Not a major issue by any means, but OP errors when ran without any arguments. This seems to be a behaviour change from Python2 to Python3. The expected behaviour was previously to print help.
```
~/onionperf$ onionperf
Traceback (most re...Not a major issue by any means, but OP errors when ran without any arguments. This seems to be a behaviour change from Python2 to Python3. The expected behaviour was previously to print help.
```
~/onionperf$ onionperf
Traceback (most recent call last):
File "/usr/local/bin/onionperf", line 532, in <module>
if __name__ == '__main__': sys.exit(main())
File "/usr/local/bin/onionperf", line 351, in main
args.func(args)
AttributeError: 'Namespace' object has no attribute 'func'
```
I've attached a patch to get back that behaviour. See also https://bugs.python.org/issue16308.https://gitlab.torproject.org/legacy/trac/-/issues/34207Please delete "bug34164-01" and "bug34206-01" branches from official tor-laun...2020-06-13T17:02:13ZKathleen BradePlease delete "bug34164-01" and "bug34206-01" branches from official tor-launcher.git repositoryI pushed two branches by mistake:
bug34164-01
bug34206-01
Please remove them from the tor-launcher.git repo. Thanks!I pushed two branches by mistake:
bug34164-01
bug34206-01
Please remove them from the tor-launcher.git repo. Thanks!https://gitlab.torproject.org/legacy/trac/-/issues/34206Tor Launcher button labels are missing (Firefox 76)2020-06-13T17:44:27ZMark SmithTor Launcher button labels are missing (Firefox 76)When running inside a Tor Browser that is based on Firefox 76 or newer, some button labels are missing from Tor Launcher's setup wizard. To fix this, we need to apply the same workaround as Mozilla applied in https://bugzilla.mozilla.org...When running inside a Tor Browser that is based on Firefox 76 or newer, some button labels are missing from Tor Launcher's setup wizard. To fix this, we need to apply the same workaround as Mozilla applied in https://bugzilla.mozilla.org/show_bug.cgi?id=1625938Kathleen BradeKathleen Bradehttps://gitlab.torproject.org/legacy/trac/-/issues/34204Downgrade Travis stem version to a commit where tests pass.2020-06-13T15:53:32ZNick MathewsonDowngrade Travis stem version to a commit where tests pass.Due to https://github.com/torproject/stem/issues/63 our CI is failing. Let's downgrade to a working version of Stem unless it gets fixed right away.
I have a test PR at https://github.com/torproject/tor/pull/1889 ; if CI passes, I'll m...Due to https://github.com/torproject/stem/issues/63 our CI is failing. Let's downgrade to a working version of Stem unless it gets fixed right away.
I have a test PR at https://github.com/torproject/tor/pull/1889 ; if CI passes, I'll make PRs for the other branches and put this in needs_review.Tor: 0.4.4.x-finalNick MathewsonNick Mathewsonhttps://gitlab.torproject.org/legacy/trac/-/issues/34203Some of the static libraries we build are not reproducible2020-06-16T01:26:26ZGeorg KoppenSome of the static libraries we build are not reproducibleI just realized that the `.a` archives we create (e.g.) for `libevent` on android are not reproducible while their contents are. We should fix that as it makes it easier to compare results and spot problems.
While we are at it we should...I just realized that the `.a` archives we create (e.g.) for `libevent` on android are not reproducible while their contents are. We should fix that as it makes it easier to compare results and spot problems.
While we are at it we should check other outputs as well as I bet not only `lilbevent` is affected.
FWIW: In the `libevent` case it seems timestamps play a role when creating the `.a` files.https://gitlab.torproject.org/legacy/trac/-/issues/34202Remove xz (LZMA) project for now2020-06-16T01:13:02ZGeorg KoppenRemove xz (LZMA) project for nowThe xz project is currently unused and starts to bitrot. We should remove it for now and add it properly back once we actually need it.The xz project is currently unused and starts to bitrot. We should remove it for now and add it properly back once we actually need it.Georg KoppenGeorg Koppenhttps://gitlab.torproject.org/legacy/trac/-/issues/34201WeSupportTor defaced2020-06-13T17:02:13ZTracWeSupportTor defacedWeSupportTor:
https://trac.torproject.org/projects/tor/wiki/org/projects/WeSupportTor
is hosting a malicious page and it includes links to obscene images.
This doesn't look good.
I looked at the history an account named cypherpunks w...WeSupportTor:
https://trac.torproject.org/projects/tor/wiki/org/projects/WeSupportTor
is hosting a malicious page and it includes links to obscene images.
This doesn't look good.
I looked at the history an account named cypherpunks with weird encoding
did it 38 minutes before this post.
**Trac**:
**Username**: crabJens KubiezielJens Kubiezielhttps://gitlab.torproject.org/legacy/trac/-/issues/34200Refactor tor's circuit path node selection checks2020-06-13T15:53:32ZteorRefactor tor's circuit path node selection checksIn #33222, we added an extra "can extend over IPv6" check to tor's circuit path node selection code.
To make sure it's applied consistently, I did a refactor of that code, so all those checks are in one function.In #33222, we added an extra "can extend over IPv6" check to tor's circuit path node selection code.
To make sure it's applied consistently, I did a refactor of that code, so all those checks are in one function.Tor: 0.4.5.x-finalteorteorhttps://gitlab.torproject.org/legacy/trac/-/issues/34199torsocks irssi weird bug2020-06-13T16:10:11ZTractorsocks irssi weird bugDepending on the arguments to torsocks the output varies even though it shouldn't
case-1: torsocks irssi
`/connect oftc` gives following error
Irssi: Unable to connect server irc.oftc.net port 6697 [Interrupted system call]
case 2: tor...Depending on the arguments to torsocks the output varies even though it shouldn't
case-1: torsocks irssi
`/connect oftc` gives following error
Irssi: Unable to connect server irc.oftc.net port 6697 [Interrupted system call]
case 2: torsocks -d irssi
`/connect oftc` works as expected
I don't think there should be difference in output just because logging is enabled. This just might be the "torsocks uncertainty principle". I think we are onto something. Below I've attached the log dumped on the terminal.
1589343629 DEBUG torsocks[22051]: Logging subsytem initialized. Level 5, file (null), time 1 (in init_logging() at torsocks.c:303)
1589343629 DEBUG torsocks[22051]: Config file not provided by TORSOCKS_CONF_FILE. Using default /etc/torsocks.conf (in config_file_read() at config-file.c:543)
1589343629 DEBUG torsocks[22051]: Config file setting tor address to 127.0.0.1 (in conf_file_set_tor_address() at config-file.c:298)
1589343629 DEBUG torsocks[22051]: Config file setting tor port to 9050 (in conf_file_set_tor_port() at config-file.c:254)
1589343629 DEBUG torsocks[22051]: [config] Onion address range set to 127.42.42.0/24 (in set_onion_info() at config-file.c:108)
1589343629 DEBUG torsocks[22051]: Config file /etc/torsocks.conf opened and parsed. (in config_file_read() at config-file.c:572)
1589343629 DEBUG torsocks[22051]: [fclose] Close caught for fd 3 (in tsocks_fclose() at fclose.c:45)
1589343629 DEBUG torsocks[22051]: [onion] Pool init with subnet 127.42.42.0 and mask 24 (in onion_pool_init() at onion.c:104)
1589343629 DEBUG torsocks[22051]: [onion] Pool initialized with base 0, max_pos 255 and size 8 (in onion_pool_init() at onion.c:132)
1589343629 DEBUG torsocks[22051]: [close] Close caught for fd 3 (in tsocks_close() at close.c:33)
1589343629 DEBUG torsocks[22051]: [close] Close caught for fd 3 (in tsocks_close() at close.c:33)
1589343629 DEBUG torsocks[22051]: [close] Close caught for fd 3 (in tsocks_close() at close.c:33)
1589343629 DEBUG torsocks[22051]: [close] Close caught for fd 5 (in tsocks_close() at close.c:33)
1589343629 DEBUG torsocks[22051]: [close] Close caught for fd 5 (in tsocks_close() at close.c:33)
1589343629 DEBUG torsocks[22051]: [close] Close caught for fd 5 (in tsocks_close() at close.c:33)
1589343629 DEBUG torsocks[22051]: [close] Close caught for fd 5 (in tsocks_close() at close.c:33)
1589343629 DEBUG torsocks[22051]: [close] Close caught for fd 5 (in tsocks_close() at close.c:33)
1589343629 DEBUG torsocks[22051]: [close] Close caught for fd 5 (in tsocks_close() at close.c:33)
1589343629 DEBUG torsocks[22051]: [close] Close caught for fd 5 (in tsocks_close() at close.c:33)
1589343629 DEBUG torsocks[22051]: [close] Close caught for fd 5 (in tsocks_close() at close.c:33)
1589343629 DEBUG torsocks[22051]: [close] Close caught for fd 5 (in tsocks_close() at close.c:33)
1589343629 DEBUG torsocks[22051]: [close] Close caught for fd 5 (in tsocks_close() at close.c:33)
1589343629 DEBUG torsocks[22051]: [close] Close caught for fd 5 (in tsocks_close() at close.c:33)
1589343629 DEBUG torsocks[22051]: [close] Close caught for fd 5 (in tsocks_close() at close.c:33)
1589343629 DEBUG torsocks[22051]: [close] Close caught for fd 5 (in tsocks_close() at close.c:33)
**Trac**:
**Username**: crabhttps://gitlab.torproject.org/legacy/trac/-/issues/34198Include full broker messaging spec in /doc2020-06-13T18:22:07ZCecylia BocovichInclude full broker messaging spec in /docThis adds information about the broker API, with the messaging protocol and the endpoints used by clients and proxies.
This is a prerequisite for our work to implement a Snowflake proxy on Android.This adds information about the broker API, with the messaging protocol and the endpoints used by clients and proxies.
This is a prerequisite for our work to implement a Snowflake proxy on Android.Cecylia BocovichCecylia Bocovichhttps://gitlab.torproject.org/legacy/trac/-/issues/34196Update site info URL with the onion name2020-06-16T01:13:02ZAntonelaantonela@torproject.orgUpdate site info URL with the onion nameAfter discussing onion names with the Freedom of the Press UX folks, they suggested showing a more explicit relationship between the origin .onion address and HTTPSeverywhere alias in our user interface.
We agreed on this idea and we pl...After discussing onion names with the Freedom of the Press UX folks, they suggested showing a more explicit relationship between the origin .onion address and HTTPSeverywhere alias in our user interface.
We agreed on this idea and we planned to:
- update the site info at the identity doorhanger by showing the onion name
- allow users to see [more info]https://gitlab.torproject.org/legacy/trac/-/issues/34195Make wolpertinger create usage metrics2020-06-13T18:36:32ZPhilipp Winterphw@torproject.orgMake wolpertinger create usage metricsWolpertinger should export usage metrics to help us understand 1) how censorship measurement platforms use its API, and 2) its inner workings. Metrics that come to mind:
* Number of bridge requests over time per censorship measurement p...Wolpertinger should export usage metrics to help us understand 1) how censorship measurement platforms use its API, and 2) its inner workings. Metrics that come to mind:
* Number of bridge requests over time per censorship measurement platform.
* The distribution of origin countries per censorship measurement platform.Philipp Winterphw@torproject.orgPhilipp Winterphw@torproject.orghttps://gitlab.torproject.org/legacy/trac/-/issues/34194dead link in tor-browser2020-06-16T01:13:01ZTracdead link in tor-browserClick on tor icon beside the search bar to show the site information.
Below the "New Circuit for this Site" button click the "Learn more" link.
link leads to https://support.torproject.org/und/tbb/tbb-2/
Greets with following error.
No...Click on tor icon beside the search bar to show the site information.
Below the "New Circuit for this Site" button click the "Learn more" link.
link leads to https://support.torproject.org/und/tbb/tbb-2/
Greets with following error.
Not Found
The requested URL was not found on this server.
Swear to god I wanted to learn more this time.
**Trac**:
**Username**: crabhttps://gitlab.torproject.org/legacy/trac/-/issues/34193Audit the U2F API2020-06-16T01:13:01ZAlex CatarineuAudit the U2F APISimilar to #26614, we should audit the `U2F` API implementation that is enabled with the `security.webauth.u2f` pref.Similar to #26614, we should audit the `U2F` API implementation that is enabled with the `security.webauth.u2f` pref.https://gitlab.torproject.org/legacy/trac/-/issues/34192It Just Does Not Work2020-06-16T01:13:00ZTracIt Just Does Not WorkTor worked like a breeze for me a few months ago. Now I cannot even get it to start.
Something is serious fucked up with this latest version of the browser, and there is **no good information out there** on what to do about it. Gibb...Tor worked like a breeze for me a few months ago. Now I cannot even get it to start.
Something is serious fucked up with this latest version of the browser, and there is **no good information out there** on what to do about it. Gibberish and nonsense.
Please post a **plain-English** solution to this problem.
No, I do not use a proxy, I am not in a country where Tor is censored, and there is absolutely nothing wrong with my system clock.
OS: **Windows 7**
Tor Version: **9.0.10**
Log:
5/12/20, 13:23:34.321 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
5/12/20, 13:23:34.321 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
5/12/20, 13:23:34.321 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
5/12/20, 13:23:34.322 [NOTICE] Opening Socks listener on 127.0.0.1:9150
5/12/20, 13:23:34.322 [NOTICE] Opened Socks listener on 127.0.0.1:9150
5/12/20, 13:23:34.322 [NOTICE] Renaming old configuration file to "E:\Tor Browser\Browser\TorBrowser\Data\Tor\torrc.orig.1"
5/12/20, 13:23:34.322 [NOTICE] Bootstrapped 5% (conn): Connecting to a relay
5/12/20, 13:24:58.291 [WARN] Problem bootstrapping. Stuck at 5% (conn): Connecting to a relay. (Connection timed out [WSAETIMEDOUT ]; TIMEOUT; count 10; recommendation warn; host 847B1F850344D7876491A54892F904934E4EB85D at 86.59.21.38:443)
5/12/20, 13:24:58.291 [WARN] 9 connections have failed:
5/12/20, 13:24:58.291 [WARN] 9 connections died in state connect()ing with SSL state (No SSL object)
5/12/20, 13:24:58.299 [WARN] Problem bootstrapping. Stuck at 5% (conn): Connecting to a relay. (Connection timed out [WSAETIMEDOUT ]; TIMEOUT; count 11; recommendation warn; host FFA72BD683BC2FCF988356E6BEC1E490F313FB07 at 193.11.164.243:9001)
5/12/20, 13:24:58.299 [WARN] 10 connections have failed:
5/12/20, 13:24:58.299 [WARN] 10 connections died in state connect()ing with SSL state (No SSL object)
5/12/20, 13:24:58.299 [NOTICE] Closing no-longer-configured Socks listener on 127.0.0.1:9150
5/12/20, 13:24:58.299 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
5/12/20, 13:24:59.290 [NOTICE] Delaying directory fetches: DisableNetwork is set.
**Trac**:
**Username**: WR Smithhttps://gitlab.torproject.org/legacy/trac/-/issues/34191Combine multiple analysis files into single data set2020-06-13T18:04:34ZKarsten LoesingCombine multiple analysis files into single data setOnionPerf's visualize mode currently supports specifying multiple data sets to be graphed with different labels for each data set. However, for each data set it's only possible to specify exactly one analysis results file. If we ever wan...OnionPerf's visualize mode currently supports specifying multiple data sets to be graphed with different labels for each data set. However, for each data set it's only possible to specify exactly one analysis results file. If we ever want to graph a data set covering more than a single day and compare that to another data set, we cannot do that at the moment.
Here's a possible user interface extension to allow specifying one or more analysis results files for each data set:
```
diff --git a/onionperf/onionperf b/onionperf/onionperf
index cb1899c..957c6df 100755
--- a/onionperf/onionperf
+++ b/onionperf/onionperf
@@ -326,8 +326,9 @@ files generated by this script will be written""",
visualize_parser.set_defaults(func=visualize, formatter_class=my_formatter_class)
visualize_parser.add_argument('-d', '--data',
- help="""Append a PATH to a onionperf.analysis.json analysis results file, and a LABEL that we
- should use for the graph legend for this dataset""",
+ help="""Append a file or directory PATH to an onionperf.analysis.json
+ analysis results file or directory of such files, and a LABEL
+ that we should use for the graph legend for this dataset""",
metavar=("PATH", "LABEL"),
nargs=2,
required="True",
```
I didn't write any other code for this yet.Ana CusturaAna Custurahttps://gitlab.torproject.org/legacy/trac/-/issues/34190New shared account idea2020-06-13T17:02:12ZTracNew shared account ideaOld system:
- cypherpunks, writecode
- Anyone can use it
- Bot attack / Script is very easy
New system:
- cypherpunk(RandomStringHere), writecode
- ID:Password rotate every 1 week or 1 day
- So they can't vandalize comments after ...Old system:
- cypherpunks, writecode
- Anyone can use it
- Bot attack / Script is very easy
New system:
- cypherpunk(RandomStringHere), writecode
- ID:Password rotate every 1 week or 1 day
- So they can't vandalize comments after 1 week or 1 day
- Anyone can use it
- Yes, this is a must
- Bot attack / Script is difficult
----
1. Open https://trac.torproject.org/projects/tor/wiki/WikiStart#UnofficialDocumentation
2. Click "use this shared account of this week"
3. Solve Captcha
4. Display current ID:Password pair
Before
```
Most of the content here is written by volunteers from around the world. If you find a topic you want to fix, expand, or create, please either create an account or use the multi-user account cypherpunks with the password writecode Note that edits will be credited to the cypherpunks account and not you personally.
```
After
```
Most of the content here is written by volunteers from around the world. If you find a topic you want to fix, expand, or create, please either create an account or use the multi-user account. Click here to view _account information_. Note that edits will be credited to the cypherpunks account and not you personally.
```
**Trac**:
**Username**: cypherpunk1Jens KubiezielJens Kubieziel