Your IP is NOT identified to be a Tor-EXIT.
So you are NOT using Tor to reach the web!
Oct 18 17:04:26 TuT kern.warn kernel: system-load 7 curr: tor runnable: 2
Oct 18 17:04:26 TuT kern.warn kernel: system-load 100 % curr: tor runnable: 1
Oct 18 17:04:31 TuT daemon.notice Tor[27327]: No AES engine found; using AES_* functions.
Oct 18 17:04:31 TuT daemon.notice Tor[27327]: This version of OpenSSL has a slow implementation of counter mode; not using it.
Oct 18 17:04:32 TuT kern.warn kernel: system-load 4 curr: tor runnable: 3
Oct 18 17:04:32 TuT daemon.notice Tor[27327]: OpenSSL OpenSSL 0.9.8y 5 Feb 2013 looks like version 0.9.8m or later; I will try SSL_OP to enable renegotiation
Oct 18 17:04:39 TuT daemon.notice Tor[27327]: Reloaded microdescriptor cache. Found 4523 descriptors.
Oct 18 17:04:42 TuT daemon.notice Tor[27327]: We now have enough directory information to build circuits.
Oct 18 17:04:42 TuT daemon.notice Tor[27327]: Bootstrapped 80%: Connecting to the Tor network.
Oct 18 17:04:43 TuT daemon.notice Tor[27327]: Heartbeat: Tor's uptime is 0:00 hours, with 4 circuits open. I've sent 0 kB and received 0 kB.
Oct 18 17:04:43 TuT daemon.notice Tor[27327]: Bootstrapped 85%: Finishing handshake with first hop.
Oct 18 17:04:43 TuT daemon.notice Tor[27327]: We weren't able to find support for all of the TLS ciphersuites that we wanted to advertise. This won't hurt security, but it might make your Tor (if run as a client) more easy for censors to block.
Oct 18 17:04:43 TuT daemon.notice Tor[27327]: To correct this, use a more recent OpenSSL, built without disabling any secure ciphers or features.
Oct 18 17:04:44 TuT daemon.notice Tor[27327]: Bootstrapped 90%: Establishing a Tor circuit.
Oct 18 17:04:45 TuT daemon.notice Tor[27327]: Tor has successfully opened a circuit. Looks like client functionality is working.
Oct 18 17:04:45 TuT daemon.notice Tor[27327]: Bootstrapped 100%: Done.
Your IP is identified to be a Tor-EXIT.
So you are using Tor successfully to reach the web!
Cookies Third Party sites get your cookies and my track you
Authentication:your unique id:251112411
User-Agent: Shows me my Browser
YOUR IP: Shows me my correct IP
Flash Cookies
his is Privoxy 3.0.21 on fritz.box (192.168.188.1), port 9051, enabled
Forwarding failure
Privoxy was unable to socks4a-forward your request http://ipcheck.info/index.php?jsID=12140797&auth=753636751&138241464811755=138241464811755n&referer=subdomainReplaceDomain through 127.0.0.1: SOCKS request rejected or failed.
Just try again to see if this is a temporary problem, or check your forwarding settings and make sure that all forwarding servers are working correctly and listening where they are supposed to be listening.
"Coolzero"
I see her http://torcheck.xenobite.eu/index.php?
Your IP is identified to be a Tor-EXIT.
So you are using Tor successfully to reach the web!
So i thing Tor is correctly running! Is this right?
Now i have some other Problems, this site:
http://ip-check.info/index.php?jsID=121 ... =unchanged
shows me my right ip, i don't understand why!