Bruno Meneguele
Bruno Meneguele
@GouveaHeitor @naltun ok, I just got the same error while playing around with nipe in my machine (not container). Not even a direct request to `https://check.torproject.org/api/ip` with `curl` worked. What...
@GouveaHeitor the idea is to keep both nipe and tor running on the same container? If so, yep, it may work without any problems. I have another idea that we'll...
Just fyi, this issue reflects the same behavior found in issue #49 .
Hi @GouveaHeitor, I'm working in a patch somewhat related to this issue. Will try to add this behavior.
Checking how tor works with multiple instances of itself I found that the command systemd runs (and that Nipe uses) for executing tor is: `/usr/bin/tor --runasdaemon 0 --defaults-torrc /usr/share/tor/defaults-torrc -f...
Ok, forget it. The systemd [email protected] file is present only in Fedora's tor package, I didn't find it not even in OpenSuse (which is a systemd and rpm based distro)...
Ok, this issue is partially solved by the PR #87. What I mean by "partially" is that with that code Nipe accepts different custom config files created by the user,...
@karencho777 , considering bridges are tor-related subject you don't have to do anything other than configure the tor client config file to actually work as a "bridge user" (please, refer...
I worked it around by completely dropping the ANSI chars rendering when the output is sent to something different of a real terminal (e.g. pipe, `cat file.txt | less`): ```go...
Any update? 1.88 was released already with several bug fixes of 1.87 I/O queue changes.