The Tor Project issueshttps://gitlab.torproject.org/groups/tpo/-/issues2023-07-20T15:44:06Zhttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/41894tor signal reload -> no more connections possible2023-07-20T15:44:06ZYetitor signal reload -> no more connections possible### Summary
After reloading TOR configuration by sending signal RELOAD (HUP) to control port no further connections are possible.
### Steps to reproduce:
1. Connect to Torbrowser/Tor control port (usually 9051), authenticate using a con...### Summary
After reloading TOR configuration by sending signal RELOAD (HUP) to control port no further connections are possible.
### Steps to reproduce:
1. Connect to Torbrowser/Tor control port (usually 9051), authenticate using a configured authentication method, and send the "signal reload" command. This is needed for example to (temporary) set a new exit node or exit country for a new browser tab without closing all other tabs and restarting Torbrowser.
2. Try to reload the current page or open a new.
### What is the current bug behavior?
Error "The proxy server is refusing connections". No more browsing is possible.
### What is the expected behavior?
The page navigation should continue working, but with the new Tor config.
### Environment
Windows 10
Torbrowser 12.5.1YetiYetihttps://gitlab.torproject.org/tpo/anti-censorship/team/-/issues/128Modern firewall-penetration protocols for Tor in China2023-08-11T09:50:26ZcomputerscotModern firewall-penetration protocols for Tor in ChinaReports on https://github.com/net4people/bbs/issues and https://forum.torproject.org say that both obfs4 and snowflake are blocked by the GFW. There are also doubts about whether the new WebTunnel pluggable transport will work. The GFW d...Reports on https://github.com/net4people/bbs/issues and https://forum.torproject.org say that both obfs4 and snowflake are blocked by the GFW. There are also doubts about whether the new WebTunnel pluggable transport will work. The GFW detects and blocks WebSocket-based proxies.
This is a proof-of-concept for more modern firewall-penetration protocols.
To test these protocols in action, set up an Xray server and client using the latest techniques, for example, https://cscot.pages.dev/2023/07/02/xray-reality-h2. If you follow the sample configuration in that article, you will have a SOCKS5 proxy listening on port `10808` on your client.
Download and install the Tor Browser from https://www.torproject.org.
When you run the Tor Browser for the first time, click **Configure Connection**.
Scroll down and click the **Settings** button at the bottom to configure how you connect to the internet. Check **I use a proxy to connect to the Internet**. The type is **SOCKS5**, the address is `127.0.0.1`, and the port is `10808`. Click **OK**.
I have found it more reliable to click **Select a Built-In Bridge**. This should not be necessary, since the Xray server is already outside the GFW. Perhaps it helps because built-in bridges are faster than random entry nodes. Select **obfs4**. Click **Connect**.
Now you can test your connection by trying to reach a Tor-only site.
BBC News in simplified Chinese:
```
https://www.bbcweb3hytmzhn5d532owbu6oqadra5z3ar726vq5kgwwn6aucdccrad.onion/zhongwen/simp
```
DW News in simplified Chinese:
```
https://www.dwnewsgngmhlplxy6o2twtfgjnrnjxbegbwqx6wnotdhkzt562tszfid.onion/zh/?zhongwen=simp
```
New York Times in simplified Chinese:
```
https://cn.nytimesn7cgmftshazwhfgzm37qxb44r64ytbb2dj3x62d2lljsciiyd.onion
```
![dw-onion-simplified-chinese](/uploads/37794d56098885a7979eb2230e140737/dw-onion-simplified-chinese.png)meskiomeskio@torproject.orgmeskiomeskio@torproject.orghttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/41870Modern firewall-penetration protocols for Tor in China2023-07-07T10:01:53ZcomputerscotModern firewall-penetration protocols for Tor in ChinaReports on https://github.com/net4people/bbs/issues and https://forum.torproject.org say that both obfs4 and snowflake are blocked by the GFW. There are also doubts about whether the new WebTunnel pluggable transport will work. The GFW d...Reports on https://github.com/net4people/bbs/issues and https://forum.torproject.org say that both obfs4 and snowflake are blocked by the GFW. There are also doubts about whether the new WebTunnel pluggable transport will work. The GFW detects and blocks WebSocket-based proxies.
This is a proof-of-concept for more modern firewall-penetration protocols.
To test these protocols in action, set up an Xray server and client using the latest techniques, for example, https://cscot.pages.dev/2023/07/02/xray-reality-h2. If you follow the sample configuration in that article, you will have a SOCKS5 proxy listening on port `10808` on your client.
Download and install the Tor Browser from https://www.torproject.org.
When you run the Tor Browser for the first time, click **Configure Connection**.
Scroll down and click the **Settings** button at the bottom to configure how you connect to the internet. Check **I use a proxy to connect to the Internet**. The type is **SOCKS5**, the address is `127.0.0.1`, and the port is `10808`. Click **OK**.
I have found it more reliable to click **Select a Built-In Bridge**. This should not be necessary, since the Xray server is already outside the GFW. Perhaps it helps because built-in bridges are faster than random entry nodes. Select **obfs4**. Click **Connect**.
Now you can test your connection by trying to reach a Tor-only site.
BBC News in simplified Chinese:
```
https://www.bbcweb3hytmzhn5d532owbu6oqadra5z3ar726vq5kgwwn6aucdccrad.onion/zhongwen/simp
```
DW News in simplified Chinese:
```
https://www.dwnewsgngmhlplxy6o2twtfgjnrnjxbegbwqx6wnotdhkzt562tszfid.onion/zh/?zhongwen=simp
```
New York Times in simplified Chinese:
```
https://cn.nytimesn7cgmftshazwhfgzm37qxb44r64ytbb2dj3x62d2lljsciiyd.onion
```
![dw-onion-simplified-chinese](/uploads/c696b775dc1f976880b42e8100342f54/dw-onion-simplified-chinese.png)meskiomeskio@torproject.orgmeskiomeskio@torproject.orghttps://gitlab.torproject.org/tpo/applications/tor-browser-build/-/issues/40883Verification issues with the new Windows code signing certificate2023-08-17T21:35:26Zcypherpunks1Verification issues with the new Windows code signing certificateThe new certificate cannot be verified on two systems that I tried it.
A comparison of the 12.0.4 and 12.5a7 installers:
![cert](/uploads/eceecebe2d7a455900271857d7484f25/cert.png)The new certificate cannot be verified on two systems that I tried it.
A comparison of the 12.0.4 and 12.5a7 installers:
![cert](/uploads/eceecebe2d7a455900271857d7484f25/cert.png)cypherpunks1cypherpunks1https://gitlab.torproject.org/tpo/tpa/team/-/issues/41222Is the web ui disabled for our VictoriaMetrics version?2023-06-13T12:37:36ZHiroIs the web ui disabled for our VictoriaMetrics version?I see the web ui for VictoriaMetrics at https://metrics-db.torproject.org/vmui/ is returning a 404.
\@gkI see the web ui for VictoriaMetrics at https://metrics-db.torproject.org/vmui/ is returning a 404.
\@gkSponsor 112 : Combating Malicious RelaysJérôme Charaouilavamind@torproject.orgJérôme Charaouilavamind@torproject.orghttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/41829Error after run make build, trying to build tor browser from source2023-07-06T18:15:47ZwaterglassError after run make build, trying to build tor browser from sourceI am trying to build tor browser from source according wiki. I get the following error when run `make build`.
```
./build.sh /home/$USER/tor-browser/tools/torbrowser/../..
0:00.37 Clobber not needed.
Config object not found by mach.
...I am trying to build tor browser from source according wiki. I get the following error when run `make build`.
```
./build.sh /home/$USER/tor-browser/tools/torbrowser/../..
0:00.37 Clobber not needed.
Config object not found by mach.
0:00.46 Using Python 3.10.6 from /home/$USER/tor-browser/obj-x86_64-pc-linux-gnu/_virtualenvs/build/bin/python
0:00.46 Adding configure options from /home/$USER/tor-browser/mozconfig
0:00.46 --enable-application=browser
0:00.46 --enable-official-branding
0:00.46 --enable-optimize
0:00.47 --enable-rust-simd
0:00.47 --enable-verify-mar
0:00.47 --enable-nss-mar
0:00.47 --enable-base-browser-update
0:00.47 --enable-bundled-fonts
0:00.47 --disable-tests
0:00.47 --disable-debug
0:00.47 --disable-crashreporter
0:00.47 --disable-webrtc
0:00.47 --disable-parental-controls
0:00.47 --disable-eme
0:00.47 --enable-proxy-bypass-protection
0:00.47 --disable-system-policies
0:00.47 --disable-backgroundtasks
0:00.47 MOZ_TELEMETRY_REPORTING=
0:00.47 --without-wasm-sandboxed-libraries
0:00.47 --with-relative-data-dir=TorBrowser/Data/Browser
0:00.47 --with-distribution-id=org.torproject
0:00.47 --with-branding=browser/branding/tb-nightly
0:00.47 --enable-default-toolkit=cairo-gtk3
0:00.47 --disable-strip
0:00.47 --disable-install-strip
0:00.47 --with-base-browser-version=dev-build
0:00.47 --disable-base-browser-update
0:00.47 --enable-artifact-builds
0:00.47 MOZILLA_OFFICIAL=
0:00.47 checking for vcs source checkout... git
0:00.58 checking for a shell... /usr/bin/sh
0:00.60 checking for host system type... x86_64-pc-linux-gnu
0:00.60 checking for target system type... x86_64-pc-linux-gnu
0:00.66 checking whether cross compiling... no
0:00.71 Traceback (most recent call last):
0:00.71 File "/home/$USER/tor-browser/configure.py", line 349, in <module>
0:00.71 sys.exit(main(sys.argv))
0:00.71 File "/home/$USER/tor-browser/configure.py", line 131, in main
0:00.71 sandbox.run(os.path.join(os.path.dirname(__file__), "moz.configure"))
0:00.71 File "/home/$USER/tor-browser/python/mozbuild/mozbuild/configure/__init__.py", line 516, in run
0:00.71 self._value_for(option)
0:00.71 File "/home/$USER/tor-browser/python/mozbuild/mozbuild/configure/__init__.py", line 621, in _value_for
0:00.71 return self._value_for_option(obj)
0:00.71 File "/home/$USER/tor-browser/python/mozbuild/mozbuild/util.py", line 1061, in method_call
0:00.71 cache[args] = self.func(instance, *args)
0:00.71 File "/home/$USER/tor-browser/python/mozbuild/mozbuild/configure/__init__.py", line 688, in _value_for_option
0:00.71 raise InvalidOptionError(
0:00.71 mozbuild.configure.options.InvalidOptionError: --enable-optimize is not available in this configuration
*** Fix above errors and then restart with "./mach build"
make: *** [Makefile:26: build] Error 1
```waterglasswaterglasshttps://gitlab.torproject.org/tpo/network-health/sbws/-/issues/40155Lower advertised bandwidth/consensus weight on relays with "higher latency"2023-07-03T13:14:12ZNeel Chauhanneel@neelc.orgLower advertised bandwidth/consensus weight on relays with "higher latency"I run four middle relays on a CenturyLink Gigabit connection in Seattle, WA: https://metrics.torproject.org/rs.html#search/neeltorrelay
I noticed that the consensus weight is lower if the latency is generally higher, with four instances...I run four middle relays on a CenturyLink Gigabit connection in Seattle, WA: https://metrics.torproject.org/rs.html#search/neeltorrelay
I noticed that the consensus weight is lower if the latency is generally higher, with four instances on a connection I get ~25 MB/s (~200 Mbps). "higher latency" means generally higher latency from most of the other relays, namely relays in Europe.
I can get around this temporally by pushing large file downloads between my relay instances, with two client instances and relays closer to my area (namely Emerald Onion, Telus, and Ziply Fiber). Right now the advertised bandwidth/consensus weight is lower than it could be.
For a while it seemed fixed, but it came back for some reason.jugajugahttps://gitlab.torproject.org/tpo/tpa/team/-/issues/41158GSOC alias not working so well2023-05-23T14:59:46ZGabagaba@torproject.orgGSOC alias not working so wellIt seems that some people are not getting the mails we send to gsoc at torproject dot org. Can you check who is there please?
We should have nick, diziet, raya, donuts, geko, juga, hiro, al and me.It seems that some people are not getting the mails we send to gsoc at torproject dot org. Can you check who is there please?
We should have nick, diziet, raya, donuts, geko, juga, hiro, al and me.anarcatanarcathttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/41742Enable IPv6 client by default2024-02-19T17:38:26Zagowa338Enable IPv6 client by defaultCurrently, the Tor Browser bundle does not enable IPv6 for connections to entry or guard nodes. This causes the tor browser to get stuck in the "Establishing a Connection" screen while claiming that internet connectivity is properly avai...Currently, the Tor Browser bundle does not enable IPv6 for connections to entry or guard nodes. This causes the tor browser to get stuck in the "Establishing a Connection" screen while claiming that internet connectivity is properly available within the settings page in IPv6-only networks with DNS64 and NAT64.
![image](/uploads/ef2fe02a28186213ecd26477fb9c1e00/image.png)
![image](/uploads/5d87348c1dc28e682742a1e416795e70/image.png)
Log:
```
2023-04-23 11:57:14.691 [NOTICE] New control connection opened from 127.0.0.1.
2023-04-23 11:57:14.691 [NOTICE] New control connection opened from 127.0.0.1.
2023-04-23 11:57:14.706 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
2023-04-23 11:57:18.065 [NOTICE] Opening Socks listener on 127.0.0.1:9150
2023-04-23 11:57:18.065 [NOTICE] Opened Socks listener connection (ready) on 127.0.0.1:9150
2023-04-23 11:57:18.072 [NOTICE] Renaming old configuration file to "D:\Tor Browser\Browser\TorBrowser\Data\Tor\torrc.orig.1"
2023-04-23 11:57:47.906 [NOTICE] Application request when we haven't used client functionality lately. Optimistically trying directory fetches again.
2023-04-23 11:58:21.158 [NOTICE] New control connection opened from 127.0.0.1.
```
Possible solutions:
1. Add `ClientUseIPv6 1` and `ClientPreferIPv6ORPort 1` to the torrc-defaults. As this only influences us using IPv6 for the connection to the entry node, and we're expecting to be on a monitored network already. It doesn't change anything. As establishing a connection with our IPv6 address is the same as someone logging all NAT44 transitions (or not having any NAT, as in, e.g., university networks) is the same threat vector. So changing this default is probably the best and easiest solution. (Also, as a side effect, it improves the performance of the tor client in CG-NAT scenarios)
2. Do #1, but not "just" within the Tor Browser (bundle) but within the tor client itself.
3. Do #1 but only as a fallback when IPv4 fails after user confirmation. I don't see why that would be preferred, but it would also improve the current situation where the tor client gets stuck without any message, and users don't know what to do. Or them assuming Tor is blocked on the network and (try to) requesting bridges where it is neither necessarily helpful nor necessary.
4. Another flavor of #3, add a distinct warning/error message when no IPv4 connectivity is possible and also add a configuration option within Tor Browser to enable IPv6 connectivity. I again don't see why this would be preferred over enabling the client to use IPv6, but ymmv.
5. Detect the presence of NAT64 using a DNS lookup of `ipv4only.arpa` and even if clientUseIPv6 is disabled use IPv6 but only to communicate with IPv4 endpoints. I consider this the worst solution, but I want to mention it, as it is still better than the status quo.
My preferred solutions are #1 and #2, as it is the simplest one to implement.https://gitlab.torproject.org/tpo/tpa/team/-/issues/41132Unable to send Nextcloud Calendar Invitations2023-05-04T19:09:38ZtylerUnable to send Nextcloud Calendar InvitationsHi there!
I am unable to send calendar invites from Nextcloud calendar events. I've had this problem before, but only when trying to send calendar invites from Isabela's personal NC Calendar. I haven't had this problem when trying to ...Hi there!
I am unable to send calendar invites from Nextcloud calendar events. I've had this problem before, but only when trying to send calendar invites from Isabela's personal NC Calendar. I haven't had this problem when trying to send calendar invitations created on my personal NC calendar.
Tyleranarcatanarcathttps://gitlab.torproject.org/tpo/tpa/team/-/issues/41123get a stable TLS private key for https://bridges.torproject.org/2023-10-05T12:59:08Zmeskiomeskio@torproject.orgget a stable TLS private key for https://bridges.torproject.org/We are considering pinning the https://bridges.torproject.org/ TLS private key in Tor Browser. Could that key be configured to don't rotate frequently and only rotate the Let's Encrypt certificate generated for it?We are considering pinning the https://bridges.torproject.org/ TLS private key in Tor Browser. Could that key be configured to don't rotate frequently and only rotate the Let's Encrypt certificate generated for it?anarcatanarcathttps://gitlab.torproject.org/tpo/applications/mullvad-browser/-/issues/145Submit Feedback link in About Mullvad Browser links to connect.mozilla.org2023-03-28T09:20:32ZrichardSubmit Feedback link in About Mullvad Browser links to connect.mozilla.orgFrom the About Mullvad Dialog, the Submit Feedback link goes to https://connect.mozilla.org . Presumably this should go to some Mullvad endpoint, or we should remove the link entirely.From the About Mullvad Dialog, the Submit Feedback link goes to https://connect.mozilla.org . Presumably this should go to some Mullvad endpoint, or we should remove the link entirely.ruihildtruihildthttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/41697issue 41598, "Prevent NoScript from being removed / disabled " is not working...2023-03-28T15:55:21Zcypherpunksissue 41598, "Prevent NoScript from being removed / disabled " is not working the way you are expecting.version 12.0.4 added "Prevent NoScript from being removed / disabled until core functionality has been migrated to Tor Browser" but at least in my tor browser the NoScript add-on stay `disabled`. This is a good thing because add-ons whic...version 12.0.4 added "Prevent NoScript from being removed / disabled until core functionality has been migrated to Tor Browser" but at least in my tor browser the NoScript add-on stay `disabled`. This is a good thing because add-ons which intercept/block traffic can block each other.
Let's just keep this. If you are going to enable this again without my consent I am going to use Tor with Google Chromium anyway.https://gitlab.torproject.org/tpo/tpa/team/-/issues/41104Create new alias ac-admins2023-04-13T14:08:44Zmicahmicah@torproject.orgCreate new alias ac-adminsThe anti-censorship team would benefit from an alias that can be used as a sort of 'role' email address for their team. For example, the azure portal for the meek configuration had Sina configured there, and now it has meskio setup there...The anti-censorship team would benefit from an alias that can be used as a sort of 'role' email address for their team. For example, the azure portal for the meek configuration had Sina configured there, and now it has meskio setup there, but it is a bit of a single point of failure, when that could be configured to be `ac-admins@torproject.org` with it pointing to `meskio`, `shelikhoo`, `cohosh` and `micah`.anarcatanarcathttps://gitlab.torproject.org/tpo/core/tor/-/issues/40764Tor dev 4.8 compile error2023-03-09T17:55:14ZredbearTor dev 4.8 compile errorUnder src/core/or/circuituse.c
this is the original **hs_metrics_failed_rdv(&circ->hs_ident->identity_pk,HS_METRICS_ERR_RDV_PATH);** but it gives error cause passing two arguments while should be one.
i changed it to this on...Under src/core/or/circuituse.c
this is the original **hs_metrics_failed_rdv(&circ->hs_ident->identity_pk,HS_METRICS_ERR_RDV_PATH);** but it gives error cause passing two arguments while should be one.
i changed it to this one and the error disappear **hs_metrics_failed_rdv(&circ->hs_ident->identity_pk);**
The thing is located on /src/features/hs/hs_metrics.h
Someone took this error about this one while compile ?gabi-250gabi-250https://gitlab.torproject.org/tpo/applications/mullvad-browser/-/issues/92On M1 macOS, the browser only start if you manually check Rosetta compatibili...2023-02-28T13:05:43ZruihildtOn M1 macOS, the browser only start if you manually check Rosetta compatibility modeIf you install the Mullvad Browser on M! macOS, the following error message appears:
![image](/uploads/7c54ab7aa97fa9ff39fb7ccb63a79d9f/image.png)
To make it work, you need to:
- Right click on the icon in Applications
- Click on Get In...If you install the Mullvad Browser on M! macOS, the following error message appears:
![image](/uploads/7c54ab7aa97fa9ff39fb7ccb63a79d9f/image.png)
To make it work, you need to:
- Right click on the icon in Applications
- Click on Get Info
- In the General section, tick Open using Rosetta
It will then start. Is there a way to make it run automatically in Rosetta compatibility mode?https://gitlab.torproject.org/tpo/tpa/team/-/issues/41076Revoke tor-security@lists.torproject.org OpenPGP key2023-03-06T15:33:04Zmicahmicah@torproject.orgRevoke tor-security@lists.torproject.org OpenPGP keyNow that #41014 resulted in the `tor-security@lists.tpo` alias being removed, it would be good to revoke the `tor-security@lists.tpo` schleuder list key, so people do not continue to try and use it. That key is on the schleuder side, and...Now that #41014 resulted in the `tor-security@lists.tpo` alias being removed, it would be good to revoke the `tor-security@lists.tpo` schleuder list key, so people do not continue to try and use it. That key is on the schleuder side, and I do not have access to it.
It seems there are two users a `torschleuder` user and a `schleuder` user, and the later one is the one who has access to .gnupg.
I asked @dgoulet to see if he was able to revoke it, but he said, he does not have access to that user.anarcatanarcathttps://gitlab.torproject.org/tpo/tpa/team/-/issues/41052can't push account keyring to alberti: detected dubious ownership in repository2023-02-01T19:30:59ZKezcan't push account keyring to alberti: detected dubious ownership in repository```
$ git push alberti
Enumerating objects: 10, done.
Counting objects: 100% (10/10), done.
Delta compression using up to 12 threads
Compressing objects: 100% (7/7), done.
Writing objects: 100% (8/8), 2.89 KiB | 2.89 MiB/s, done.
Total 8...```
$ git push alberti
Enumerating objects: 10, done.
Counting objects: 100% (10/10), done.
Delta compression using up to 12 threads
Compressing objects: 100% (7/7), done.
Writing objects: 100% (8/8), 2.89 KiB | 2.89 MiB/s, done.
Total 8 (delta 4), reused 1 (delta 0), pack-reused 0
remote: + env -i HOME=/home/kez make -C /srv/db.torproject.org/keyrings
remote: make: Entering directory '/srv/db.torproject.org/keyrings'
remote: umask 002 && \
remote: cd keyring && \
remote: git -c safe.directory=/srv/db.torproject.org/keyrings/keyring.git pull && \
remote: rm -f torproject-keyring.gpg && \
remote: ./build-keyring && \
remote: cp -f torproject-*.gpg ..
remote: fatal: detected dubious ownership in repository at '/srv/db.torproject.org/keyrings/keyring'
remote: To add an exception for this directory, call:
remote:
remote: git config --global --add safe.directory /srv/db.torproject.org/keyrings/keyring
remote: make: *** [Makefile:5: torproject-keyring.gpg] Error 128
remote: make: Leaving directory '/srv/db.torproject.org/keyrings'
To alberti.torproject.org:/srv/db.torproject.org/keyrings/keyring.git
598d96a..96a747f master -> master
```
so we have dubious ownership in the account-keyring repo on alberti. i think the only solution is to add it as a safe directory, unless we want to require everyone to push to the alberti remote as the `git` user.
/cc @anarcat @lavamindanarcatanarcathttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/41602Designing the User Interface of Conjure in Tor Browser2023-05-30T21:43:51ZrichardDesigning the User Interface of Conjure in Tor BrowserFollowing https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/41361 we need to do the UX work for exposing this feature to users.
@cohosh can you reply with a blurb about how conjure works/differs from other bridges, tra...Following https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/41361 we need to do the UX work for exposing this feature to users.
@cohosh can you reply with a blurb about how conjure works/differs from other bridges, tradeoffs, etc so we get a string written for the bridge selection UX ( see https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/41583#note_2870062 for reference).Sponsor 30 - Objective 2.3https://gitlab.torproject.org/tpo/applications/mullvad-browser/-/issues/62Bad UX when attempting run multiple instances of Mullvad Browser2023-03-22T12:08:18ZrichardBad UX when attempting run multiple instances of Mullvad BrowserSo we disable remote execution (if I recall correctly) which prevents the desktop environment from creating new tabs/windows in an existing process(jump list commands in Windows). However, when we attempt to launch a duplicate instance f...So we disable remote execution (if I recall correctly) which prevents the desktop environment from creating new tabs/windows in an existing process(jump list commands in Windows). However, when we attempt to launch a duplicate instance from the desktop environment we get this dialog which is less than helpful:
![image](/uploads/c840bf2c05481577bbb4cb740e1c1de4/image.png)
We probably want to tweak this to be more accurate useful.
/cc @donuts