From: Joshua Branson <jbranso@dismail.de>
To: help-guix@gnu.org
Subject: Re: Problem with Tor & IceCat
Date: Sun, 13 Jan 2019 13:14:31 -0500 [thread overview]
Message-ID: <87y37os9vc.fsf@dismail.de> (raw)
In-Reply-To: <87y37s4t7k.fsf@elephly.net> (Ricardo Wurmus's message of "Thu, 10 Jan 2019 13:01:35 +0100")
Ricardo Wurmus <rekado@elephly.net> writes:
> Joshua Branson <jbranso@dismail.de> writes:
>
>> Archetyp Jung <archetyp@e.mail.de> writes:
>>
>>> Sorry Ludo, but I reinstalled the operating system yesterday. :-(
>>>
>>> Thanks to my customized config.scm, everything works fine here,
>>> including Tor. ;-)
>>>
>>> BTW: I no longer use Tor in GNU IceCat with the Tor™ browser button,
>>> but directly via Proxy DNS when using SOCKS v5.
>>
>> Can you describe this setup? I would like to use Tor properly, and
>> currently I cannot. :(
>
> You only need to add (tor-service) to the list of services. Then tell
> your browser to connect to the SOCKS proxy at localhost:9050. If you
> use Epiphany or Eolie that would be done through the network settings
> where you can configure GNOME-wide settings.
>
> For Icecat that would be done in Preferences, searching for “proxy”,
> hitting “Settings…” and specifying a manual proxy in the “SOCKS Host”
> line. Also check the box next to “Proxy DNS when using SOCKS v5”.
Thanks for the information. It seems like I have to check "Proxy DNS
when using SOCKS v5" every time I open IceCat. I suppose that I could
turn off the Icecat plugin and have this written in manually. I can now
connect to some tor hidden services!
http://nzh3fv6jc6jskki3.onion/ --> riseup.net
>
> --
> Ricardo
>
--
Joshua Branson
Sent from Emacs and Gnus
next prev parent reply other threads:[~2019-01-13 18:14 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-06 18:13 Problem with Tor & IceCat Archetyp Jung
2019-01-06 20:09 ` Joshua Branson
2019-01-07 1:37 ` Matthias Lehr
2019-01-07 1:41 ` Archetyp Jung
2019-01-07 8:16 ` Ricardo Wurmus
2019-01-07 11:50 ` Archetyp Jung
2019-01-07 12:08 ` Ricardo Wurmus
2019-01-08 22:46 ` Ludovic Courtès
2019-01-08 23:52 ` Archetyp Jung
2019-01-09 0:18 ` Archetyp Jung
2019-01-09 14:36 ` Joshua Branson
2019-01-09 14:36 ` Joshua Branson
2019-01-10 12:01 ` Ricardo Wurmus
2019-01-10 14:59 ` Joshua Branson
2019-01-13 18:14 ` Joshua Branson [this message]
2019-01-07 2:02 ` Mike Gerwitz
2019-01-07 7:16 ` znavko
2019-01-07 11:37 ` Archetyp Jung
2019-01-07 14:58 ` Joshua Branson
2019-01-07 14:57 ` Joshua Branson
2019-01-06 21:29 ` Chris Marusich
-- strict thread matches above, loose matches on Subject: below --
2019-01-09 16:09 Archetyp Jung
2019-01-09 16:47 Archetyp Jung
2019-01-09 17:24 Archetyp Jung
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y37os9vc.fsf@dismail.de \
--to=jbranso@dismail.de \
--cc=help-guix@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).