Guest User

Untitled

a guest
Jun 22nd, 2018
93
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 2.55 KB | None | 0 0
  1. Feb 11 21:23:22.000 [notice] Tor 0.2.3.11-alpha-dev (git-64523609c91d9207) opening log file.
  2. Feb 11 21:23:22.000 [notice] Parsing GEOIP file /usr/local/share/tor/geoip.
  3. Feb 11 21:23:22.000 [notice] Configured to measure statistics. Look for the *-stats files that will first be written to the data directory in 24 hours from now.
  4. Feb 11 21:23:22.000 [warn] You are running Tor as root. You don't need to, and you probably shouldn't.
  5. Feb 11 21:23:22.000 [notice] No AES engine found; using AES_* functions.
  6. Feb 11 21:23:22.000 [notice] This version of OpenSSL has a slow implementation of counter mode; not using it.
  7. Feb 11 21:23:22.000 [notice] OpenSSL OpenSSL 0.9.8o 01 Jun 2010 looks like version 0.9.8m or later; I will try SSL_OP to enable renegotiation
  8. Feb 11 21:23:23.000 [notice] Your Tor server's identity key fingerprint is 'Hermes42 E51B36C7CAF3A8F7C42BEA54E53463CD02439EEE'
  9. Feb 11 21:23:23.000 [notice] This version of Tor (0.2.3.11-alpha-dev) is newer than any recommended version, according to the directory authorities. Recommended versions are: 0.2.1.32,0.2.2.35,0.2.3.10-alpha,0.2.3.11-alpha
  10. Feb 11 21:23:23.000 [notice] Reloaded microdescriptor cache. Found 2915 descriptors.
  11. Feb 11 21:23:23.000 [notice] We now have enough directory information to build circuits.
  12. Feb 11 21:23:23.000 [notice] Bootstrapped 80%: Connecting to the Tor network.
  13. Feb 11 21:23:24.000 [notice] Heartbeat: It seems like we are not in the cached consensus.
  14. Feb 11 21:23:24.000 [notice] Heartbeat: Tor's uptime is 0:00 hours, with 1 circuits open. I've sent 54 kB and received 25 kB.
  15. Feb 11 21:23:24.000 [notice] Bootstrapped 85%: Finishing handshake with first hop.
  16. Feb 11 21:23:24.000 [notice] Bootstrapped 90%: Establishing a Tor circuit.
  17. Feb 11 21:23:25.000 [notice] Tor has successfully opened a circuit. Looks like client functionality is working.
  18. Feb 11 21:23:25.000 [notice] Bootstrapped 100%: Done.
  19. Feb 11 21:23:25.000 [notice] Now checking whether ORPort 82.149.225.171:443 and DirPort 82.149.225.171:80 are reachable... (this may take up to 20 minutes -- look for log messages indicating success)
  20. Feb 11 21:23:25.000 [notice] Managed proxy stream closed. Most probably application stopped running
  21. Feb 11 21:23:25.000 [notice] Failed to terminate process with PID '29840'
  22. Feb 11 21:23:26.000 [notice] Self-testing indicates your DirPort is reachable from the outside. Excellent.
  23. Feb 11 21:23:28.000 [notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor.
  24. Feb 11 21:23:34.000 [notice] Performing bandwidth self-test...done.
Add Comment
Please, Sign In to add comment