Peter Palfrader:
> Did we ever learn what this was about?
Unfortunately not.
> Without more information this ticket doesn't seem very actionable, alas.
Yes, closing this bug report seems okay. However, If I ever figure out
the reason for this I will let you know! :)
Joonas
On Fri, 17 Feb 2017, Joonas Kylmälä wrote:
> Could it be something simple as different port for the user run tor
> which might cause this? Then it would not be a bug but just my
> university censoring. And also the systemd tor daemon works fine on my
> home network so it must be something related
intrigeri:
> Now I'm confused: the way I understood your bug report, the
> system-wide Tor daemon does *not* connect to the Tor network. And the
> way I understand your reply (quoted above): it does work. Can you
> please clarify?
The systemd tor daemon doesn't connect, but the user run tor progr
Joonas Kylmälä:
> intrigeri:
>> Did you configure the same bridges for the system-wide Tor daemon as
>> the ones you've configured in the Tor Browser's one?
> I didn't configure any bridges for the system wide Tor daemon and
> interestingly it works without them meanwhile Tor Browser doesn't.
Now
Hi,
intrigeri:
> Did you configure the same bridges for the system-wide Tor daemon as
> the ones you've configured in the Tor Browser's one?
I didn't configure any bridges for the system wide Tor daemon and
interestingly it works without them meanwhile Tor Browser doesn't.
-Joonas
Control: tag -1 + moreinfo
> And so it doesn't work. I have had recently problems with my
> university censoring Tor connections (e.g. Tor browser needs to have
> bridges otherwise it doesn't work), but I don't get why tor run as a
> normal user works but not as a daemon.
Did you configure the sa
Package: tor
Version: 0.2.9.9-1
Severity: normal
Dear Maintainer,
If I run 'tor' as normal user I can connect to Tor network, i.e. the
output of running the command is:
--
user@host:~/Downloads/tor-browser_en-US$ tor
Feb 17 08:12:15.018 [notice
7 matches
Mail list logo
