Guest User

Untitled

a guest
Jan 1st, 2014
820
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
  1. Orbot is starting…
  2. Orbot is starting…
  3. link command output:
  4. Orbot is starting…
  5. got tor proc id: 27262
  6. Tor process id=27262
  7. Connecting to control port: 9051
  8. SUCCESS connected to control port
  9. SUCCESS authenticated to control port
  10. Starting Tor client… complete.
  11. adding control port event handler
  12. SUCCESS added control port event handler
  13. updating settings in Tor service
  14. WARN: You specified a public address '0.0.0.0:9050' for SocksPort. Other people on the Internet might find your computer and use it as an open proxy. Please don't allow this unless you have a good reason.
  15. WARN: You specified a public address '0.0.0.0:5400' for DNSPort. Other people on the Internet might find your computer and use it as an open proxy. Please don't allow this unless you have a good reason.
  16. WARN: You specified a public address '0.0.0.0:9040' for TransPort. Other people on the Internet might find your computer and use it as an open proxy. Please don't allow this unless you have a good reason.
  17. WARN: You have a ControlPort set to accept connections from a non-local address. This means that programs not running on your computer can reconfigure your Tor. That's pretty bad, since the controller protocol isn't encrypted! Maybe you should just listen on 127.0.0.1 and use a tool like stunnel or ssh to encrypt remote connections to your control port.
  18. WARN: You specified a public address '0.0.0.0:9050' for SocksPort. Other people on the Internet might find your computer and use it as an open proxy. Please don't allow this unless you have a good reason.
  19. WARN: You specified a public address '0.0.0.0:5400' for DNSPort. Other people on the Internet might find your computer and use it as an open proxy. Please don't allow this unless you have a good reason.
  20. WARN: You specified a public address '0.0.0.0:9040' for TransPort. Other people on the Internet might find your computer and use it as an open proxy. Please don't allow this unless you have a good reason.
  21. WARN: You have a ControlPort set to accept connections from a non-local address. This means that programs not running on your computer can reconfigure your Tor. That's pretty bad, since the controller protocol isn't encrypted! Maybe you should just listen on 127.0.0.1 and use a tool like stunnel or ssh to encrypt remote connections to your control port.
  22. WARN: Option 'StrictNodes' used more than once; all but the last value will be ignored.
  23. WARN: Option 'UseBridges' used more than once; all but the last value will be ignored.
  24. WARN: You specified a public address '0.0.0.0:9050' for SocksPort. Other people on the Internet might find your computer and use it as an open proxy. Please don't allow this unless you have a good reason.
  25. WARN: You specified a public address '0.0.0.0:5400' for DNSPort. Other people on the Internet might find your computer and use it as an open proxy. Please don't allow this unless you have a good reason.
  26. WARN: You specified a public address '0.0.0.0:9040' for TransPort. Other people on the Internet might find your computer and use it as an open proxy. Please don't allow this unless you have a good reason.
  27. WARN: You have a ControlPort set to accept connections from a non-local address. This means that programs not running on your computer can reconfigure your Tor. That's pretty bad, since the controller protocol isn't encrypted! Maybe you should just listen on 127.0.0.1 and use a tool like stunnel or ssh to encrypt remote connections to your control port.
  28. WARN: You specified a public address '0.0.0.0:9050' for SocksPort. Other people on the Internet might find your computer and use it as an open proxy. Please don't allow this unless you have a good reason.
  29. WARN: You specified a public address '0.0.0.0:5400' for DNSPort. Other people on the Internet might find your computer and use it as an open proxy. Please don't allow this unless you have a good reason.
  30. WARN: You specified a public address '0.0.0.0:9040' for TransPort. Other people on the Internet might find your computer and use it as an open proxy. Please don't allow this unless you have a good reason.
  31. WARN: You have a ControlPort set to accept connections from a non-local address. This means that programs not running on your computer can reconfigure your Tor. That's pretty bad, since the controller protocol isn't encrypted! Maybe you should just listen on 127.0.0.1 and use a tool like stunnel or ssh to encrypt remote connections to your control port.
  32. Starting privoxy process
  33. /data/app-lib/org.torproject.android-1/libprivoxy.so /data/data/org.torproject.android/app_bin/privoxy.config &
  34.  
  35. orConnStatus (absVpsTorRelayLUX): LAUNCHED
  36. orConnStatus (afo2): LAUNCHED
  37. NOTICE: Bootstrapped 85%: Finishing handshake with first hop.
  38. orConnStatus (absVpsTorRelayLUX): CONNECTED
  39. NOTICE: Bootstrapped 90%: Establishing a Tor circuit.
  40. orConnStatus (afo2): CONNECTED
  41. Circuit (1) BUILT: absVpsTorRelayLUX
  42. Privoxy is running on port:8118
  43. Privoxy process id=27277
  44.  
  45. Circuit (2) BUILT: afo2 > askatasuna65 > MichaelsTorExit
  46. NOTICE: Tor has successfully opened a circuit. Looks like client functionality is working.
  47. NOTICE: Bootstrapped 100%: Done.
  48. orConnStatus (Unnamed): LAUNCHED
  49. NOTICE: Our directory information is no longer up-to-date enough to build circuits: We need more microdescriptors: we have 3752/4713, and can only build 50% of likely paths. (We have 81% of guards bw, 78% of midpoint bw, and 79% of exit bw.)
  50. NOTICE: I learned some more directory information, but not enough to build a circuit: We need more microdescriptors: we have 3752/4713, and can only build 50% of likely paths. (We have 81% of guards bw, 78% of midpoint bw, and 79% of exit bw.)
  51. Circuit (3) BUILT: afo2 > Unnamed > AccessNow
  52. NOTICE: Tor has successfully opened a circuit. Looks like client functionality is working.
  53. Circuit (5) BUILT: afo2
  54. NOTICE: We now have enough directory information to build circuits.
  55. Circuit (6) BUILT: afo2 > BostonUCompSci > manning1
  56. orConnStatus (Unnamed): CONNECTED
  57. Circuit (4) BUILT: Unnamed
  58. Circuit (7) BUILT: afo2 > RainbowGate > ndnr1
  59. Circuit (8) BUILT: afo2 > torpidsUKuk2 > remoc
RAW Paste Data