-
Notifications
You must be signed in to change notification settings - Fork 7
/
watch-tor.txt
91 lines (91 loc) · 4.43 KB
/
watch-tor.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
#################### harmless
Bootstrapped 0%: Starting
Bootstrapped 0% (starting): Starting
Bootstrapped 100% (done): Done
Bootstrapped 10% (conn_done): Connected to a relay
Bootstrapped 14% (handshake): Handshaking with a relay
Bootstrapped 15% (handshake_done): Handshake with a relay done
Bootstrapped 20% (onehop_create): Establishing an encrypted directory connection
Bootstrapped 5% (conn): Connecting to a relay
Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits
Bootstrapped 85% (ap_conn_done): Connected to a relay to build circuits
Bootstrapped 89% (ap_handshake): Finishing handshake with a relay to build circuits
Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits
Bootstrapped 95% (circuit_create): Establishing a Tor circuit
Channel padding timeout scheduled
Circuit handshake stats since last time:
Clean shutdown finished. Exiting.
Configured to measure statistics. Look for the *-stats files that will first be written to the data directory in 24 hours from now.
DoS mitigation since startup:
Heartbeat:
I learned some more directory information, but not enough to build a circuit
Included configuration file or directory at recursion level
Including configuration file "/etc/tor/conf.d//
is newer than any recommended version, according to the directory authorities.
is reachable from the outside. Excellent.
New control connection opened from
No circuits are opened. Relaxed timeout for circuit
Now checking whether IPv4 DirPort
Now checking whether IPv4 ORPort
Opened Control listener connection
Opening Control listener on
opening log file
Opening Metrics listener on
Opening Socks listener on
Our directory information is no longer up-to-date enough to build circuits: We're missing descriptors for
Parsing GEOIP IPv4 file /usr/share/tor/geoip.
Parsing GEOIP IPv6 file /usr/share/tor/geoip6.
Performing bandwidth self-test...done.
Possible compression bomb; abandoning stream.
Processing configuration path "/etc/tor/conf.d/" at recursion level 1
Read configuration file
Received circuit padding stop command for unknown machine.
Received directory with skewed time
Received http status code 404
Received reload signal (hup). Reloading config and resetting internal state.
Since last heartbeat message
Since our last heartbeat,
Since startup we initiated
Starting with guard context "default"
The current consensus contains exit nodes
The current consensus has no exit nodes
These two versions should be binary compatible.
Tried to establish rendezvous on non-edge circuit
We now have enough directory information to build circuits
We were built to run on a 64-bit CPU, with OpenSSL 1.0.1 or later, but with a version of OpenSSL that apparently lacks accelerated support for the NIST P-224 and P-256 groups. Building openssl with such support (using the enable-ec_nistp_64_gcc_128 option when configuring it) would make ECDH much faster.
While bootstrapping, fetched this many bytes:
While not bootstrapping, fetched this many bytes:
You have asked to exclude certain relays from all positions in your circuits
Your Tor server's identity key
#################### ignoreable notices and warnings
connection_edge_process_relay_cell (at origin) failed.
Detected possible compression bomb with input size
Sudden decrease in circuit RTT
Unable to decompress HTTP body
Unable to send INTRODUCE2 cell to the service.
Your network connection speed appears to have changed.
#################### known bugs
Bug: /
Couldn't send authenticate cell
Duplicate call to circuit_mark_for_close
Error relaying cell across rendezvous; closing circuits
Missing master key after handshake using TLSv1.3
Non-fatal assertion !(! master_key_len)
tor_bug_occurred_(): Bug: src/lib/tls/tortls_openssl.c
#################### protocol warnings
Attempt by \[scrubbed\] to open a stream
Client asked me to extend
conn to next hop already launched. Bug/attack. Closing.
connection_edge_process_relay_cell (away from origin) failed.
DH key must be at least 2.
Expiring stuck OR connection to
Inbound circuit has 1250 cells in its queue, maximum allowed is 1250
Outbound circuit has 1000 cells in its queue
Received a bad CERTS cell
Received too many RELAY_EARLY cells on circ
Single hop client was rejected while trying to introduce
Somebody asked us for an older TLS authentication method
Tried connecting to router at
Unable to compute authenticate cell!
We received a SENDME but we have no cell digests to match. Closing circuit.
Your log may contain sensitive information