Jul 05 18:25:18.000 [notice] Tor 0.3.0.9 (git-22b3bf094e327093) opening log file.
Jul 05 18:25:18.671 [notice] Tor 0.3.0.9 (git-22b3bf094e327093) running on Windows 8 with Libevent 2.0.22-stable, OpenSSL 1.0.2k and Zlib 1.2.8.
Jul 05 18:25:18.671 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning
Jul 05 18:25:18.671 [notice] Read configuration file "C:\TorBrowser\Browser\TorBrowser\Data\Tor\torrc-defaults".
Jul 05 18:25:18.671 [notice] Read configuration file "C:\TorBrowser\Browser\TorBrowser\Data\Tor\torrc".
Jul 05 18:25:18.687 [warn] The CacheDNS option is deprecated, and will most likely be removed in a future version of Tor. Client-side DNS cacheing enables a wide variety of route-capture attacks. If a single bad exit node lies to you about an IP address, cacheing that address would make you visit an address of the attacker's choice every time you connected to your destination. (If you think this is a mistake, please let us know!)
Jul 05 18:25:18.687 [warn] The UseDNSCache option is deprecated, and will most likely be removed in a future version of Tor. Client-side DNS cacheing enables a wide variety of route-capture attacks. If a single bad exit node lies to you about an IP address, cacheing that address would make you visit an address of the attacker's choice every time you connected to your destination. (If you think this is a mistake, please let us know!)
Jul 05 18:25:18.687 [warn] The CacheDNS option is deprecated, and will most likely be removed in a future version of Tor. Client-side DNS cacheing enables a wide variety of route-capture attacks. If a single bad exit node lies to you about an IP address, cacheing that address would make you visit an address of the attacker's choice every time you connected to your destination. (If you think this is a mistake, please let us know!)
Jul 05 18:25:18.687 [warn] The UseDNSCache option is deprecated, and will most likely be removed in a future version of Tor. Client-side DNS cacheing enables a wide variety of route-capture attacks. If a single bad exit node lies to you about an IP address, cacheing that address would make you visit an address of the attacker's choice every time you connected to your destination. (If you think this is a mistake, please let us know!)
Jul 05 18:25:18.687 [notice] Opening Socks listener on 127.0.0.1:9051
Jul 05 18:25:18.687 [notice] Opening Socks listener on 127.0.0.1:9150
Jul 05 18:25:18.687 [notice] Opening Control listener on 127.0.0.1:9151
Jul 05 18:25:18.000 [notice] Parsing GEOIP IPv4 file C:\TorBrowser\Browser\TorBrowser\Data\Tor\geoip.
Jul 05 18:25:19.000 [notice] Parsing GEOIP IPv6 file C:\TorBrowser\Browser\TorBrowser\Data\Tor\geoip6.
Jul 05 18:25:19.000 [notice] Bootstrapped 0%: Starting
Jul 05 18:25:20.000 [notice] Starting with guard context "bridges"
Jul 05 18:25:20.000 [notice] new bridge descriptor 'Unnamed' (cached): <<some bridge info>>
Jul 05 18:25:20.000 [notice] new bridge descriptor 'soddennessesdeco' (cached): <<some bridge info>>
Jul 05 18:25:20.000 [notice] Bridge 'Unnamed' has both an IPv4 and an IPv6 address.  Will prefer using its IPv4 address (<<some bridge info>>) based on the configured Bridge address.
Jul 05 18:25:20.000 [notice] new bridge descriptor 'Unnamed' (cached): <<some bridge info>>
Jul 05 18:25:20.000 [notice] new bridge descriptor 'Unnamed' (cached): <<some bridge info>>
Jul 05 18:25:20.000 [notice] new bridge descriptor 'Unnamed' (cached): <<some bridge info>>
Jul 05 18:25:20.000 [notice] new bridge descriptor 'soddennessesdeco' (cached): <<some bridge info>>
Jul 05 18:25:20.000 [notice] new bridge descriptor 'soddennessesdeco' (cached): <<some bridge info>>
Jul 05 18:25:20.000 [notice] new bridge descriptor 'soddennessesdeco' (cached): <<some bridge info>>
Jul 05 18:25:20.000 [notice] Bridge 'Unnamed' has both an IPv4 and an IPv6 address.  Will prefer using its IPv4 address (<<some bridge info>>) based on the configured Bridge address.
Jul 05 18:25:20.000 [notice] new bridge descriptor 'Unnamed' (cached): <<some bridge info>>
Jul 05 18:25:20.000 [notice] Bridge 'Unnamed' has both an IPv4 and an IPv6 address.  Will prefer using its IPv4 address (<<some bridge info>>) based on the configured Bridge address.
Jul 05 18:25:20.000 [notice] new bridge descriptor 'Unnamed' (cached): <<some bridge info>>
Jul 05 18:25:20.000 [notice] Bootstrapped 80%: Connecting to the Tor network
Jul 05 18:25:20.000 [notice] New control connection opened from 127.0.0.1.
Jul 05 18:25:27.000 [warn] The CacheDNS option is deprecated, and will most likely be removed in a future version of Tor. Client-side DNS cacheing enables a wide variety of route-capture attacks. If a single bad exit node lies to you about an IP address, cacheing that address would make you visit an address of the attacker's choice every time you connected to your destination. (If you think this is a mistake, please let us know!)
Jul 05 18:25:27.000 [warn] The UseDNSCache option is deprecated, and will most likely be removed in a future version of Tor. Client-side DNS cacheing enables a wide variety of route-capture attacks. If a single bad exit node lies to you about an IP address, cacheing that address would make you visit an address of the attacker's choice every time you connected to your destination. (If you think this is a mistake, please let us know!)
Jul 05 18:25:27.000 [warn] The CacheDNS option is deprecated, and will most likely be removed in a future version of Tor. Client-side DNS cacheing enables a wide variety of route-capture attacks. If a single bad exit node lies to you about an IP address, cacheing that address would make you visit an address of the attacker's choice every time you connected to your destination. (If you think this is a mistake, please let us know!)
Jul 05 18:25:27.000 [warn] The UseDNSCache option is deprecated, and will most likely be removed in a future version of Tor. Client-side DNS cacheing enables a wide variety of route-capture attacks. If a single bad exit node lies to you about an IP address, cacheing that address would make you visit an address of the attacker's choice every time you connected to your destination. (If you think this is a mistake, please let us know!)
Jul 05 18:25:27.000 [notice] Tor 0.3.0.9 (git-22b3bf094e327093) opening log file.
Jul 05 18:25:27.000 [notice] New control connection opened from 127.0.0.1.
Jul 05 18:25:27.000 [notice] Bootstrapped 85%: Finishing handshake with first hop
Jul 05 18:25:28.000 [notice] Bootstrapped 90%: Establishing a Tor circuit
Jul 05 18:25:28.000 [notice] new bridge descriptor 'soddennessesdeco' (fresh): <<some bridge info>>
Jul 05 18:25:29.000 [notice] Tor has successfully opened a circuit. Looks like client functionality is working.
Jul 05 18:25:29.000 [notice] Bootstrapped 100%: Done
Jul 05 18:25:29.000 [notice] new bridge descriptor 'Unnamed' (fresh): <<some bridge info>>
Jul 05 18:25:30.000 [notice] New control connection opened from 127.0.0.1.
Jul 05 18:25:30.000 [notice] New control connection opened from 127.0.0.1.
Jul 05 18:27:33.000 [warn] Rejecting SOCKS request for anonymous connection to private address [scrubbed].
Jul 05 18:27:33.000 [warn] socks5: command 3 not recognized. Rejecting.
Jul 05 18:27:33.000 [warn] socks5: command 3 not recognized. Rejecting.
Jul 05 18:27:35.000 [warn] Missing mapping for virtual address '[scrubbed]'. Refusing.
Jul 05 18:27:36.000 [warn] socks5: command 3 not recognized. Rejecting.
Jul 05 18:27:38.000 [warn] Missing mapping for virtual address '[scrubbed]'. Refusing.
Jul 05 18:27:39.000 [warn] socks5: command 3 not recognized. Rejecting.
Jul 05 18:27:42.000 [warn] socks5: command 3 not recognized. Rejecting.
Jul 05 18:27:42.000 [warn] Missing mapping for virtual address '[scrubbed]'. Refusing.
Jul 05 18:27:45.000 [warn] socks5: command 3 not recognized. Rejecting.
Jul 05 18:27:45.000 [warn] Missing mapping for virtual address '[scrubbed]'. Refusing.
Jul 05 18:27:48.000 [warn] socks5: command 3 not recognized. Rejecting.
Jul 05 18:27:51.000 [notice] Have tried resolving or connecting to address '[scrubbed]' at 3 different places. Giving up.
Jul 05 18:27:51.000 [warn] socks5: command 3 not recognized. Rejecting.
Jul 05 18:27:54.000 [warn] socks5: command 3 not recognized. Rejecting.
Jul 05 18:27:57.000 [warn] socks5: command 3 not recognized. Rejecting.
Jul 05 18:27:57.000 [warn] Missing mapping for virtual address '[scrubbed]'. Refusing.
Jul 05 18:27:57.000 [notice] Have tried resolving or connecting to address '[scrubbed]' at 3 different places. Giving up.
Jul 05 18:28:00.000 [warn] socks5: command 3 not recognized. Rejecting.
Jul 05 18:28:01.000 [warn] Missing mapping for virtual address '[scrubbed]'. Refusing.
Jul 05 18:28:03.000 [warn] socks5: command 3 not recognized. Rejecting.
Jul 05 18:28:06.000 [warn] socks5: command 3 not recognized. Rejecting.
Jul 05 18:28:09.000 [warn] socks5: command 3 not recognized. Rejecting.
Jul 05 18:28:10.000 [notice] Have tried resolving or connecting to address '[scrubbed]' at 3 different places. Giving up.
Jul 05 18:28:10.000 [notice] Have tried resolving or connecting to address '[scrubbed]' at 3 different places. Giving up.
Jul 05 18:28:12.000 [warn] socks5: command 3 not recognized. Rejecting.
Jul 05 18:28:15.000 [warn] socks5: command 3 not recognized. Rejecting.
Jul 05 18:28:31.000 [notice] Owning controller connection has closed -- exiting now.
Jul 05 18:28:31.000 [notice] Catching signal TERM, exiting cleanly.