Trac issueshttps://gitlab.torproject.org/legacy/trac/-/issues2020-06-13T17:56:17Zhttps://gitlab.torproject.org/legacy/trac/-/issues/34293Create an API for running the system on the user-provided websites2020-06-13T17:56:17ZBarkin SimsekCreate an API for running the system on the user-provided websitesThis part of the API aims to run certain tests on user-provided websites. So that people are not limited to the types of websites provided by the CAPTCHA Monitor.This part of the API aims to run certain tests on user-provided websites. So that people are not limited to the types of websites provided by the CAPTCHA Monitor.https://gitlab.torproject.org/legacy/trac/-/issues/34292Create an API for people to fetch data easily2020-06-13T17:56:16ZBarkin SimsekCreate an API for people to fetch data easilyThis API might feature customized queries to get a specific part of the dataset rather than the whole dataset.This API might feature customized queries to get a specific part of the dataset rather than the whole dataset.https://gitlab.torproject.org/legacy/trac/-/issues/34291Create an API for enabling 3rd party interactions with the system2020-06-13T17:56:16ZBarkin SimsekCreate an API for enabling 3rd party interactions with the systemhttps://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/34151Readme needs update2020-06-13T18:22:07ZHashikDReadme needs updateFor testing, according to ReadMe.md...
''Unit testing with Jasmine are available with: npm install npm test
To run locally, start an HTTP server in build/ and navigate to /embed.html''
_npm run build_ needs to be a prerequisite before...For testing, according to ReadMe.md...
''Unit testing with Jasmine are available with: npm install npm test
To run locally, start an HTTP server in build/ and navigate to /embed.html''
_npm run build_ needs to be a prerequisite before starting the server and navigating to /embed.html.HashikDHashikDhttps://gitlab.torproject.org/legacy/trac/-/issues/33787T-shirts for volunteers should be substituted, or supplemented, with socks2020-06-13T17:37:32ZTracT-shirts for volunteers should be substituted, or supplemented, with socksNote: this ticket was created on April 1, it's probably a joke
The community team should consider awarding volunteers with socks instead of t-shirts. Socks are much better for at least 3 reasons:
1. They are a symbolic reference to SOC...Note: this ticket was created on April 1, it's probably a joke
The community team should consider awarding volunteers with socks instead of t-shirts. Socks are much better for at least 3 reasons:
1. They are a symbolic reference to SOCKS (obviously)
2. They can be worn in a much more clandestine fashion, which corresponds to the way Tor users browse the internet
3. They are smaller, so easier to transport (and cheaper)
They could be provided in various colour, like t-shirts are now - classic black, Tor green and Tor purple, all with Tor onion logo, would be solid choices.
I suggest providing them in sets of two pairs (4 individual sock pieces) to represent SOCKS4a. Better yet, they could be provided as 5 individual sock pieces in order to represent SOCKS5 and as a workaround to the common and dreaded missing sock problem. It could also be considered to provide them as three pairs (6 individual sock pieces, possibly each pair in different colour) in anticipation of a breakthrough in SOCKS technology and the introduction of SOCKS6.
**Trac**:
**Username**: umGusGushttps://gitlab.torproject.org/legacy/trac/-/issues/33744Remove local LAN address ICE candidates from JS proxy answer2020-06-13T18:21:50ZArlo BreaultRemove local LAN address ICE candidates from JS proxy answerThis is a follow up from #19026 where it was done for the clients and golang proxies.This is a follow up from #19026 where it was done for the clients and golang proxies.https://gitlab.torproject.org/legacy/trac/-/issues/33742Add information about design paper and anonbib inside README.1st2020-06-13T15:52:36ZGhost UserAdd information about design paper and anonbib inside README.1stAs mentioned under #33688 (comment 9) some old "TODO" items were removed from `doc/HACKING/README.1st.md` file.
Link and description should be added for:
- design paper,
- anonbib.As mentioned under #33688 (comment 9) some old "TODO" items were removed from `doc/HACKING/README.1st.md` file.
Link and description should be added for:
- design paper,
- anonbib.Tor: unspecifiedhttps://gitlab.torproject.org/legacy/trac/-/issues/33741Format code blocks inside markdown files (documentation)2020-06-13T15:52:36ZGhost UserFormat code blocks inside markdown files (documentation)There are issues with code blocks inside some *.md files (some files use code blocks syntax, some do not). First of all, it's not consistent but what's really bad is when *.md file is being displayed incorrectly. You can find an example ...There are issues with code blocks inside some *.md files (some files use code blocks syntax, some do not). First of all, it's not consistent but what's really bad is when *.md file is being displayed incorrectly. You can find an example of what I'm saying in CodingStandards.md under How we log changes section.
​https://github.com/torproject/tor/blob/master/doc/HACKING/CodingStandards.md#how-we-log-changes
Part of the git log output is still displayed as a regular text rather than a formatted code block.
Goal of this ticket is to go through all *.md files under `doc` and `doc/HACKING` directories and format code snippets accordingly.
```
```c
// code snippet
// written in
// C language
```
```
```
```bash
// command to be run
// inside bash
```
```
This should fix the issues described above and enable syntax highlighting on supported websites and editors.Tor: unspecifiedhttps://gitlab.torproject.org/legacy/trac/-/issues/33688README cleanups2020-06-13T15:52:30ZGhost UserREADME cleanupsHello everyone,
I just started playing around with Tor a few days back so as one could expect I started with `README.1st.md` file. I realized that different `*.md` files are not consistent style-wise so I decided to clean them up a bit.
...Hello everyone,
I just started playing around with Tor a few days back so as one could expect I started with `README.1st.md` file. I realized that different `*.md` files are not consistent style-wise so I decided to clean them up a bit.
Brief summary:
- no empty line at the very beginning of the file,
- single empty line between sections (sometimes there were two)
```
... end of the sentence.
New Section
----
```
rather than
```
... end of the sentence.
New Section
----
```
- external links use [name](url) format,
- there is no single space in front of the section name
```
Foo
===
```
is changed to
```
Foo
===
```
Which fixes syntax issues in editors like GNU Emacs with enabled markdown preview.
- I tried to check all links (local and external) and fix the ones which were broken.
For example **the Tor proposal process** inside `README.1st.md` or `doc/WritingTests.txt` were changed to `.../doc/HACKING/WritingTests.md` in few places).
----
At the very end of `README.1st.md` file there are some TODO (I think?) sections. I wrapped them around in "TODO" section.
```
TODO
-----------------------
XXXXX also describe
doc/HACKING/WritingTests.md
torguts.git
torspec.git
The design paper
freehaven.net/anonbib
XXXX describe these and add links.
```
However I am not sure if these are still needed there. Most of these topics are mentioned already in this file and linked to other files (WritingTests, torspec, etc.).Tor: 0.4.4.x-finalhttps://gitlab.torproject.org/legacy/trac/-/issues/33552Unsupported syscall number 229 on Debian on torsocks 2.3.02020-06-13T16:10:11ZTracUnsupported syscall number 229 on Debian on torsocks 2.3.0arch is x64.
Versions:
Tor 0.4.2.6 running on Linux with Libevent 2.1.8-stable, OpenSSL 1.1.1d, Zlib 1.2.11, Liblzma 5.2.4, and Libzstd 1.3.8.
I'm testing Interactive Brokers' TWS software on Tails OS (just for fun, I see it's not a use...arch is x64.
Versions:
Tor 0.4.2.6 running on Linux with Libevent 2.1.8-stable, OpenSSL 1.1.1d, Zlib 1.2.11, Liblzma 5.2.4, and Libzstd 1.3.8.
I'm testing Interactive Brokers' TWS software on Tails OS (just for fun, I see it's not a use case, however, I hope this can help), but I've met a problem launching it:
1583671114 WARNING torsocks[25196]: [syscall] Unsupported syscall number 229. Denying the call (in tsocks_syscall() at syscall.c:605)
1583671115 ERROR torsocks[25196]: Unable to resolve. Status reply: 4 (in socks5_recv_resolve_reply() at socks5.c:677)
The application show an error message: Update Failed. Check log file for details: /home/amnesia/Jts/.intall4j/updater.log (see below).
----
Steps to reproduce:
1. Launch Tails 4.3.
2. Download tws-latest-linux-x64.sh or tws-stable-linux-x64.sh from [the official website](https://www.interactivebrokers.com/en/index.php?f=14099#tws-software).
3. Run the installer: for example,
```
./tws-stable-linux-x64.sh
```
4. After the installation, launch the application: from the installer or from Terminal:
```
torify "/home/amnesia/Jts/tws" -J-DjtsConfigDir="/home/amnesia/Jts" %U
```
or
```
. torsocks on
"/home/amnesia/Jts/tws" -J-DjtsConfigDir="/home/amnesia/Jts" %U
```
5. You get:
```
1583672301 WARNING torsocks[26808]: [syscall] Unsupported syscall number 229. Denying the call (in tsocks_syscall() at syscall.c:605)
1583672301 ERROR torsocks[26808]: Unable to resolve. Status reply: 4 (in socks5_recv_resolve_reply() at socks5.c:677)
1583672301 ERROR torsocks[26808]: Unable to resolve. Status reply: 4 (in socks5_recv_resolve_reply() at socks5.c:677)
1583672302 ERROR torsocks[26808]: Unable to resolve. Status reply: 4 (in socks5_recv_resolve_reply() at socks5.c:677)
1583672379 PERROR torsocks[26808]: socks5 libc connect: Invalid argument (in socks5_connect() at socks5.c:202)
```
----
See the log (Jts/.intall4j/updater.log):
```
[INFO] com.install4j.runtime.beans.actions.control.SetVariableAction [ID 4839]: Execute action
Property script: com.install4j.script.I4jScript_Internal_62
Property variableName: updateDescriptorUrl
Property failIfNull: true
Property onlyIfUndefined: false
Property responseFileVariable: false
Property rollbackSupported: false
Variable changed: updateDescriptorUrl=https://download2.interactivebrokers.com/installers/tws/stable/tws-stable-linux-x64.xml[class java.lang.String]
Execute action successful after 3 ms
[INFO] com.install4j.runtime.beans.actions.update.CheckForUpdateAction [ID 479]: Execute action
Property connectTimeout: 10000
Property connectionFailureScript: null
Property readTimeout: 20000
Property requestHeaders: []
Property url: https://download2.interactivebrokers.com/installers/tws/stable/tws-stable-linux-x64.xml
Property variable: updateDescriptor
Property acceptAllCertificates: false
Property askForProxy: true
Property rollbackSupported: false
Property showError: true
[ERROR] com.install4j.runtime.beans.actions.update.CheckForUpdateAction [ID 479]: could not download file
java.net.ConnectException: Invalid argument (connect failed)
java.net.ConnectException: Invalid argument (connect failed)
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
at java.net.Socket.connect(Socket.java:589)
at sun.security.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:673)
at sun.net.NetworkClient.doConnect(NetworkClient.java:175)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:463)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:558)
at sun.net.www.protocol.https.HttpsClient.<init>(HttpsClient.java:264)
at sun.net.www.protocol.https.HttpsClient.New(HttpsClient.java:367)
at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.getNewHttpClient(AbstractDelegateHttpsURLConnection.java:191)
at sun.net.www.protocol.http.HttpURLConnection.plainConnect0(HttpURLConnection.java:1156)
at sun.net.www.protocol.http.HttpURLConnection$6.run(HttpURLConnection.java:1040)
at sun.net.www.protocol.http.HttpURLConnection$6.run(HttpURLConnection.java:1038)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.AccessController.doPrivilegedWithCombiner(AccessController.java:782)
at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:1037)
at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:177)
at sun.net.www.protocol.https.HttpsURLConnectionImpl.connect(HttpsURLConnectionImpl.java:162)
at com.install4j.runtime.installer.helper.content.HttpRequestHandler.getURLConnection(HttpRequestHandler.java:288)
at com.install4j.runtime.installer.helper.content.HttpRequestHandler.connect(HttpRequestHandler.java:135)
at com.install4j.runtime.installer.helper.content.Downloader.connect(Downloader.java:155)
at com.install4j.runtime.installer.helper.content.Downloader.connect(Downloader.java:24)
at com.install4j.runtime.installer.helper.content.HttpRequestHandler.connect(HttpRequestHandler.java:128)
at com.install4j.runtime.installer.helper.content.Downloader.connect(Downloader.java:150)
at com.install4j.runtime.beans.actions.update.CheckForUpdateAction.execute(CheckForUpdateAction.java:35)
at com.install4j.runtime.beans.actions.SystemInstallOrUninstallAction.install(SystemInstallOrUninstallAction.java:29)
at com.install4j.runtime.installer.ContextImpl$9.executeAction(ContextImpl.java:1727)
at com.install4j.runtime.installer.ContextImpl$9.fetchValue(ContextImpl.java:1718)
at com.install4j.runtime.installer.ContextImpl$9.fetchValue(ContextImpl.java:1715)
at com.install4j.runtime.installer.helper.comm.actions.FetchObjectAction.execute(FetchObjectAction.java:14)
at com.install4j.runtime.installer.helper.comm.HelperCommunication.executeActionDirect(HelperCommunication.java:271)
at com.install4j.runtime.installer.helper.comm.HelperCommunication.executeActionInt(HelperCommunication.java:246)
at com.install4j.runtime.installer.helper.comm.HelperCommunication.executeActionChecked(HelperCommunication.java:184)
at com.install4j.runtime.installer.helper.comm.HelperCommunication.fetchObjectChecked(HelperCommunication.java:167)
at com.install4j.runtime.installer.ContextImpl.performActionIntStatic(ContextImpl.java:1715)
at com.install4j.runtime.installer.InstallerContextImpl.performActionInt(InstallerContextImpl.java:159)
at com.install4j.runtime.installer.ContextImpl.performAction(ContextImpl.java:1143)
at com.install4j.runtime.installer.controller.Controller.executeAction(Controller.java:398)
at com.install4j.runtime.installer.controller.Controller.executeActions(Controller.java:364)
at com.install4j.runtime.installer.controller.Controller.handleCommand(Controller.java:221)
at com.install4j.runtime.installer.controller.Controller.handleStartup(Controller.java:142)
at com.install4j.runtime.installer.controller.Controller.start(Controller.java:98)
at com.install4j.runtime.installer.Application.runApplication(Application.java:91)
at com.install4j.runtime.installer.Application.main(Application.java:51)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at com.exe4j.runtime.LauncherEngine.launch(LauncherEngine.java:85)
at com.install4j.runtime.launcher.UnixLauncher.start(UnixLauncher.java:66)
at install4j.App3118837495Id443.main(Unknown Source)
Execute action not successful after 10500 ms
[INFO] Canceled
```
**Trac**:
**Username**: secureyourselfhttps://gitlab.torproject.org/legacy/trac/-/issues/33520'hacking Tor' web page has a few problems2020-06-16T01:11:29ZTrac'hacking Tor' web page has a few problemsThe page https://trac.torproject.org/projects/tor/wiki/doc/TorBrowser/Hacking#WaystoBuildTorBrowser for building just the browser has a couple of problems.
The first is that the origin/Master branch doesn't build using those instructi...The page https://trac.torproject.org/projects/tor/wiki/doc/TorBrowser/Hacking#WaystoBuildTorBrowser for building just the browser has a couple of problems.
The first is that the origin/Master branch doesn't build using those instructions. The 'mach configure' line's first option throws an error. Remove that option and you get ValueError in build/moz.configure/init.configure split-triplet.
I went to branch tor-browser-68.5.0esr-9.5-1 and these went away. The page should point people to either 'oldest branch that builds' or just say use the latest if you're going to hack.
With this version, the steps are good except it misses one. It says that tor-launcher needs to be in browser/extensions. It doesn't say that torbutton needs to be in toolkit/torproject.
I know they are small, but they might save someone else some time.
**Trac**:
**Username**: drjohnson1984https://gitlab.torproject.org/legacy/trac/-/issues/33449puppet: replace dsa_systemd with camptocamp systemd module2020-06-13T17:01:05Zanarcatpuppet: replace dsa_systemd with camptocamp systemd modulewe currently have two systemd module in Puppet, dsa_systemd (from the Debian sysadmins) and [camptocamp-systemd](https://github.com/camptocamp/puppet-systemd/), from the Puppet forge.
the latter was imported as a dependency of the Prome...we currently have two systemd module in Puppet, dsa_systemd (from the Debian sysadmins) and [camptocamp-systemd](https://github.com/camptocamp/puppet-systemd/), from the Puppet forge.
the latter was imported as a dependency of the Prometheus module and it would be very hard to remove it from our codebase.
we should look at whether we can replace the dsa_systemd module with the forge systemd module instead. this would allow us to collaborate with a broader community and remove duplicate code from our monorepo.
ideally, we'd also provide the good DSA folks a procedure on how to perform the migration, since we'll have to do it anyways.
so far, I've found this transition:
```
dsa_systemd::linger { 'bridgescan': }
```
... becomes:
```
loginctl_user { 'tordnsel':
linger => enabled,
}
```
we also use:
* `dsa_systemd::override`
* `dsa_systemd::mask`
we already use the camptocamp:
* `systemd::tmpfile`
* `systemd::unit_file`
... and we have various systemd files manually deployed in `/lib` and `/etc`https://gitlab.torproject.org/legacy/trac/-/issues/33044Outreachy internship timeline2020-06-13T17:36:50ZTracOutreachy internship timelineI'm rearranging the timeline of my Outreachy internship, keeping tracking of what's been done so far and upcoming tasks.
**Month 1 (Dec 3 to Jan 3):**
- Resolved about 250 frontdesk tickets, not counting those marked as spam.
- https...I'm rearranging the timeline of my Outreachy internship, keeping tracking of what's been done so far and upcoming tasks.
**Month 1 (Dec 3 to Jan 3):**
- Resolved about 250 frontdesk tickets, not counting those marked as spam.
- https://github.com/torproject/lego/pull/13
- Opened a new ticket based on user feedback: https://trac.torproject.org/projects/tor/ticket/32853
- Wrote the December 2019 feedback report: https://lists.torproject.org/pipermail/tor-project/2020-January/002645.html
**Month 2 (Jan 4 to Feb 4):**
- Resolved about 30 new frontdesk tickets, not counting those marked as spam.
- Closed some old unassigned open frontdesk tickets.
- The frontdesk queue has been reduced from 320 to 40 tickets.
- Worked on the Tor Mobile manual: https://github.com/torproject/manual/pull/58
- Created new issue based on user feedback: https://dip.torproject.org/torproject/web/tpo/issues/56
**Trac**:
**Username**: PROTechThorhttps://gitlab.torproject.org/legacy/trac/-/issues/33028v0.4.1.6 bug journalctl failed assertion2020-06-13T15:50:08ZTracv0.4.1.6 bug journalctl failed assertionUsing tor as a relay and a client to make a batches on requests to onion domains; cleaning HS cache from time to time (NEWNYM signal).
On some machines encountered th following in the system journal:
```
```log
Jan 22 17:49:45 xxx Tor[...Using tor as a relay and a client to make a batches on requests to onion domains; cleaning HS cache from time to time (NEWNYM signal).
On some machines encountered th following in the system journal:
```
```log
Jan 22 17:49:45 xxx Tor[19497]: tor_bug_occurred_(): Bug: src/feature/hs/hs_client.c:685: setup_intro_circ_auth_key: Non-fatal assertion !(desc == NULL) failed. (Future instances of this warning will be silenced.) (on Tor 0.4.1.6 )
Jan 22 17:49:45 xxx Tor[19497]: Bug: Non-fatal assertion !(desc == NULL) failed in setup_intro_circ_auth_key at src/feature/hs/hs_client.c:685. Stack trace: (on Tor 0.4.1.6 )
Jan 22 17:49:45 xxx Tor[19497]: Bug: /usr/bin/tor(log_backtrace_impl+0x47) [0x55c488cdfe77] (on Tor 0.4.1.6 )
Jan 22 17:49:45 xxx Tor[19497]: Bug: /usr/bin/tor(tor_bug_occurred_+0x186) [0x55c488cdb576] (on Tor 0.4.1.6 )
Jan 22 17:49:45 xxx Tor[19497]: Bug: /usr/bin/tor(hs_client_circuit_has_opened+0x3cf) [0x55c488bd10ff] (on Tor 0.4.1.6 )
Jan 22 17:49:45 xxx Tor[19497]: Bug: /usr/bin/tor(circuit_send_next_onion_skin+0x2a8) [0x55c488b4d7f8] (on Tor 0.4.1.6 )
Jan 22 17:49:45 xxx Tor[19497]: Bug: /usr/bin/tor(+0x1469ca) [0x55c488b839ca] (on Tor 0.4.1.6 )
Jan 22 17:49:45 xxx Tor[19497]: Bug: /usr/bin/tor(circuit_receive_relay_cell+0x321) [0x55c488b85a71] (on Tor 0.4.1.6 )
Jan 22 17:49:45 xxx Tor[19497]: Bug: /usr/bin/tor(command_process_cell+0x17f) [0x55c488b6761f] (on Tor 0.4.1.6 )
Jan 22 17:49:45 xxx Tor[19497]: Bug: /usr/bin/tor(channel_tls_handle_cell+0x2bb) [0x55c488b4785b] (on Tor 0.4.1.6 )
Jan 22 17:49:45 xxx Tor[19497]: Bug: /usr/bin/tor(+0x1331af) [0x55c488b701af] (on Tor 0.4.1.6 )
Jan 22 17:49:45 xxx Tor[19497]: Bug: /usr/bin/tor(connection_handle_read+0x8f8) [0x55c488b35458] (on Tor 0.4.1.6 )
Jan 22 17:49:45 xxx Tor[19497]: Bug: /usr/bin/tor(+0xfd741) [0x55c488b3a741] (on Tor 0.4.1.6 )
Jan 22 17:49:45 xxx Tor[19497]: Bug: /lib64/libevent-2.0.so.5(event_base_loop+0x774) [0x7f8cd2272a14] (on Tor 0.4.1.6 )
Jan 22 17:49:45 xxx Tor[19497]: Bug: /usr/bin/tor(do_main_loop+0xd2) [0x55c488b3ba62] (on Tor 0.4.1.6 )
Jan 22 17:49:45 xxx Tor[19497]: Bug: /usr/bin/tor(tor_run_main+0x11fd) [0x55c488b298dd] (on Tor 0.4.1.6 )
Jan 22 17:49:45 xxx Tor[19497]: Bug: /usr/bin/tor(tor_main+0x3a) [0x55c488b26e2a] (on Tor 0.4.1.6 )
Jan 22 17:49:45 xxx Tor[19497]: Bug: /usr/bin/tor(main+0x19) [0x55c488b26999] (on Tor 0.4.1.6 )
Jan 22 17:49:45 xxx Tor[19497]: Bug: /lib64/libc.so.6(__libc_start_main+0xf5) [0x7f8cd118b505] (on Tor 0.4.1.6 )
Jan 22 17:49:45 xxx Tor[19497]: Bug: /usr/bin/tor(+0xe99eb) [0x55c488b269eb] (on Tor 0.4.1.6 )
Jan 22 17:49:46 xxx Tor[19497]: tor_bug_occurred_(): Bug: src/feature/hs/hs_client.c:491: intro_circ_is_ok: Non-fatal assertion !(!hs_ident_intro_circ_is_valid(circ->hs_ident)) failed. (Future instances of this warning will be silenced.) (on Tor 0.4.1.6 )
Jan 22 17:49:46 xxx Tor[19497]: Bug: Non-fatal assertion !(!hs_ident_intro_circ_is_valid(circ->hs_ident)) failed in intro_circ_is_ok at src/feature/hs/hs_client.c:491. Stack trace: (on Tor 0.4.1.6 )
Jan 22 17:49:46 xxx Tor[19497]: Bug: /usr/bin/tor(log_backtrace_impl+0x47) [0x55c488cdfe77] (on Tor 0.4.1.6 )
Jan 22 17:49:46 xxx Tor[19497]: Bug: /usr/bin/tor(tor_bug_occurred_+0x186) [0x55c488cdb576] (on Tor 0.4.1.6 )
Jan 22 17:49:46 xxx Tor[19497]: Bug: /usr/bin/tor(hs_client_send_introduce1+0x347) [0x55c488bd0bc7] (on Tor 0.4.1.6 )
Jan 22 17:49:46 xxx Tor[19497]: Bug: /usr/bin/tor(connection_ap_handshake_attach_circuit+0x7da) [0x55c488b660ba] (on Tor 0.4.1.6 )
Jan 22 17:49:46 xxx Tor[19497]: Bug: /usr/bin/tor(connection_ap_attach_pending+0x198) [0x55c488b69fd8] (on Tor 0.4.1.6 )
Jan 22 17:49:46 xxx Tor[19497]: Bug: /usr/bin/tor(hs_client_receive_rendezvous_acked+0x7c) [0x55c488bd11ac] (on Tor 0.4.1.6 )
Jan 22 17:49:46 xxx Tor[19497]: Bug: /usr/bin/tor(rend_process_relay_cell+0x113) [0x55c488c1a383] (on Tor 0.4.1.6 )
Jan 22 17:49:46 xxx Tor[19497]: Bug: /usr/bin/tor(+0x1467e8) [0x55c488b837e8] (on Tor 0.4.1.6 )
Jan 22 17:49:46 xxx Tor[19497]: Bug: /usr/bin/tor(circuit_receive_relay_cell+0x321) [0x55c488b85a71] (on Tor 0.4.1.6 )
Jan 22 17:49:46 xxx Tor[19497]: Bug: /usr/bin/tor(command_process_cell+0x17f) [0x55c488b6761f] (on Tor 0.4.1.6 )
Jan 22 17:49:46 xxx Tor[19497]: Bug: /usr/bin/tor(channel_tls_handle_cell+0x2bb) [0x55c488b4785b] (on Tor 0.4.1.6 )
Jan 22 17:49:46 xxx Tor[19497]: Bug: /usr/bin/tor(+0x1331af) [0x55c488b701af] (on Tor 0.4.1.6 )
Jan 22 17:49:46 xxx Tor[19497]: Bug: /usr/bin/tor(connection_handle_read+0x8f8) [0x55c488b35458] (on Tor 0.4.1.6 )
Jan 22 17:49:46 xxx Tor[19497]: Bug: /usr/bin/tor(+0xfd741) [0x55c488b3a741] (on Tor 0.4.1.6 )
Jan 22 17:49:46 xxx Tor[19497]: Bug: /lib64/libevent-2.0.so.5(event_base_loop+0x774) [0x7f8cd2272a14] (on Tor 0.4.1.6 )
Jan 22 17:49:46 xxx Tor[19497]: Bug: /usr/bin/tor(do_main_loop+0xd2) [0x55c488b3ba62] (on Tor 0.4.1.6 )
Jan 22 17:49:46 xxx Tor[19497]: Bug: /usr/bin/tor(tor_run_main+0x11fd) [0x55c488b298dd] (on Tor 0.4.1.6 )
Jan 22 17:49:46 xxx Tor[19497]: Bug: /usr/bin/tor(tor_main+0x3a) [0x55c488b26e2a] (on Tor 0.4.1.6 )
Jan 22 17:49:46 xxx Tor[19497]: Bug: /usr/bin/tor(main+0x19) [0x55c488b26999] (on Tor 0.4.1.6 )
Jan 22 17:49:46 xxx Tor[19497]: Bug: /lib64/libc.so.6(__libc_start_main+0xf5) [0x7f8cd118b505] (on Tor 0.4.1.6 )
Jan 22 17:49:46 xxx Tor[19497]: Bug: /usr/bin/tor(+0xe99eb) [0x55c488b269eb] (on Tor 0.4.1.6 )
Jan 22 17:51:28 xxx Tor[19497]: Rend stream is 120 seconds late. Giving up on address '[scrubbed].onion'.
```
```
**Trac**:
**Username**: anonprojecthttps://gitlab.torproject.org/legacy/trac/-/issues/32590Remove the "Experimental" label on the AMO listing of the Snowflake WebExt2020-06-13T18:21:18ZcypherpunksRemove the "Experimental" label on the AMO listing of the Snowflake WebExtYou can see an "Experimental" label when you go to https://addons.mozilla.org/en-US/firefox/addon/torproject-snowflake/You can see an "Experimental" label when you go to https://addons.mozilla.org/en-US/firefox/addon/torproject-snowflake/https://gitlab.torproject.org/legacy/trac/-/issues/32589Update the logos of Firefox and Chrome in https://snowflake.torproject.org/2020-06-13T18:21:17ZcypherpunksUpdate the logos of Firefox and Chrome in https://snowflake.torproject.org/https://gitlab.torproject.org/legacy/trac/-/issues/32183Repeated captcha requests2020-06-13T16:59:20ZTracRepeated captcha requestsBlundering noob here:
Trying to create a ticket about an onboarding fault - repeated captcha requests.
Seems tho I'm signed in and can ignore those requests?
Posting this to confirm !^
_notaninja_
**Trac**:
**Username**: notaninjaBlundering noob here:
Trying to create a ticket about an onboarding fault - repeated captcha requests.
Seems tho I'm signed in and can ignore those requests?
Posting this to confirm !^
_notaninja_
**Trac**:
**Username**: notaninjaJens KubiezielJens Kubiezielhttps://gitlab.torproject.org/legacy/trac/-/issues/31949Broken links in support page faqs2020-06-13T17:12:33ZTracBroken links in support page faqsAt https://support.torproject.org/, the "Edit this page" links under "Most Frequently Asked Questions" doesn't work.
**Trac**:
**Username**: PROTechThorAt https://support.torproject.org/, the "Edit this page" links under "Most Frequently Asked Questions" doesn't work.
**Trac**:
**Username**: PROTechThorHiroHirohttps://gitlab.torproject.org/legacy/trac/-/issues/31791disable alt key toggling the menu bar2020-06-16T01:07:38ZThorindisable alt key toggling the menu barFollowing the discussion at https://trac.torproject.org/projects/tor/ticket/31512#comment:10 where I suspect changes to the inner window are happening. Of the plethora of things that can alter the inner window measurements....
`ui.key.m...Following the discussion at https://trac.torproject.org/projects/tor/ticket/31512#comment:10 where I suspect changes to the inner window are happening. Of the plethora of things that can alter the inner window measurements....
`ui.key.menuAccessKey` = `0` will disable the alt key toggling the menu bar on and off
Letterboxing solves this issue, but it can also be very annoying if your letterboxed height keeps jumping sizes. It's not the only thing that can alter your height, but it is something that users can inadvertently trigger (I have fat thumbs, 10 of them, and it really annoys me: hence I set this myself in Firefox)
I'll leave it up to you. If the threat is mitigated, then why remove functionality. Feel free to close... or action ...