Tor issueshttps://gitlab.torproject.org/tpo/core/tor/-/issues2023-05-30T18:39:08Zhttps://gitlab.torproject.org/tpo/core/tor/-/issues/33669"Pluggable Transport process terminated" but Tor keeps on going (and of cours...2023-05-30T18:39:08ZRoger Dingledine"Pluggable Transport process terminated" but Tor keeps on going (and of course doesn't work)In https://trac.torproject.org/projects/tor/ticket/33336#comment:20 I encountered the unfortunate situation where my snowflake client exited:
```
Feb 25 14:36:24.458 [warn] Pluggable Transport process terminated with status code 512
```
...In https://trac.torproject.org/projects/tor/ticket/33336#comment:20 I encountered the unfortunate situation where my snowflake client exited:
```
Feb 25 14:36:24.458 [warn] Pluggable Transport process terminated with status code 512
```
It still remains unclear whether snowflake had a bug that crashed it, or if Tor has a bug that made it close the socket to snowflake.
But either way, after this event Tor quietly cries to itself:
```
Feb 25 14:36:44.825 [warn] The connection to the SOCKS5 proxy server at 127.0.0.1:45527 just failed. Make sure that the proxy server is up and running.
```
and Tor Browser has no idea this is happening, or that trying to use Tor is now hopeless.
We should figure out something smarter that Tor should do in this situation. Perhaps it should exit, forcing the user to notice? Perhaps it should emit an event that Tor Browser picks up on? Maybe we have an even better idea?Tor: 0.4.8.x-freezeAlexander Færøyahf@torproject.orgAlexander Færøyahf@torproject.org2023-05-31https://gitlab.torproject.org/tpo/core/tor/-/issues/30105"pr" lines in consensus can have trailing whitespace2021-09-16T14:19:58Zirl"pr" lines in consensus can have trailing whitespacedir-spec specifies keyword lines as:
```
KeywordLine ::= Keyword NL | Keyword WS ArgumentChar+ NL
```
However, observed in the wild:
```
pr
```
There is trailing whitespace on line 1840 of the [[19:00:00 consensus](https://collector...dir-spec specifies keyword lines as:
```
KeywordLine ::= Keyword NL | Keyword WS ArgumentChar+ NL
```
However, observed in the wild:
```
pr
```
There is trailing whitespace on line 1840 of the [[19:00:00 consensus](https://collector.torproject.org/recent/relay-descriptors/consensuses/2019-04-09-19-00-00-consensus|2019-04-09)]. It is at line 1840.
As the directory authorities all seem to agree that this trailing whitespace should be there we don't have an issue, but it's against the spec and has likely happened by accident.
If we accidentally remove the trailing whitespace, we don't have a consensus anymore.
Options for fixing this are:
* require trailing whitespace for pr lines with no arguments
* make a new consensus method that doesn't have trailing whitespace
Either way, this needs a spec change before we write any code.https://gitlab.torproject.org/tpo/core/tor/-/issues/21073"PredictedPortsRelevanceTime 0" causes stagnant/uncommunicative onion service...2020-06-27T13:57:28Zalecmuffett"PredictedPortsRelevanceTime 0" causes stagnant/uncommunicative onion services, stale descriptorsI am running 72 tor daemons with the following spec:
Tor 0.2.9.7-rc (git-6b6ad81c2e140d85) running on Linux with Libevent 2.0.21-stable, OpenSSL 1.0.1t and Zlib 1.2.8.
...on a cluster of identical Raspberry Pi hardware.
The goal is to...I am running 72 tor daemons with the following spec:
Tor 0.2.9.7-rc (git-6b6ad81c2e140d85) running on Linux with Libevent 2.0.21-stable, OpenSSL 1.0.1t and Zlib 1.2.8.
...on a cluster of identical Raspberry Pi hardware.
The goal is to experiment with Tor bandwidth via OnionBalance, so I have been tweaking configurations because a cluster of N tor daemons doesn't really benefit from predictive persistent anything.
The configuration (text in the footer) in about 8% of cases, creates a daemon which, after initial upload, appears to never (or-only-very-rarely - unsure) refresh its descriptors in an HSDir.
This behaviour stops when "PredictedPortsRelevanceTime 0" is commented out.
Using a small custom Stem script, I query the age of the 72 daemons' descriptor; the vast majority are less than 2 hours old, but some - the afflicted daemons - are 10+hours old.
Sample output from my tool:
```
19:25:22 mistral:~ $ ls-hsdir `cat Dropbox/all-onions.txt`
v=2 age=5183 pub(2016-12-23 18:00:00) 2pnhm32wvh2g6bod
v=2 age=5183 pub(2016-12-23 18:00:00) 2ss5hl24km3cnedb
# unavailable 44kpqx3wj4pdj4x3
v=2 age=1583 pub(2016-12-23 19:00:00) 457vhfiipyfahsw2
v=2 age=5183 pub(2016-12-23 18:00:00) 4byeybc6yyqvxc64
v=2 age=12383 pub(2016-12-23 16:00:00) 4sj56yfqt6iimah2
v=2 age=5183 pub(2016-12-23 18:00:00) 57j6n5nsrvl2n3lm
# unavailable 5imawjwdy2332sk2
v=2 age=5183 pub(2016-12-23 18:00:00) 5k2ukr3gjxw4iuwo
v=2 age=12383 pub(2016-12-23 16:00:00) 6bdgdiyoqdaq65oh
v=2 age=1583 pub(2016-12-23 19:00:00) 6egxpvvszfzriamo
v=2 age=5183 pub(2016-12-23 18:00:00) 7rydmwifplyugjzg
v=2 age=5183 pub(2016-12-23 18:00:00) a7ls3tboibdtexpa
v=2 age=66383 pub(2016-12-23 01:00:00) apk2wb3qdwzovtdj
v=2 age=1583 pub(2016-12-23 19:00:00) av6plyhrd5j7enoo
v=2 age=1583 pub(2016-12-23 19:00:00) awocgbvyljq4nf2p
v=2 age=5183 pub(2016-12-23 18:00:00) ayzn2s76oh4eqw45
v=2 age=37583 pub(2016-12-23 09:00:00) b6rzknxn664juice
# unavailable bnuy3zlmrnvljylh
v=2 age=1583 pub(2016-12-23 19:00:00) btxtnep4ipsgiq6j
...
...
```
The daemons, despite some having such old descriptors, are all still reachable some 21 hours after launch
I shall be taking these (cited) daemons down, but can recreate them pretty easily.
Purely speculatively, it does sound vaguely similar to this Ricochet issue which arma reported to Ricochet: https://github.com/ricochet-im/ricochet/issues/245
I have 2x 'debug' logs from the same physical machine, one which is of a 'good' daemon and the other 'stale' daemon, running concurrently. The 'good' log is 35Mb versus the 'stale' 27Mb, but comparison with other logs does not suggest a strong correlation for stale daemons vs: logfile size.
The files are presumably too large to attach? Even after compression they will be several Mb.
Running carml on an stale daemon for HS_DESC activity showed little of note. Surprisingly little, even.
I'm stuck for ideas, but am aware that a very large site uses this option in its 2.7 config, so it would be good to know if it is needed and/or helpful for SingleOnions in 2.9, and.or also bugfixed.
```
19:28:24 rig2:hs2.d $ more config
DataDirectory /home/alecm/master/halfagig/hs2.d
HiddenServiceDir /home/alecm/master/halfagig/hs2.d
ControlPort unix:/home/alecm/master/halfagig/hs2.d/control.sock
SocksPort 0
Log debug file /home/alecm/master/halfagig/hs2.d/log.txt
SafeLogging 0
HeartbeatPeriod 60 minutes
# HiddenServicePort 19 localhost:8502
# HiddenServicePort 22 localhost:22
HiddenServicePort 80 localhost:10502
HiddenServiceNumIntroductionPoints 3
LongLivedPorts 19,22,80
#
# CircuitBuildTimeout 60
# LearnCircuitBuildTimeout 0
PredictedPortsRelevanceTime 0
# UseEntryGuards 0
# UseEntryGuardsAsDirGuards 0
```Tor: unspecifiedhttps://gitlab.torproject.org/tpo/core/tor/-/issues/2408"PublishServerDescriptor hidserv" publishes a public relay descriptor2020-06-27T14:08:46ZRobert Ransom"PublishServerDescriptor hidserv" publishes a public relay descriptorI ran a Tor instance with the following lines in its torrc:
```
ORPort 51412
BridgeRelay 1
ExitPolicy reject *:*
PublishServerDescriptor hidserv
```
(There were other non-comment lines in the torrc, including lines specifying hidden se...I ran a Tor instance with the following lines in its torrc:
```
ORPort 51412
BridgeRelay 1
ExitPolicy reject *:*
PublishServerDescriptor hidserv
```
(There were other non-comment lines in the torrc, including lines specifying hidden services, but those are not relevant.)
I expected this Tor instance to publish hidden service descriptors and not publish any router descriptor (whether bridge or public relay). Instead, it published a router descriptor as a public relay.
The `hidserv` parameter to the `PublishServerDescriptor` torrc option is obsolete, it is ignored by the code that publishes hidden service descriptors (even v0 descriptors), and the configuration-parsing code should explicitly ignore it (and print a warning).Robert RansomRobert Ransomhttps://gitlab.torproject.org/tpo/core/tor/-/issues/6238"Removed n/m microdescriptors as old" log message once per hour on notice2020-06-27T14:06:09ZSebastian Hahn"Removed n/m microdescriptors as old" log message once per hour on noticeLooks like we forgot to demote a log message because it only happens after a relay has been running for a couple of days. Probably we should move that message to infoLooks like we forgot to demote a log message because it only happens after a relay has been running for a couple of days. Probably we should move that message to infoTor: 0.2.3.x-finalhttps://gitlab.torproject.org/tpo/core/tor/-/issues/9625"rend_service_introduce(): Bug: Internal error: Got an INTRODUCE22020-06-27T14:03:59ZTrac"rend_service_introduce(): Bug: Internal error: Got an INTRODUCE2"rend_service_introduce(): Bug: Internal error: Got an INTRODUCE2 cell on an intro circ (for service "*******") with no corresponding rend_intro_point_t.
**Trac**:
**Username**: Vasia"rend_service_introduce(): Bug: Internal error: Got an INTRODUCE2 cell on an intro circ (for service "*******") with no corresponding rend_intro_point_t.
**Trac**:
**Username**: VasiaTor: unspecifiedhttps://gitlab.torproject.org/tpo/core/tor/-/issues/17146"Sandbox 1" in chutney makes coverage underreported2020-07-24T18:12:14ZNick Mathewson"Sandbox 1" in chutney makes coverage underreportedI like testing with the sandbox enabled, but it does seem to interfere with storing coverage results.I like testing with the sandbox enabled, but it does seem to interfere with storing coverage results.Tor: unspecifiedhttps://gitlab.torproject.org/tpo/core/tor/-/issues/32295"Skipping obsolete configuration option." doesn't say which one2020-06-27T13:49:00ZRoger Dingledine"Skipping obsolete configuration option." doesn't say which oneIn Tor 0.3.5.x:
```
app/config/confparse.c:
log_warn(LD_CONFIG, "Skipping obsolete configuration option '%s'", c->key);
```
But in 0.4.2.3-alpha:
```
lib/confmgt/type_defs.c:
log_warn(LD_GENERAL, "Skipping obsolete configuration option."...In Tor 0.3.5.x:
```
app/config/confparse.c:
log_warn(LD_CONFIG, "Skipping obsolete configuration option '%s'", c->key);
```
But in 0.4.2.3-alpha:
```
lib/confmgt/type_defs.c:
log_warn(LD_GENERAL, "Skipping obsolete configuration option.");
```
Resulting in log messages like:
```
Oct 25 16:19:28.906 [warn] Skipping obsolete configuration option.
Oct 25 16:19:28.906 [warn] Skipping obsolete configuration option.
```
which are not as helpful as they could be.
The bug went in with commit c60a85d2, which I think first went into 0.4.2.1-alpha.
The new file has a XXXX next to this line:
```
// XXXX move this to a higher level, once such a level exists.
log_warn(LD_GENERAL, "Skipping obsolete configuration option.");
```
but I see that most tickets like legacy/trac#29211 and legacy/trac#30866 are scheduled for 0.4.3.x, and this is an 0.4.2 bug so I am filing a separate ticket.
Bug reported by OFFShare in irc.Tor: 0.4.2.x-finalteorteorhttps://gitlab.torproject.org/tpo/core/tor/-/issues/5373"socksport 2000 testingtornetwork 1" results in socksport 90502020-06-27T14:06:41ZRoger Dingledine"socksport 2000 testingtornetwork 1" results in socksport 9050If you run Tor client with these two options, it ignores your requested socksport.
This is an important bug because it is preventing our Tor network simulators from running the 0.2.3 branch. (Whee.)If you run Tor client with these two options, it ignores your requested socksport.
This is an important bug because it is preventing our Tor network simulators from running the 0.2.3 branch. (Whee.)Tor: 0.2.3.x-finalhttps://gitlab.torproject.org/tpo/core/tor/-/issues/18024"sum" accounting displays bad log message2020-06-27T13:59:48ZNick Mathewson"sum" accounting displays bad log messageWhile doing an implementation for legacy/trac#15989, unixninja fixed this issue. Giving it a bug number for the changelog.While doing an implementation for legacy/trac#15989, unixninja fixed this issue. Giving it a bug number for the changelog.Tor: 0.2.8.x-finalhttps://gitlab.torproject.org/tpo/core/tor/-/issues/25136"system clock jump" warnings still persist2020-06-27T13:54:14ZTrac"system clock jump" warnings still persistThis is an addition to legacy/trac#25052 as it was directly closed before I could reply.
I have changed my relay settings as recommended and disabled the "DirCache", set an "Address" and removed the (in any case temporary) cpu pinning. ...This is an addition to legacy/trac#25052 as it was directly closed before I could reply.
I have changed my relay settings as recommended and disabled the "DirCache", set an "Address" and removed the (in any case temporary) cpu pinning. At least it helped to reduce the "jump clock" warnings to one every one or two hours. But they are not gone.
```
Feb 2 06:08:11 <daemon.notice> Tor[1941]: Heartbeat: Tor's uptime is 1 day 11:27 hours, with 0 circuits open. I've sent 13.59 MB and received 26.91 MB.
Feb 2 06:08:11 <daemon.notice> Tor[1941]: Circuit handshake stats since last time: 0/0 TAP, 0/0 NTor.
Feb 2 06:08:11 <daemon.notice> Tor[1941]: Since startup, we have initiated 0 v1 connections, 0 v2 connections, 0 v3 connections, and 20 v4 connections; and received 11 v1 connections, 22 v2 connections, 0 v3 connections, and 131 v4 connections.
Feb 2 12:08:11 <daemon.notice> Tor[1941]: Heartbeat: Tor's uptime is 1 day 17:27 hours, with 0 circuits open. I've sent 13.59 MB and received 26.91 MB.
Feb 2 12:08:11 <daemon.notice> Tor[1941]: Circuit handshake stats since last time: 0/0 TAP, 0/0 NTor.
Feb 2 12:08:11 <daemon.notice> Tor[1941]: Since startup, we have initiated 0 v1 connections, 0 v2 connections, 0 v3 connections, and 20 v4 connections; and received 11 v1 connections, 22 v2 connections, 0 v3 connections, and 131 v4 connections.
Feb 2 12:11:51 <daemon.notice> Tor[1941]: Your IP address seems to have changed to 178.1.226.79 (METHOD=RESOLVED HOSTNAME=bundesgebaermutter.ddnss.eu). Updating.
Feb 2 12:11:51 <daemon.notice> Tor[1941]: Our IP Address has changed from 178.1.228.74 to 178.1.226.79; rebuilding descriptor (source: METHOD=RESOLVED HOSTNAME=bundesgebaermutter.ddnss.eu).
Feb 2 12:11:57 <daemon.notice> Tor[1941]: Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor.
Feb 2 12:11:58 <daemon.notice> Tor[1941]: Tor has successfully opened a circuit. Looks like client functionality is working.
Feb 2 12:11:58 <daemon.notice> Tor[1941]: Tor has successfully opened a circuit. Looks like client functionality is working.
Feb 2 12:11:58 <daemon.notice> Tor[1941]: Performing bandwidth self-test...done.
Feb 2 14:01:39 <daemon.warning> Tor[1941]: Your system clock just jumped 108 seconds forward; assuming established circuits no longer work.
Feb 2 18:08:11 <daemon.notice> Tor[1941]: Heartbeat: Tor's uptime is 5:54 hours, with 0 circuits open. I've sent 15.22 MB and received 29.82 MB.
Feb 2 18:08:11 <daemon.notice> Tor[1941]: Circuit handshake stats since last time: 0/0 TAP, 9/9 NTor.
Feb 2 18:08:11 <daemon.notice> Tor[1941]: Since startup, we have initiated 0 v1 connections, 0 v2 connections, 0 v3 connections, and 23 v4 connections; and received 11 v1 connections, 25 v2 connections, 0 v3 connections, and 151 v4 connections.
Feb 2 18:44:21 <daemon.warning> Tor[1941]: Your system clock just jumped 1720 seconds forward; assuming established circuits no longer work.
Feb 2 18:47:08 <daemon.warning> Tor[1941]: Your system clock just jumped 107 seconds forward; assuming established circuits no longer work.
Feb 2 20:29:55 <daemon.warning> Tor[1941]: Your system clock just jumped 107 seconds forward; assuming established circuits no longer work.
Feb 2 21:49:42 <daemon.warning> Tor[1941]: Your system clock just jumped 107 seconds forward; assuming established circuits no longer work.
Feb 2 22:56:29 <daemon.warning> Tor[1941]: Your system clock just jumped 107 seconds forward; assuming established circuits no longer work.
Feb 3 00:08:11 <daemon.notice> Tor[1941]: Heartbeat: Tor's uptime is 11:18 hours, with 1 circuits open. I've sent 17.56 MB and received 32.43 MB.
Feb 3 00:08:11 <daemon.notice> Tor[1941]: Circuit handshake stats since last time: 0/0 TAP, 2/2 NTor.
Feb 3 00:08:11 <daemon.notice> Tor[1941]: Since startup, we have initiated 0 v1 connections, 0 v2 connections, 0 v3 connections, and 25 v4 connections; and received 12 v1 connections, 32 v2 connections, 0 v3 connections, and 174 v4 connections.
Feb 3 02:05:15 <daemon.warning> Tor[1941]: Your system clock just jumped 106 seconds forward; assuming established circuits no longer work.
Feb 3 05:19:02 <daemon.warning> Tor[1941]: Your system clock just jumped 105 seconds forward; assuming established circuits no longer work.
Feb 3 06:08:11 <daemon.notice> Tor[1941]: Heartbeat: Tor's uptime is 17:15 hours, with 1 circuits open. I've sent 18.47 MB and received 34.66 MB.
Feb 3 06:08:11 <daemon.notice> Tor[1941]: Circuit handshake stats since last time: 0/0 TAP, 1/1 NTor.
Feb 3 06:08:11 <daemon.notice> Tor[1941]: Since startup, we have initiated 0 v1 connections, 0 v2 connections, 0 v3 connections, and 25 v4 connections; and received 12 v1 connections, 39 v2 connections, 0 v3 connections, and 198 v4 connections.
Feb 3 09:19:20 <daemon.warning> Tor[1941]: Didn't recognize cell, but circ stops here! Closing circ.
Feb 3 09:19:20 <daemon.warning> Tor[1941]: circuit_receive_relay_cell (forward) failed. Closing.
Feb 3 10:38:48 <daemon.warning> Tor[1941]: Your system clock just jumped 105 seconds forward; assuming established circuits no longer work.
Feb 3 12:08:11 <daemon.notice> Tor[1941]: Heartbeat: Tor's uptime is 23:13 hours, with 2 circuits open. I've sent 19.70 MB and received 36.97 MB.
Feb 3 12:08:11 <daemon.notice> Tor[1941]: Circuit handshake stats since last time: 1/1 TAP, 1/1 NTor.
Feb 3 12:08:11 <daemon.notice> Tor[1941]: Since startup, we have initiated 0 v1 connections, 0 v2 connections, 0 v3 connections, and 26 v4 connections; and received 13 v1 connections, 43 v2 connections, 0 v3 connections, and 221 v4 connections.
Feb 3 12:31:37 <daemon.warning> Tor[1941]: Your system clock just jumped 107 seconds forward; assuming established circuits no longer work.
Feb 3 14:43:25 <daemon.warning> Tor[1941]: Your system clock just jumped 108 seconds forward; assuming established circuits no longer work.
Feb 3 16:12:13 <daemon.warning> Tor[1941]: Your system clock just jumped 108 seconds forward; assuming established circuits no longer work.
Feb 3 17:08:00 <daemon.warning> Tor[1941]: Your system clock just jumped 107 seconds forward; assuming established circuits no longer work.
Feb 3 18:09:47 <daemon.warning> Tor[1941]: Your system clock just jumped 107 seconds forward; assuming established circuits no longer work.
Feb 3 18:09:47 <daemon.notice> Tor[1941]: Heartbeat: Tor's uptime is 1 day 5:06 hours, with 2 circuits open. I've sent 23.34 MB and received 41.04 MB.
Feb 3 18:09:47 <daemon.notice> Tor[1941]: Circuit handshake stats since last time: 0/0 TAP, 1/1 NTor.
Feb 3 18:09:47 <daemon.notice> Tor[1941]: Since startup, we have initiated 0 v1 connections, 0 v2 connections, 0 v3 connections, and 35 v4 connections; and received 13 v1 connections, 47 v2 connections, 0 v3 connections, and 264 v4 connections.
Feb 3 19:49:35 <daemon.warning> Tor[1941]: Your system clock just jumped 107 seconds forward; assuming established circuits no longer work.
Feb 3 21:31:23 <daemon.warning> Tor[1941]: Your system clock just jumped 108 seconds forward; assuming established circuits no longer work.
```
The "address-hostname" is resolved by a dynamic dns provider in germany (bundesgebaermutter.ddnss.eu) and Atlas/Metrics shows the fqdn of my dial-up connection (xxxx.vodafone-ip.de). And tor is causing only little spikes in the cpu usage graph now. When the consensus diffs were computed it took half an hour or more at 100 percent on the poor bPi SoC.
Granted, it is a low-volume relay. Maybe I should just shut up ;)
**Trac**:
**Username**: bundesgebaermutterTor: unspecifiedhttps://gitlab.torproject.org/tpo/core/tor/-/issues/4094"TestSocks 1" and IP addresses in requests using "safe" socks protocols resul...2020-06-27T14:07:42Zfk"TestSocks 1" and IP addresses in requests using "safe" socks protocols result in misleading log messagesAccording to the man page, the TestSocks option causes Tor to
"make a notice-level log entry for each connection to the Socks
port indicating whether the request used a safe socks protocol
or an unsafe one".
In case of "safe" socks prot...According to the man page, the TestSocks option causes Tor to
"make a notice-level log entry for each connection to the Socks
port indicating whether the request used a safe socks protocol
or an unsafe one".
In case of "safe" socks protocols Tor however goes a bit
further and always claims:
Your application (using socks(4a|5) to port 80) gave Tor a hostname, which means Tor will do the DNS resolve for you. This is good.
The message is printed even if the application actually gave
Tor an IP address and not a hostname.
I think Tor should either verify that a hostname has been given,
or the log message should be reworded to something like:
Your application (using socks(4a|5) to port 80) instructed Tor
to take care of the DNS resolution itself if necessary. This is good.https://gitlab.torproject.org/tpo/core/tor/-/issues/162"The service did not return an error." message2020-06-27T14:11:07ZTrac"The service did not return an error." messageGet "The service did not return an error." message when trying to stop service in services.msc in windows (on windows XP SP2). It does close the process, and if you try and tell it to stop again, it just hangs for a while, and eventually...Get "The service did not return an error." message when trying to stop service in services.msc in windows (on windows XP SP2). It does close the process, and if you try and tell it to stop again, it just hangs for a while, and eventually says that it stopped. After this you can hit start process, and everything works normally.
[Automatically added by flyspray2trac: Operating System: Windows 2k/XP]
**Trac**:
**Username**: bknobbshttps://gitlab.torproject.org/tpo/core/tor/-/issues/16608"time published in the consensus network status" seems to be wrong2020-09-18T14:20:32Ztoralf"time published in the consensus network status" seems to be wrongI setup a watch dog script which informs me immediately about such log messages.
I checked immediately the time. The time at my server was the same at my desktop and both seems to be accurate (set by ntpd).
That's why I do assume that t...I setup a watch dog script which informs me immediately about such log messages.
I checked immediately the time. The time at my server was the same at my desktop and both seems to be accurate (set by ntpd).
That's why I do assume that this log
```
Jul 17 10:58:58.000 [warn] Our clock is 1 minutes, 2 seconds behind the time published in the consensus network status document (2015-07-17 09:00:00 UTC). Tor needs an accurate clock to work correctly. Please check your time and date settings!
```
points to an issue which has nothing to do with a wrong local clock of my server (F1BE15429B3CE696D6807F4D4A58B1BFEC45C822)Nick MathewsonNick Mathewsonhttps://gitlab.torproject.org/tpo/core/tor/-/issues/20306"Tor cannot connect to the Internet if ReachableAddresses, ReachableORAddress...2020-06-27T13:58:05ZRoger Dingledine"Tor cannot connect to the Internet if ReachableAddresses, ReachableORAddresses, or ReachableDirAddresses reject all addresses. Please accept some addresses in these options." when "FascistFirewall 1" is setI start my Tor client running 0.2.9.3-alpha-dev (git-bfaded9143d127cb) with `FascistFirewall 1`, and it says:
```
Oct 06 15:32:11.620 [notice] Converting FascistFirewall config option to new format: "ReachableDirAddresses *:80"
Oct 06 15...I start my Tor client running 0.2.9.3-alpha-dev (git-bfaded9143d127cb) with `FascistFirewall 1`, and it says:
```
Oct 06 15:32:11.620 [notice] Converting FascistFirewall config option to new format: "ReachableDirAddresses *:80"
Oct 06 15:32:11.620 [notice] Converting FascistFirewall config option to new format: "ReachableORAddresses *:443"
```
which is reasonable, but later it says
```
Oct 06 15:32:11.623 [warn] Tor cannot connect to the Internet if ReachableAddresses, ReachableORAddresses, or ReachableDirAddresses reject all addresses. Please accept some addresses in these options.
```
which is surprising.Tor: 0.2.9.x-finalhttps://gitlab.torproject.org/tpo/core/tor/-/issues/12657"Tor has unexpectantly exited"2020-06-27T14:02:46Zcypherpunks"Tor has unexpectantly exited"Browser 3.6.2
OS-Win7-Ultimate/SP1
Win7 Firewall
no anti-virus
use bleachbit weekly
The Browser exits every couple of hours leaving a small window message stating "Tor has unexpectantly exited". Firewall on or off makes no difference. ...Browser 3.6.2
OS-Win7-Ultimate/SP1
Win7 Firewall
no anti-virus
use bleachbit weekly
The Browser exits every couple of hours leaving a small window message stating "Tor has unexpectantly exited". Firewall on or off makes no difference. Browser being actively used at the time or not, makes no difference.
LogFile:
7/14/2014 1:34:48 AM.380 [NOTICE] Opening Socks listener on 127.0.0.1:9150
7/14/2014 1:34:48 AM.380 [NOTICE] Pluggable transport proxy (fte exec Tor\PluggableTransports\fteproxy --managed) does not provide any needed transports and will not be launched.
7/14/2014 1:34:48 AM.380 [NOTICE] Pluggable transport proxy (obfs2,obfs3 exec Tor\PluggableTransports\obfsproxy managed) does not provide any needed transports and will not be launched.
7/14/2014 1:34:48 AM.380 [NOTICE] Pluggable transport proxy (flashproxy exec Tor\PluggableTransports\flashproxy-client --register :0 :9000) does not provide any needed transports and will not be launched.
7/14/2014 1:34:49 AM.390 [NOTICE] Bootstrapped 5%: Connecting to directory server.
7/14/2014 1:34:49 AM.390 [WARN] Problem bootstrapping. Stuck at 5%: Connecting to directory server. (Network is unreachable [WSAENETUNREACH ]; NOROUTE; count 1; recommendation warn)
7/14/2014 1:34:58 AM.386 [NOTICE] We now have enough directory information to build circuits.
7/14/2014 1:34:58 AM.386 [NOTICE] Bootstrapped 80%: Connecting to the Tor network.
7/14/2014 1:34:58 AM.387 [WARN] Problem bootstrapping. Stuck at 80%: Connecting to the Tor network. (Network is unreachable [WSAENETUNREACH ]; NOROUTE; count 2; recommendation warn)
7/14/2014 1:34:59 AM.411 [WARN] Problem bootstrapping. Stuck at 80%: Connecting to the Tor network. (Network is unreachable [WSAENETUNREACH ]; NOROUTE; count 3; recommendation warn)
7/14/2014 1:34:59 AM.411 [WARN] Problem bootstrapping. Stuck at 80%: Connecting to the Tor network. (Network is unreachable [WSAENETUNREACH ]; NOROUTE; count 4; recommendation warn)
7/14/2014 1:34:59 AM.412 [WARN] Problem bootstrapping. Stuck at 80%: Connecting to the Tor network. (Network is unreachable [WSAENETUNREACH ]; NOROUTE; count 5; recommendation warn)
7/14/2014 1:34:59 AM.412 [WARN] Problem bootstrapping. Stuck at 80%: Connecting to the Tor network. (Network is unreachable [WSAENETUNREACH ]; NOROUTE; count 6; recommendation warn)
7/14/2014 1:34:59 AM.413 [WARN] Problem bootstrapping. Stuck at 80%: Connecting to the Tor network. (Network is unreachable [WSAENETUNREACH ]; NOROUTE; count 7; recommendation warn)
7/14/2014 1:34:59 AM.413 [WARN] Problem bootstrapping. Stuck at 80%: Connecting to the Tor network. (Network is unreachable [WSAENETUNREACH ]; NOROUTE; count 8; recommendation warn)
7/14/2014 1:34:59 AM.414 [WARN] Problem bootstrapping. Stuck at 80%: Connecting to the Tor network. (Network is unreachable [WSAENETUNREACH ]; NOROUTE; count 9; recommendation warn)
7/14/2014 1:34:59 AM.415 [WARN] Problem bootstrapping. Stuck at 80%: Connecting to the Tor network. (Network is unreachable [WSAENETUNREACH ]; NOROUTE; count 10; recommendation warn)
7/14/2014 1:34:59 AM.415 [WARN] Problem bootstrapping. Stuck at 80%: Connecting to the Tor network. (Network is unreachable [WSAENETUNREACH ]; NOROUTE; count 11; recommendation warn)
7/14/2014 1:34:59 AM.416 [WARN] Problem bootstrapping. Stuck at 80%: Connecting to the Tor network. (Network is unreachable [WSAENETUNREACH ]; NOROUTE; count 12; recommendation warn)
7/14/2014 1:34:59 AM.416 [WARN] Problem bootstrapping. Stuck at 80%: Connecting to the Tor network. (Network is unreachable [WSAENETUNREACH ]; NOROUTE; count 13; recommendation warn)
7/14/2014 1:35:00 AM.320 [WARN] Problem bootstrapping. Stuck at 80%: Connecting to the Tor network. (Network is unreachable [WSAENETUNREACH ]; NOROUTE; count 14; recommendation warn)
7/14/2014 1:35:01 AM.320 [WARN] Problem bootstrapping. Stuck at 80%: Connecting to the Tor network. (Network is unreachable [WSAENETUNREACH ]; NOROUTE; count 15; recommendation warn)
7/14/2014 1:35:02 AM.300 [WARN] Problem bootstrapping. Stuck at 80%: Connecting to the Tor network. (Network is unreachable [WSAENETUNREACH ]; NOROUTE; count 16; recommendation warn)
7/14/2014 1:35:03 AM.310 [WARN] Problem bootstrapping. Stuck at 80%: Connecting to the Tor network. (Network is unreachable [WSAENETUNREACH ]; NOROUTE; count 17; recommendation warn)
7/14/2014 1:35:04 AM.380 [WARN] Problem bootstrapping. Stuck at 80%: Connecting to the Tor network. (Network is unreachable [WSAENETUNREACH ]; NOROUTE; count 18; recommendation warn)
7/14/2014 1:35:05 AM.260 [WARN] Problem bootstrapping. Stuck at 80%: Connecting to the Tor network. (Network is unreachable [WSAENETUNREACH ]; NOROUTE; count 19; recommendation warn)
7/14/2014 1:35:06 AM.300 [WARN] Problem bootstrapping. Stuck at 80%: Connecting to the Tor network. (Network is unreachable [WSAENETUNREACH ]; NOROUTE; count 20; recommendation warn)
7/14/2014 1:35:07 AM.310 [WARN] Problem bootstrapping. Stuck at 80%: Connecting to the Tor network. (Network is unreachable [WSAENETUNREACH ]; NOROUTE; count 21; recommendation warn)
7/14/2014 1:35:08 AM.310 [WARN] Problem bootstrapping. Stuck at 80%: Connecting to the Tor network. (Network is unreachable [WSAENETUNREACH ]; NOROUTE; count 22; recommendation warn)
7/14/2014 1:35:09 AM.310 [WARN] Problem bootstrapping. Stuck at 80%: Connecting to the Tor network. (Network is unreachable [WSAENETUNREACH ]; NOROUTE; count 23; recommendation warn)
7/14/2014 1:35:10 AM.310 [WARN] Problem bootstrapping. Stuck at 80%: Connecting to the Tor network. (Network is unreachable [WSAENETUNREACH ]; NOROUTE; count 24; recommendation warn)
7/14/2014 1:35:11 AM.320 [WARN] Problem bootstrapping. Stuck at 80%: Connecting to the Tor network. (Network is unreachable [WSAENETUNREACH ]; NOROUTE; count 25; recommendation warn)
7/14/2014 1:35:12 AM.300 [WARN] Problem bootstrapping. Stuck at 80%: Connecting to the Tor network. (Network is unreachable [WSAENETUNREACH ]; NOROUTE; count 26; recommendation warn)
7/14/2014 1:35:13 AM.310 [WARN] Problem bootstrapping. Stuck at 80%: Connecting to the Tor network. (Network is unreachable [WSAENETUNREACH ]; NOROUTE; count 27; recommendation warn)
7/14/2014 1:35:14 AM.350 [WARN] Problem bootstrapping. Stuck at 80%: Connecting to the Tor network. (Network is unreachable [WSAENETUNREACH ]; NOROUTE; count 28; recommendation warn)
7/14/2014 1:35:15 AM.340 [WARN] Problem bootstrapping. Stuck at 80%: Connecting to the Tor network. (Network is unreachable [WSAENETUNREACH ]; NOROUTE; count 29; recommendation warn)
7/14/2014 1:35:16 AM.320 [WARN] Problem bootstrapping. Stuck at 80%: Connecting to the Tor network. (Network is unreachable [WSAENETUNREACH ]; NOROUTE; count 30; recommendation warn)
7/14/2014 1:35:17 AM.320 [WARN] Problem bootstrapping. Stuck at 80%: Connecting to the Tor network. (Network is unreachable [WSAENETUNREACH ]; NOROUTE; count 31; recommendation warn)
7/14/2014 1:35:18 AM.320 [WARN] Problem bootstrapping. Stuck at 80%: Connecting to the Tor network. (Network is unreachable [WSAENETUNREACH ]; NOROUTE; count 32; recommendation warn)
7/14/2014 1:35:19 AM.300 [WARN] Problem bootstrapping. Stuck at 80%: Connecting to the Tor network. (Network is unreachable [WSAENETUNREACH ]; NOROUTE; count 33; recommendation warn)
7/14/2014 1:35:20 AM.300 [WARN] Problem bootstrapping. Stuck at 80%: Connecting to the Tor network. (Network is unreachable [WSAENETUNREACH ]; NOROUTE; count 34; recommendation warn)
7/14/2014 1:35:21 AM.300 [WARN] Problem bootstrapping. Stuck at 80%: Connecting to the Tor network. (Network is unreachable [WSAENETUNREACH ]; NOROUTE; count 35; recommendation warn)
7/14/2014 1:35:22 AM.310 [WARN] Problem bootstrapping. Stuck at 80%: Connecting to the Tor network. (Network is unreachable [WSAENETUNREACH ]; NOROUTE; count 36; recommendation warn)
7/14/2014 1:35:23 AM.360 [WARN] Problem bootstrapping. Stuck at 80%: Connecting to the Tor network. (Network is unreachable [WSAENETUNREACH ]; NOROUTE; count 37; recommendation warn)
7/14/2014 1:35:24 AM.300 [WARN] Problem bootstrapping. Stuck at 80%: Connecting to the Tor network. (Network is unreachable [WSAENETUNREACH ]; NOROUTE; count 38; recommendation warn)
7/14/2014 1:35:25 AM.310 [WARN] Problem bootstrapping. Stuck at 80%: Connecting to the Tor network. (Network is unreachable [WSAENETUNREACH ]; NOROUTE; count 39; recommendation warn)
7/14/2014 1:35:51 AM.180 [WARN] Problem bootstrapping. Stuck at 80%: Connecting to the Tor network. (Network is unreachable [WSAENETUNREACH ]; NOROUTE; count 40; recommendation warn)
7/14/2014 1:35:52 AM.300 [WARN] Problem bootstrapping. Stuck at 80%: Connecting to the Tor network. (Network is unreachable [WSAENETUNREACH ]; NOROUTE; count 41; recommendation warn)
7/14/2014 1:35:53 AM.310 [WARN] Problem bootstrapping. Stuck at 80%: Connecting to the Tor network. (Network is unreachable [WSAENETUNREACH ]; NOROUTE; count 42; recommendation warn)
7/14/2014 1:35:54 AM.300 [WARN] Problem bootstrapping. Stuck at 80%: Connecting to the Tor network. (Network is unreachable [WSAENETUNREACH ]; NOROUTE; count 43; recommendation warn)
7/14/2014 1:35:55 AM.290 [WARN] Problem bootstrapping. Stuck at 80%: Connecting to the Tor network. (Network is unreachable [WSAENETUNREACH ]; NOROUTE; count 44; recommendation warn)
7/14/2014 1:35:56 AM.290 [WARN] Problem bootstrapping. Stuck at 80%: Connecting to the Tor network. (Network is unreachable [WSAENETUNREACH ]; NOROUTE; count 45; recommendation warn)
7/14/2014 1:36:22 AM.230 [WARN] Problem bootstrapping. Stuck at 80%: Connecting to the Tor network. (Network is unreachable [WSAENETUNREACH ]; NOROUTE; count 46; recommendation warn)
7/14/2014 1:36:23 AM.300 [WARN] Problem bootstrapping. Stuck at 80%: Connecting to the Tor network. (Network is unreachable [WSAENETUNREACH ]; NOROUTE; count 47; recommendation warn)
7/14/2014 1:36:24 AM.290 [WARN] Problem bootstrapping. Stuck at 80%: Connecting to the Tor network. (Network is unreachable [WSAENETUNREACH ]; NOROUTE; count 48; recommendation warn)
7/14/2014 1:36:25 AM.300 [WARN] Problem bootstrapping. Stuck at 80%: Connecting to the Tor network. (Network is unreachable [WSAENETUNREACH ]; NOROUTE; count 49; recommendation warn)
7/14/2014 1:36:26 AM.280 [WARN] Problem bootstrapping. Stuck at 80%: Connecting to the Tor network. (Network is unreachable [WSAENETUNREACH ]; NOROUTE; count 50; recommendation warn)
7/14/2014 1:36:27 AM.280 [WARN] Problem bootstrapping. Stuck at 80%: Connecting to the Tor network. (Network is unreachable [WSAENETUNREACH ]; NOROUTE; count 51; recommendation warn)
7/14/2014 1:36:53 AM.388 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop.
7/14/2014 1:36:56 AM.619 [NOTICE] Bootstrapped 90%: Establishing a Tor circuit.
7/14/2014 1:37:17 AM.935 [WARN] Problem bootstrapping. Stuck at 90%: Establishing a Tor circuit. (CONNECTRESET; CONNECTRESET; count 52; recommendation warn)
7/14/2014 1:37:17 AM.935 [WARN] 1 connections have failed:
7/14/2014 1:37:17 AM.936 [WARN] 1 connections died in state handshaking (Tor, v3 handshake) with SSL state SSL negotiation finished successfully in OPEN
7/14/2014 1:37:26 AM.347 [WARN] Problem bootstrapping. Stuck at 90%: Establishing a Tor circuit. (DONE; DONE; count 53; recommendation warn)
7/14/2014 1:37:26 AM.347 [WARN] 2 connections have failed:
7/14/2014 1:37:26 AM.347 [WARN] 1 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE
7/14/2014 1:37:26 AM.347 [WARN] 1 connections died in state handshaking (Tor, v3 handshake) with SSL state SSL negotiation finished successfully in OPEN
7/14/2014 1:37:42 AM.886 [NOTICE] Pluggable transport proxy (fte exec Tor\PluggableTransports\fteproxy --managed) does not provide any needed transports and will not be launched.
7/14/2014 1:37:42 AM.886 [NOTICE] Pluggable transport proxy (obfs2,obfs3 exec Tor\PluggableTransports\obfsproxy managed) does not provide any needed transports and will not be launched.
7/14/2014 1:37:42 AM.886 [NOTICE] Pluggable transport proxy (flashproxy exec Tor\PluggableTransports\flashproxy-client --register :0 :9000) does not provide any needed transports and will not be launched.
7/14/2014 1:37:42 AM.935 [NOTICE] Tor has successfully opened a circuit. Looks like client functionality is working.
7/14/2014 1:37:42 AM.935 [NOTICE] Bootstrapped 100%: Done.
7/14/2014 1:37:54 AM.290 [WARN] onion_skin_client_handshake failed.
7/14/2014 1:37:54 AM.290 [WARN] circuit_finish_handshake failed.
7/14/2014 1:37:54 AM.290 [WARN] connection_edge_process_relay_cell (at origin) failed.Tor: 0.2.6.x-finalhttps://gitlab.torproject.org/tpo/core/tor/-/issues/24149"Tor is running with Rust integration. Please report any bugs you encouter."2020-06-27T13:55:04ZAlex Xu"Tor is running with Rust integration. Please report any bugs you encouter."I have encoutered a bug.
encounter is misspelled.I have encoutered a bug.
encounter is misspelled.https://gitlab.torproject.org/tpo/core/tor/-/issues/12065"tor unexpectedly exited" after I edit the torcc file.2020-06-27T14:02:58Zcypherpunks"tor unexpectedly exited" after I edit the torcc file.All I did was add two lines to Data\Tor\torrc:
```
ExitNodes {us}
StrictExitNodes1
```
After I save the file and restart tor, I get the "tor unexpectedly exited" error. If I remove the two lines and save, the error goes away.All I did was add two lines to Data\Tor\torrc:
```
ExitNodes {us}
StrictExitNodes1
```
After I save the file and restart tor, I get the "tor unexpectedly exited" error. If I remove the two lines and save, the error goes away.https://gitlab.torproject.org/tpo/core/tor/-/issues/40189"tor-gencert --create-identity-key" fails with no clear error message if pass...2022-07-07T00:48:31ZRoger Dingledine"tor-gencert --create-identity-key" fails with no clear error message if passphrase is empty or shortRun tor-gencert to make a new key, but leave the PEM pass phrase empty (just hit enter):
```
$ ./tor-gencert --create-identity-key
Enter PEM pass phrase:
Nov 15 15:32:59.730 [err] Couldn't write identity key to ./authority_identity_key
N...Run tor-gencert to make a new key, but leave the PEM pass phrase empty (just hit enter):
```
$ ./tor-gencert --create-identity-key
Enter PEM pass phrase:
Nov 15 15:32:59.730 [err] Couldn't write identity key to ./authority_identity_key
Nov 15 15:32:59.730 [err] crypto error while Writing identity key: result too small (in UI routines:UI_set_result_ex)
Nov 15 15:32:59.730 [err] crypto error while Writing identity key: processing error (in UI routines:UI_process)
Nov 15 15:32:59.730 [err] crypto error while Writing identity key: problems getting password (in PEM routines:PEM_def_callback)
Nov 15 15:32:59.730 [err] crypto error while Writing identity key: read key (in PEM routines:do_pk8pkey)
```
It seems to me that having an empty pass phrase should work; but if we want it to not work, we should say that as an error message.
(Found by tech-exorcist on #tor)
In fact, I just tried it with short passphrases, and they also fail with these cryptic error messages. So it sounds like maybe we have a secret minimum passphrase length or something?Tor: 0.4.6.x-freezeNeel Chauhanneel@neelc.orgNeel Chauhanneel@neelc.orghttps://gitlab.torproject.org/tpo/core/tor/-/issues/295"Tor.exe -remove" appears to not be waiting for service to stop.2020-06-27T14:10:55ZTrac"Tor.exe -remove" appears to not be waiting for service to stop.C:\Program Files\Tor>tor -remove
Service failed to stop :
Service could not be removed
C:\Program Files\Tor>tor -remove
Service is already stopped
Removed service successfully
[Automatically added by flyspray2trac: Operating System: Wi...C:\Program Files\Tor>tor -remove
Service failed to stop :
Service could not be removed
C:\Program Files\Tor>tor -remove
Service is already stopped
Removed service successfully
[Automatically added by flyspray2trac: Operating System: Windows 2k/XP]
**Trac**:
**Username**: HexMaster