The Tor Project issueshttps://gitlab.torproject.org/groups/tpo/-/issues2021-07-14T17:00:34Zhttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/20784TBB on OSX: "Something went wrong..."2021-07-14T17:00:34ZTracTBB on OSX: "Something went wrong..."I am new to TOR. Downloaded browser and went to open it. Once opened it stated "Something Went Wrong TOR not working in this browser. For help contact : help@rt.torproject.org
I'm running the latest version of OSX. I do not have a VPN ...I am new to TOR. Downloaded browser and went to open it. Once opened it stated "Something Went Wrong TOR not working in this browser. For help contact : help@rt.torproject.org
I'm running the latest version of OSX. I do not have a VPN as I can not afford to buy one...
Help!
**Trac**:
**Username**: devildevinehttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/20795Torbrowser crashes if it can't DNS resolve the Socks5Proxy host in torrc2022-02-03T19:06:33ZTracTorbrowser crashes if it can't DNS resolve the Socks5Proxy host in torrcUsing Torbrowser 6.0.6 on OS X Yosemite.
When in the office behind our corporate firewall I configure Torbrowser to use our socks5 proxy.
When at home Torbrowser crashes on launch.
If I delete the Sock5Proxy line from torrc it works.
...Using Torbrowser 6.0.6 on OS X Yosemite.
When in the office behind our corporate firewall I configure Torbrowser to use our socks5 proxy.
When at home Torbrowser crashes on launch.
If I delete the Sock5Proxy line from torrc it works.
If I put a dummy entry for my office socks proxy host in /etc/hosts torbrowser doesn't crash.
Tor should trap a failed DNS resolve when validating the proxy config on launch and tell the user that it can't connect to the internet.
**Trac**:
**Username**: gaffer206https://gitlab.torproject.org/tpo/core/tor/-/issues/20849periodic pattern in network connections ofa newly setup relay2020-07-28T15:50:21Ztoralfperiodic pattern in network connections ofa newly setup relayI observed this in August this year and now in the last days again.
I'm just curious if this is the test pattern from the authorities or whatever else is causing this ?I observed this in August this year and now in the last days again.
I'm just curious if this is the test pattern from the authorities or whatever else is causing this ?Tor: unspecifiedhttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/21224Youtube fullscreen errorr in TBB fullscreen mode on MacOS 10.122022-06-22T15:56:57ZTracYoutube fullscreen errorr in TBB fullscreen mode on MacOS 10.12Since the window resizing logic was updated in the 6.5 alphas there is a problem with fullscreen videos on Youtube.
I'm on a fully up to date MacOS Sierra installation and when I put the Tor Browser in the native Mac fullscreen mode and ...Since the window resizing logic was updated in the 6.5 alphas there is a problem with fullscreen videos on Youtube.
I'm on a fully up to date MacOS Sierra installation and when I put the Tor Browser in the native Mac fullscreen mode and then put a Youtube video in fullscreen from that window it only shows in a small rectangle in the upper left corner of the screen.
Other websites with video players don't have this problem.
When I take Tor Browser back out of its fullscreen mode then the Youtube video works fullscreen as normal again but it seems it is overlaying the window and not using the native Mac fullscreen apis.
I can make a screenshot if necessary but it should be easily reproducible.
**Trac**:
**Username**: exattohttps://gitlab.torproject.org/tpo/core/tor/-/issues/21311Exits should resolve IPv6 addresses, regardless of IPv6Exit2022-06-17T17:40:46ZteorExits should resolve IPv6 addresses, regardless of IPv6ExitThat way, clients find out if the hostname they're trying to reach is IPv6-only, and can try an IPv6 exit next time.
Was: launch_resolve() should always resolve AAAA records, regardless of IPv6ExitThat way, clients find out if the hostname they're trying to reach is IPv6-only, and can try an IPv6 exit next time.
Was: launch_resolve() should always resolve AAAA records, regardless of IPv6Exithttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/21331Incorrect default browser window size for ver6.5 on 1024 x 768 resolution s...2022-02-03T19:06:33ZTracIncorrect default browser window size for ver6.5 on 1024 x 768 resolution screens.Starting with Tor Browser Bundle 6.5 A2 or A3 the default browser window size upon startup is incorrect for monitor resolutions of 1024 x 768. The browser window is too narrow and short compared to the 6.0 version. This handicaps...Starting with Tor Browser Bundle 6.5 A2 or A3 the default browser window size upon startup is incorrect for monitor resolutions of 1024 x 768. The browser window is too narrow and short compared to the 6.0 version. This handicaps anonymity.
**Trac**:
**Username**: torgurlhttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/21444Webcam light flashes when I open NoScript menu2022-02-03T19:06:33ZTracWebcam light flashes when I open NoScript menuWhen I click the "NoScript" icon in Tor Browser Bundle version 6.5, my webcam light flashes for a split second, almost like it records something for a split second. I've been having this problem for a while, and decided it's time to file...When I click the "NoScript" icon in Tor Browser Bundle version 6.5, my webcam light flashes for a split second, almost like it records something for a split second. I've been having this problem for a while, and decided it's time to file a bug report for this.
I'm running Gentoo kernel version 4.9.6, I have installed the Tor Browser Bundle with the layman repo git://github.com/MeisterP/torbrowser-overlay.git, and my webcam is a USB device, works properly using V4L kernel drivers, and is considered a UVC input device.
I can record a video of this happening if anybody thinks it would be helpful.
Thanks,
ChatTor
**Trac**:
**Username**: ChatTorhttps://gitlab.torproject.org/tpo/core/tor/-/issues/21446Number of Introduction Points for a (SingleOnion?) HS seems variable, or degr...2020-07-28T02:23:17ZalecmuffettNumber of Introduction Points for a (SingleOnion?) HS seems variable, or degrades with timeI'm helping some people tune a very large Tor Onion site which has recently converted to 2.9.9 and Single Onions.
There have been some strange reachability issues which I am helping triage.
Analysis is tricky because independent copie...I'm helping some people tune a very large Tor Onion site which has recently converted to 2.9.9 and Single Onions.
There have been some strange reachability issues which I am helping triage.
Analysis is tricky because independent copies of the onion exist in two different datacentres, and they both descriptors into the HSDirs.
To date this configuration has not contributed to any outages that we're aware.
For this ticket the specific onion address is "fbsbx2q4mvcl63pw" - though at least one other onion address (out of 3) has been showing the same symptoms.
All onions are configured with "HiddenServiceNumIntroductionPoints 10"
I have been monitoring the Onion descriptors with a Stem script* that prints the HS Descriptor IPs, and over time the listed IPs appear to drop from the expected 10, to as low as 4.
Partial output from the script log, for this morning, is at:
https://gist.github.com/alecmuffett/2910328730012f9af3410a28e5e6071e
At 0800h the IPs in retrieved HSDescriptor (reminder: from one of two purposely-duplicated HS instances) looked like this, lines 1..12 in the Gist; note NumIntroductionPoints/nip=10
Mon 13 Feb 2017 08:00:55 GMT
v=2 age=55 nip=10 pub(2017-02-13 08:00:00) now(2017-02-13 08:00:55) fbsbx2q4mvcl63pw
0: 134.19.177.109:443
1: 178.254.20.134:9001
2: 185.73.220.8:443
3: 188.114.140.245:9001
4: 37.187.4.8:21
5: 46.101.102.71:443
6: 46.4.49.201:9001
7: 62.210.82.44:21
8: 62.210.92.11:9001
9: 83.44.207.3:9001
Yet further down the file, a different descriptor, possibly from the other instance (lines 50-57)
Mon 13 Feb 2017 08:21:03 GMT
v=2 age=1263 nip=6 pub(2017-02-13 08:00:00) now(2017-02-13 08:21:03) fbsbx2q4mvcl63pw
0: 188.118.217.236:443
1: 192.42.116.161:9001
2: 37.187.4.8:21
3: 80.248.208.131:9001
4: 82.165.207.102:9001
5: 88.190.210.240:9001
...only 6 introduction points.
If we assume (?) that it's unlikely for the two daemons to pick the same introduction point, the fact that "188.118.217.236:443" is present in all the descriptors in lines 40..150 suggests that all these descriptors are from the same daemon instance - however the number of introduction points varies.
See attached image for highlight. Is this expected?
*script: https://github.com/alecmuffett/halfagigonion/blob/master/ls-hsdir.pyTor: unspecifiedhttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/21483DuckDuckGo Onion should be the default instead of DuckDuckGo2023-06-14T21:14:29ZTracDuckDuckGo Onion should be the default instead of DuckDuckGoNow that single onion services are a thing it seems that DuckDuckGo Onion should be the default
**Trac**:
**Username**: lolscreenNow that single onion services are a thing it seems that DuckDuckGo Onion should be the default
**Trac**:
**Username**: lolscreenhttps://gitlab.torproject.org/tpo/core/tor/-/issues/21511State.tmp is not erased and it may contain sensitive information2020-07-28T02:45:44ZTracState.tmp is not erased and it may contain sensitive informationThis is not a bug, but can improve the TOR browser.
The TorBrowser\Browser\TorBrowser\Data\Tor\state.tmp is not erased when TOR exits, in my tests it was not even erased after rebooting the computer.
**Trac**:
**Username**: ric_smThis is not a bug, but can improve the TOR browser.
The TorBrowser\Browser\TorBrowser\Data\Tor\state.tmp is not erased when TOR exits, in my tests it was not even erased after rebooting the computer.
**Trac**:
**Username**: ric_smTor: unspecifiedhttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/21763Improve Cookie settings2022-07-26T12:50:13ZcypherpunksImprove Cookie settingsabout:preferences#privacy
Before:
[_] Accept Cookies from sites
After:
[_] Accept Cookies from clearnet sites
[X] Accept Cookies from .onion sites
I had to add my .onion site to "Exceptions"(Allow for session).
It automatically cleare...about:preferences#privacy
Before:
[_] Accept Cookies from sites
After:
[_] Accept Cookies from clearnet sites
[X] Accept Cookies from .onion sites
I had to add my .onion site to "Exceptions"(Allow for session).
It automatically cleared when I restart the browser.
Please make this permanent by:
a) Add new option: [X] Don't clear my cookie exceptions list.
b) Or, add new cookie option, like above.https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/21798Does not display the manually added root certificats2022-02-03T19:06:19ZTracDoes not display the manually added root certificatsI added the certificate of a custom AC ("Import") and now I want to remove it. But it does not appear in the list "View Certificates", making it impossible to remove.
Tor Browser 6.5.1 (updated today) running on a Debian machine. I test...I added the certificate of a custom AC ("Import") and now I want to remove it. But it does not appear in the list "View Certificates", making it impossible to remove.
Tor Browser 6.5.1 (updated today) running on a Debian machine. I tested with the CAcert http://cacert.org/ root certificate.
On the same machine, a Firefox 45.7.0 does not show the problem: "View certificates" show me my manually added certificates.
**Trac**:
**Username**: bortzmeyerhttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/21802Login failure with Tor Browser: Error loading content, try again.2021-03-18T11:47:11ZTracLogin failure with Tor Browser: Error loading content, try again.Hi,
I'll try to rejoin on this site (http://www.l2amerika.com/#!/vote/vote), but i can't log in anymore there. I get this message from the site "**Error loading content, try again.**"
**IMAGE:** https://postimg.org/image/xvsz53sxz/
**...Hi,
I'll try to rejoin on this site (http://www.l2amerika.com/#!/vote/vote), but i can't log in anymore there. I get this message from the site "**Error loading content, try again.**"
**IMAGE:** https://postimg.org/image/xvsz53sxz/
**Trac**:
**Username**: CodyRohttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/21806webgl hangs on Tor Browser2022-02-03T19:06:19ZArthur Edelsteinwebgl hangs on Tor BrowserCynthia and Tim observed this. First go to http://hexgl.bkcore.com/play . Then click NoScript to allow webgl. Seen on mac.Cynthia and Tim observed this. First go to http://hexgl.bkcore.com/play . Then click NoScript to allow webgl. Seen on mac.https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/21973Fonts settings changed badly in 7.0a3 on Win 72022-02-03T19:06:19ZcypherpunksFonts settings changed badly in 7.0a3 on Win 7Fonts look blurry in Browser Console, something is wrong or is this a new feature?
Security Settings text becomes scrollable when set to High.Fonts look blurry in Browser Console, something is wrong or is this a new feature?
Security Settings text becomes scrollable when set to High.https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/22000update OSX browser sandbox profile for e10s2022-07-12T23:33:44ZKathleen Bradeupdate OSX browser sandbox profile for e10sFor compatibility with e10s, the TB.sb file needs to be updated to allow creation of content processes.For compatibility with e10s, the TB.sb file needs to be updated to allow creation of content processes.https://gitlab.torproject.org/tpo/core/tor/-/issues/22094Creating private_key/hostname fails with "RO filesystem" message but target d...2020-07-27T19:39:17ZTracCreating private_key/hostname fails with "RO filesystem" message but target dir is actually RWVersion: 0.2.9.10 (git-e28303bcf90b842d) on debian jessie live iso
## Problem
```
Apr 28 10:22:58.000 [warn] Couldn't open "/var/tor/hidden_site/private_key.tmp" (/var/tor/hidden_site/private_key) for writing: Read-only file system
Apr...Version: 0.2.9.10 (git-e28303bcf90b842d) on debian jessie live iso
## Problem
```
Apr 28 10:22:58.000 [warn] Couldn't open "/var/tor/hidden_site/private_key.tmp" (/var/tor/hidden_site/private_key) for writing: Read-only file system
Apr 28 10:22:58.000 [err] Couldn't write generated key to "/var/tor/hidden_site/private_key".
```
## Wanted behaviour
These files are to be written in a directory which *IS* writable by the designated running user
These error/warning message seem wrong, and the creating of the hidden service is rendered impossible, if running through systemd
## Steps to reproduce
1) run debian-live-8.7.1-amd64-standard.iso is live mode
2) run following commands
```
gpg --keyserver keys.gnupg.net --recv A3C4F0F979CAA22CDBA8F512EE8CBC9E886DDD89
gpg --export A3C4F0F979CAA22CDBA8F512EE8CBC9E886DDD89 | sudo apt-key add -
cat << "EOF" | sudo tee /etc/apt/sources.list.d/tor.list
deb http://deb.torproject.org/torproject.org jessie main
deb-src http://deb.torproject.org/torproject.org jessie main
EOF
sudo apt-get update
sudo apt-get install deb.torproject.org-keyring
sudo apt-get install tor
sudo systemctl stop tor
sudo mkdir -p /var/tor
sudo mount -t tmpfs tmpfs /var/tor/
sudo mkdir -p /var/tor/hidden_site
sudo chmod 700 /var/tor/hidden_site
sudo chown debian-tor:debian-tor /var/tor/hidden_site
cat << "EOF" | sudo tee /etc/tor/torrc
HiddenServiceDir /var/tor/hidden_site
HiddenServicePort 80 127.0.0.1:8080
EOF
sudo -u debian-tor tor --verify-config
sudo systemctl start tor
```
NOTE: mounting a tmpfs is just an attempt at making sure no RO filesystem was in the game...
3) tor log
```
Apr 28 10:22:58.000 [notice] Tor 0.2.9.10 (git-e28303bcf90b842d) opening log file.
Apr 28 10:22:58.067 [notice] Tor 0.2.9.10 (git-e28303bcf90b842d) running on Linux with Libevent 2.0.21-stable, OpenSSL 1.0.1t and Zlib 1.2.8.
Apr 28 10:22:58.067 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning
Apr 28 10:22:58.067 [notice] Read configuration file "/usr/share/tor/tor-service-defaults-torrc".
Apr 28 10:22:58.067 [notice] Read configuration file "/etc/tor/torrc".
Apr 28 10:22:58.071 [notice] Opening Socks listener on 127.0.0.1:9050
Apr 28 10:22:58.000 [warn] Couldn't open "/var/tor/hidden_site/private_key.tmp" (/var/tor/hidden_site/private_key) for writing: Read-only file system
Apr 28 10:22:58.000 [err] Couldn't write generated key to "/var/tor/hidden_site/private_key".
Apr 28 10:22:58.000 [warn] Error loading rendezvous service keys
Apr 28 10:22:58.000 [err] set_options(): Bug: Acting on config options left us in a broken state. Dying. (on Tor 0.2.9.10 )
```
## Actual mountpoints
```
aufs on / type aufs (rw,noatime,si=2cb2b7e036b24d5d,noxino)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime)
mqueue on /dev/mqueue type mqueue (rw,relatime)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devtmpfs on /dev type devtmpfs (rw,nosuid,size=10240k,nr_inodes=124323,mode=755)
/dev/sr0 on /lib/live/mount/medium type iso9660 (ro,noatime)
tmpfs on /lib/live/mount/overlay type tmpfs (rw,noatime,mode=755)
tmpfs on /lib/live/mount/overlay type tmpfs (rw,relatime)
/dev/loop0 on /lib/live/mount/rootfs/filesystem.squashfs type squashfs (ro,noatime)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=22,pgrp=1,timeout=300,minproto=5,maxproto=5,direct)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
rpc_pipefs on /run/rpc_pipefs type rpc_pipefs (rw,relatime)
tmpfs on /run type tmpfs (rw,nosuid,relatime,size=204864k,mode=755)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev,relatime)
tmpfs on /var/tor type tmpfs (rw,relatime)
```
## Manual run
If instead of running tor via systemctl, we then launch it manually in shell through ssh :
```
sudo /usr/bin/tor --defaults-torrc /usr/share/tor/tor-service-defaults-torrc -f /etc/tor/torrc --RunAsDaemon 0
```
`ps auxf` confirms it runs as `debian-tor`.
Here everything goes fine :
```
Apr 28 13:00:41.281 [notice] Tor 0.2.9.10 (git-e28303bcf90b842d) running on Linux with Libevent 2.0.21-stable, OpenSSL 1.0.1t and Zlib 1.2.8.
Apr 28 13:00:41.281 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning
Apr 28 13:00:41.281 [notice] Read configuration file "/usr/share/tor/tor-service-defaults-torrc".
Apr 28 13:00:41.282 [notice] Read configuration file "/etc/tor/torrc".
Apr 28 13:00:41.286 [notice] Opening Socks listener on 127.0.0.1:9050
Apr 28 13:00:41.000 [notice] Tor 0.2.9.10 (git-e28303bcf90b842d) opening log file.
Apr 28 13:00:41.281 [notice] Tor 0.2.9.10 (git-e28303bcf90b842d) running on Linux with Libevent 2.0.21-stable, OpenSSL 1.0.1t and Zlib 1.2.8.
Apr 28 13:00:41.281 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning
Apr 28 13:00:41.281 [notice] Read configuration file "/usr/share/tor/tor-service-defaults-torrc".
Apr 28 13:00:41.282 [notice] Read configuration file "/etc/tor/torrc".
Apr 28 13:00:41.286 [notice] Opening Socks listener on 127.0.0.1:9050
Apr 28 13:00:41.000 [notice] Parsing GEOIP IPv4 file /usr/share/tor/geoip.
Apr 28 13:00:41.000 [notice] Parsing GEOIP IPv6 file /usr/share/tor/geoip6.
Apr 28 13:00:41.000 [notice] Bootstrapped 0%: Starting
Apr 28 13:00:41.000 [notice] Bootstrapped 80%: Connecting to the Tor network
Apr 28 13:00:42.000 [notice] Opening Socks listener on /var/run/tor/socks
Apr 28 13:00:42.000 [notice] Opening Control listener on /var/run/tor/control
Apr 28 13:00:42.000 [notice] Bootstrapped 85%: Finishing handshake with first hop
Apr 28 13:00:42.000 [notice] Bootstrapped 90%: Establishing a Tor circuit
Apr 28 13:00:43.000 [notice] Tor has successfully opened a circuit. Looks like client functionality is working.
Apr 28 13:00:43.000 [notice] Bootstrapped 100%: Done
```
The hidden service files are created :
```
sudo find /var/tor -ls
31802 0 drwxrwxrwt 3 root root 60 Apr 28 12:30 /var/tor
31841 0 drwx------ 2 debian-tor debian-tor 80 Apr 28 13:00 /var/tor/hidden_site
36795 4 -rw------- 1 debian-tor debian-tor 23 Apr 28 13:00 /var/tor/hidden_site/hostname
36794 4 -rw------- 1 debian-tor debian-tor 887 Apr 28 13:00 /var/tor/hidden_site/private_key
```
**Trac**:
**Username**: nipilTor: unspecifiedhttps://gitlab.torproject.org/tpo/tpa/schleuder/-/issues/22260Schleuder does not decrypt and re-encrypt attachments2020-06-27T14:15:58ZteorSchleuder does not decrypt and re-encrypt attachmentsInstead, it sends them encrypted with the tor-network-security key.
So this isn't a security issue, but it would be nice to get it to work.Instead, it sends them encrypted with the tor-network-security key.
So this isn't a security issue, but it would be nice to get it to work.HiroHirohttps://gitlab.torproject.org/tpo/core/tor/-/issues/22453Relays should regularly do a larger bandwidth self-test2022-08-30T12:40:03ZRoger DingledineRelays should regularly do a larger bandwidth self-testInspired by legacy/trac#8247 ("In sum. a vestigial tiny bw self-test seems silly to keep around"), I wonder if we're at the point where we can just take out all the bandwidth self-test infrastructure.
In favor of ripping it out: there's...Inspired by legacy/trac#8247 ("In sum. a vestigial tiny bw self-test seems silly to keep around"), I wonder if we're at the point where we can just take out all the bandwidth self-test infrastructure.
In favor of ripping it out: there's some complexity at relay startup where we try to delay publishing our descriptor until we've done the self-test, since we know we'll have a newer bandwidth number to include soon. We've had bugs in this delay step.
In favor of ripping it out: in the current design we try to build 4 separate circuits, without using our guards in order to have actually independent paths, for pushing our 500KB. Relays that aren't reachable end up with hundreds or thousands of connections open, because they keep making new circuits and each one probably is to a new relay. Not a big deal but kind of unfortunate.
In favor of ripping it out: 50KB, which is the most that the current bandwidth test can tell you, is super tiny compared to current descriptor bandwidths and current consensus weights. In fact, as prophesied in legacy/trac#8247, the threshold for the Fast flag is now above 50KB, so publishing 0 vs 50 is essentially just moving you around within the "don't use, they're too slow" bucket.
In favor of keeping it: maybe the bandwidth authorities have some sort of psychotic behavior in the face of relays that have a 0 in their descriptor? Like, they multiply the 0 by a factor for how much better than the other 0's they are? I have no idea. In case they do, I propose that we proceed with ripping out the self-test, and simply replace it with the number "20KB" to guard against psychotic bwauth behavior. (I picked that number because the directory authorities already use the number 20 when assigning a weight to a relay that (A) is unmeasured and (B) self-declares at least 20KB in its descriptor.)
Note: if we do keep it in, here's a better design:
https://trac.torproject.org/projects/tor/ticket/22453#comment:35
But what about bridges, you might ask? Public relays might have the bwauths to measure them remotely, but bridges don't have that. I think nothing uses the bandwidths in bridge descriptors. Are there any plans for that to change in the future? Even if there are, I think raising the floor from 0 to 20, and retaining the behavior where we publish a bigger number if we actually see a bigger number due to client load, should make us compatible with whatever these plans might be.https://gitlab.torproject.org/tpo/core/tor/-/issues/22489Bridge oftenly reports Failed to find node for hop 0 of our path. Discarding ...2020-07-28T03:36:35Zs7rBridge oftenly reports Failed to find node for hop 0 of our path. Discarding this circuit.I have just setup an obfs4 bridge on `0.3.1.2-alpha-dev (git-1763aa058b08a1c5)` on FreeBSD. I am using it as a client from another computer and it works well, except I see this warn in the log files of the bridge relay instance:
```
Jun ...I have just setup an obfs4 bridge on `0.3.1.2-alpha-dev (git-1763aa058b08a1c5)` on FreeBSD. I am using it as a client from another computer and it works well, except I see this warn in the log files of the bridge relay instance:
```
Jun 03 21:54:41.000 [warn] Failed to find node for hop 0 of our path. Discarding this circuit.
Jun 03 21:58:08.000 [warn] Failed to find node for hop 0 of our path. Discarding this circuit.
Jun 03 22:01:30.000 [warn] Failed to find node for hop 0 of our path. Discarding this circuit.
Jun 03 22:04:37.000 [warn] Failed to find node for hop 0 of our path. Discarding this circuit.
Jun 03 22:07:45.000 [warn] Failed to find node for hop 0 of our path. Discarding this circuit.
Jun 03 22:11:27.000 [warn] Failed to find node for hop 0 of our path. Discarding this circuit.
Jun 03 23:03:04.000 [warn] Failed to find node for hop 0 of our path. Discarding this circuit.
Jun 03 23:06:14.000 [warn] Failed to find node for hop 0 of our path. Discarding this circuit.
Jun 03 23:09:49.000 [warn] Failed to find node for hop 0 of our path. Discarding this circuit.
Jun 03 23:13:19.000 [warn] Failed to find node for hop 0 of our path. Discarding this circuit.
Jun 03 23:16:08.000 [warn] Failed to find node for hop 0 of our path. Discarding this circuit.
Jun 03 23:19:41.000 [warn] Failed to find node for hop 0 of our path. Discarding this circuit.
Jun 03 23:23:48.000 [warn] Failed to find node for hop 0 of our path. Discarding this circuit.
Jun 03 23:27:13.000 [warn] Failed to find node for hop 0 of our path. Discarding this circuit.
Jun 03 23:30:52.000 [warn] Failed to find node for hop 0 of our path. Discarding this circuit.
Jun 03 23:34:55.000 [warn] Failed to find node for hop 0 of our path. Discarding this circuit.
Jun 03 23:38:13.000 [warn] Failed to find node for hop 0 of our path. Discarding this circuit.
Jun 03 23:41:54.000 [warn] Failed to find node for hop 0 of our path. Discarding this circuit.
Jun 03 23:45:18.000 [warn] Failed to find node for hop 0 of our path. Discarding this circuit.
Jun 03 23:48:39.000 [warn] Failed to find node for hop 0 of our path. Discarding this circuit.
Jun 03 23:52:21.000 [warn] Failed to find node for hop 0 of our path. Discarding this circuit.
Jun 03 23:55:56.000 [warn] Failed to find node for hop 0 of our path. Discarding this circuit.
```
There are a lot of similar messages, no sense to provide all of them since they're all the same.Tor: unspecified