unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: znavko <znavko@protonmail.com>
Cc: help-guix@gnu.org
Subject: Re: Other web-browser for tor
Date: Thu, 27 Sep 2018 03:45:08 -0400	[thread overview]
Message-ID: <87o9cjcrjv.fsf@netris.org> (raw)
In-Reply-To: <-gWUFYZtXIy1o1yk-LpWq2xpLnqXz8GS0l2fCpzqLZiJ6Lww_oBiS9_QlgGTd8hElPbzSCuAzswBOzSSkzSxcdk4qB-ezxQToQmn-JlAW3k=@protonmail.com> (znavko's message of "Mon, 24 Sep 2018 16:15:18 +0000")

znavko <znavko@protonmail.com> writes:

> Hello! I am using GNU IceCat, that has Network Settings for using
> proxy. I can use tor with it. I was using Abrowaser on trisquel, but
> GuixSD repository has no such:
>
> $ guix package -s abrowser
> $
>
> I've found other browsers with `guix package -s 'web browser'` but all
> of that I've installed has no Network configurations . Epiphany,
> Dillo, Conkeror can't.  Netsurf browser has network settings, but
> there is only http proxy, and I get this when type proxy:
> 127.0.0.1:9050 : "This is a SOCKs proxy, not an HTTP proxy."
>
> Which other free software browser can work on socks4 proxy? On
> trisquel I had Abrowser, but here it is only Icecat.

Epiphany can be configured to use a SOCKs proxy via the "Network"
section of GNOME settings.

Conkeror can be configured to use a SOCKs proxy.  See
<http://conkeror.org/Proxy>.

For software that does not support SOCKs proxies, you can use 'privoxy'
as a gateway.  'privoxy' presents itself as an HTTP/HTTPS proxy, and it
can be configured to use a SOCKs proxy.  See
<https://www.privoxy.org/faq/misc.html#TOR>.

Dillo can be configured to use an HTTP/HTTPS proxy in its
~/.dillo/dillorc.

Wget and some other command-line utilities will honor the http_proxy and
https_proxy environment variables.  Alternatively, you can configure
wget to use a proxy via ~/.wgetrc.

I do not know off-hand whether these programs leak information in
practice (e.g. by making untorified DNS requests) when configured in
this way.

      Mark

  parent reply	other threads:[~2018-09-27  7:45 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-24 16:15 Other web-browser for tor znavko
2018-09-24 19:50 ` Ricardo Wurmus
2018-09-24 20:20   ` Ricardo Wurmus
     [not found]     ` <m2580mue8DFlH-eFG1WwCBXwFU2y_a7P8KHQOwQEgPQGmGswUy61gF6VmJ71J1MgAdv3dXneg-9gcPfmZsmzKY2AwmcR9HePxP8Yiarya1U=@protonmail.com>
2018-09-26 18:32       ` Ricardo Wurmus
2018-09-26 19:45         ` Pierre Neidhardt
2018-09-25 12:29 ` v88m
2018-09-26 14:46   ` znavko
2018-10-02 10:01     ` Ludovic Courtès
2018-10-02 10:25       ` Pierre Neidhardt
2018-10-02 11:00         ` Ricardo Wurmus
2018-10-02 11:18           ` Pierre Neidhardt
2018-10-02 11:49             ` Ludovic Courtès
2018-10-02 12:34               ` Pierre Neidhardt
2018-10-02 14:06                 ` Ludovic Courtès
2018-10-02 14:36                   ` Pierre Neidhardt
2018-10-04 11:27                     ` Ludovic Courtès
2018-10-04 13:14                       ` Pierre Neidhardt
2018-10-04 17:57                         ` Ricardo Wurmus
2018-10-04 20:17                           ` Pierre Neidhardt
2018-09-27  7:45 ` Mark H Weaver [this message]
2018-09-27  8:03   ` Pierre Neidhardt
2018-09-27  8:09     ` Pierre Neidhardt
2018-10-02 10:00     ` Ludovic Courtès
2018-10-11 16:39 ` Devan Carpenter

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=87o9cjcrjv.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=help-guix@gnu.org \
    --cc=znavko@protonmail.com \
    /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).