Normally the Tor service should be started/stopped with either sudo systemctl start/stop tor.service or sudo service tor start/stop.
Personally I've always used the service command because it is simpler. I'm guessing things get a little more complicated when you run multiple Tor instances, but I have no experience with that.
Running Tor in a terminal runs ...
torsocks intercepts calls to the libc syscall() function (and various other libc calls) by hooking into them through the dynamic linkers LD_PRELOAD environment variable.
It creates a "shim" function around the calls that it knows it can properly torify, and runs a torified version of the function. Those that it cannot properly torify or does not know can be ...
It seems that you're hitting the Tor built-in protection against requests to private LAN addresses through SOCKS proxy backend. Try using redsocks or something like it, but revise your config first : you're defenately routing LAN through Tor. Post your configs and scripts here, so I'll be able to help you further.
No, the Tor Browser will launch it's own tor process by default and both will connect to the Tor network separately.
So unless you've knowingly configured your system daemon instance of tor to act as a transparent proxy and set some iptables rules to enforce it, you will not be creating a "Tor-over-Tor" situation (I.E. you won't be connecting through "6 ...
The control port is used for controlling Tor, usually via other software like Arm.
The Socks port is the port running as a SOCKS5 proxy. This is the one you want to use. Please note that Tor is not an HTTP proxy, so your script will need to be configured to use a SOCKS5 proxy.
You should prefer torsocks over proxychains, since torsocks is intended to block potential leaks.
Especially in cases with tools like youtube-dl which might try to pass over execution to programs that can make network connections of their own in unexpected or attacker controlled ways.
Specifically with proxychains, if anything wrapped in proxychains tries ...
You should definitely use torsocks curl here, because curl --socks5 does NOT use the given SOCKS proxy to resolve DNS name. See torsocks documentation for more specifics. Also, you can use usewithtor [application] instead of torsocks [application].
TBB is a Firefox ESR with some configuration changes that make it more 'anonymous'
this is from the web:
"...Also, note that the Firefox ESR in our bundles is modified from the default Firefox ESR "
It also could be an add-on, usually Tor´s browser has enable "noScript", disable it and try again.
I found some clues reading this question: https://apple.stackexchange.com/questions/212586/torsocks-not-working-in-el-capitan
Suppose I installed httpie with brew
$ brew install httpie
The following command line won't have expected result:
$ torsocks http https://check.torproject.org/api/ip
HTTP/1.1 200 OK
Tor not just a not http proxy - it's a transparent proxy with host-mapping features and DNS + SOCKS backend. If you want it as a VPN, especially on Windows 10, you MUST use a separate box as a router, where you'll actually route all the traffic through Tor. I've made some research in Windows 10 case, and here's a conclusion :
If you're using laptop, ...
This is unrelated to the onion service, there is a problem with your client configuration. It is not properly using SOCKS5/SOCKS4a's remote hostname functionality.
The problem is that you're resolving the ".onion" address, then connecting to the resolved IP over SOCKS5 (a classic "DNS leak"). Normally this should result in some kind of NXDOMAIN resolve ...
You could try and use jtorctl which is a
A Java library for controlling a Tor instance via its control port. It
is used in the Android app Orbot as well as others.
Orchid is a Tor client implementation and library written in pure Java.
It was written from the Tor specification documents, which are available here.
Orchid runs on Java ...
It seems you have installed the Tor package, either from Tor directly or as a Debian package. By default the software is set up to start by system start and it always runs in the background. So this is expected behaviour.
You can disable this with systemd or with startup scripts.
From the Tor manual:
Other options can be specified on the command-line in the format "--option value", in the format "option value", or in a configuration file. For instance, you can tell Tor to start listening for SOCKS connections on port 9999 by passing --SocksPort 9999 or SocksPort 9999 to it on the command line, or by putting "SocksPort 9999" in the ...
If you want to use Tor Browser's Tor instance you'll have to use TorPort 9150. Alternatively, you can install a global Tor instance.
This doesn't work if you're running the alpha version of Tor Broswer on a Unix-like system, it uses a Unix socket instead. You should also expect the stable series to switch to Unix sockets before long.
GeoIP needs to be installed for Tor to be able to determine in what country a exit relay is.
You can install it using sudo apt install tor-geoipdb.
From the logs:
We've been configured to use (or avoid) nodes in certain countries, and we need GEOIP information to figure out which ones they are. Do you have the tor-geoipdb package installed?".
You want to configure Tor to use an upstream proxy.
Tor Button/Onion Menu -> Network Settings -> Tick 'This computer needs to use a local proxy to access the Internet'
Proxy Type: SOCKS5
Port: Enter the port number you set for -D here
Username and Password: Leave blank
Now the Tor that Tor Browser launches will connect ...
You're not trying to speak SOCKS, the SOCKS port only speaks the SOCKS protocol.
Decimal 22 is hexadecimal 0x16, which is the initial byte of a TLS connection. Tor's SOCKS port does not speak TLS. You cannot arbitrarily add TLS onto the SOCKS connection.
No one can MITM between you and a localhost proxy without being an administrator or having privileges ...
Well, privoxy and polipo are basically even: they both have filtering systems inside them, both are HTTP-to-SOCKS tools. In the last beta of tor you have a HTTPS proxy embedded in tor itself, so I'd rather recommend you to use an embedded one. To do so you should add HTTPTunnelPort directive to your torrc like this:
All certificates types are listed here, see section "A.1. List of certificate types"
 - Ed25519 signing key with an identity key
(see prop220 section 4.2)
 - TLS link certificate signed with ed25519 signing key
(see prop220 section 4.2)
** - Reserved for RSA identity cross-certification;
(see section 2.3 ...
You can use any TCP-based service. Try to use VNC+noVNC or X11 + js/html5 X server. It will be 100% in-Tor/in-browser solution for easy connections. If you're serious about using it extensively - X11+ssh is your very best friend
socat TCP4-LISTEN:31337,reuseaddr,fork,bind=127.0.0.1 SOCKS4A:127.0.0.1:myserver.foo:3389,socksport=9050,socksuser=rdp
This will listen on TCP port 31337 at address 127.0.0.1 and for each incoming connection, connect through a SOCKS4A proxy to 127.0.0.1 on port 9050 (Tor) to myserver.foo on port 3389.
This won't work on Tails, due to it's ...
There is PORTAL of Pi which bridges ethernet to wireless on an RPi, intended for use with Arch Linux ARM, there is also PORTAL of Raspbian which is the same, except ported to the Raspbian.
You should be aware that there are serious security issues associated with these kinds of device, especially if the client device is connecting to it over wireless, and ...
To fix all the DNS issues like that I do recommend you to use a local resolver configured for using Tor as a transport, but serving your system as usual. I'm using ISC Bind, works like a charm. Don't fprget to edit /etc/resolv.conf and so forth.