From: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
To: Gottfried <gottfried@posteo.de>
Cc: Csepp <raingloom@riseup.net>, help-guix@gnu.org
Subject: Re: tor
Date: Thu, 1 Sep 2022 16:27:35 +0200 [thread overview]
Message-ID: <20220901162735.785a14c9@primary_laptop> (raw)
In-Reply-To: <92a94bf3-12a8-8743-e338-7906835c9697@posteo.de>
[-- Attachment #1: Type: text/plain, Size: 2518 bytes --]
On Tue, 30 Aug 2022 18:32:26 +0000
Gottfried <gottfried@posteo.de> wrote:
> As far as I understand you I can delete the package:
> tor-client and tor-socks, because I have tor installed.
> Am I right?
tor is just a daemon that somehow connects your machine to the
tor-network but it doesn't automatically route any traffic through that
network.
And to start it you either need to run it manually or configure it in
your list of services in your system.scm with something that looks like
that:
>(service tor-service-type
> (tor-configuration))
The tor-client only contains some utilities that are not very
interesting.
As for torsocks, it's an application to enable other applications to
route their traffic through Tor, but in an extremely unreliable way.
The Tor project documentation has been advising people not to rely on
torsocks because some of the times it doesn't work at all and the
application doesn't use Tor at all, even with torsocks.
And in many cases, with torsocks, very important private information
(like DNS querries) do not go through the Tor network.
The alternative is to configure each applications to talk to the tor
daemon through the socks5 protocol.
And even that is not perfect because if you do that with a browser, the
browser will still not be anonymous because of browser fingerprinting.
But at least your location will be hidden which is already something
good.
Tails works by preventing almost all applications from accessing the
Internet directly, and they are configured for using the Tor daemon.
So if there is any application misbehaving, it's not that problematic
because the only way the applications can send data is through Tor.
To have something like that in Guix we would need to package the ferm
firewall tool Tails used to implement this, and have users adapt the
Tails ferm configuration for their usage and/or enable users to use a
default configuration that is very restrictive (and so doesn't work for
everybody).
I've managed to relatively easily reproduce something like that on
Parabola (because ferm is packaged there), but not yet to have a fully
functional system with it because I didn't manage yet to run the
tor-browser as another user yet, which is required for that setup to
work.
The issue is that we obviously need to put more resources on things
like that (by funding the tor-project, having more people work on that,
etc), but resources are also not easy to find.
Denis.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-09-01 14:41 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-28 10:52 tor Gottfried
2022-08-28 12:09 ` tor Csepp
2022-08-29 14:19 ` tor Gottfried
2022-08-30 10:54 ` tor Csepp
2022-08-30 18:32 ` tor Gottfried
2022-08-31 16:23 ` tor Denis 'GNUtoo' Carikli
2022-09-01 13:59 ` tor Denis 'GNUtoo' Carikli
2022-09-02 18:31 ` tor Gottfried
2022-09-21 9:52 ` tor Gottfried
2022-09-22 11:52 ` tor Chris Keschnat via
2022-09-01 14:27 ` Denis 'GNUtoo' Carikli [this message]
2022-09-01 17:35 ` tor Gottfried
2022-09-01 23:35 ` tor Denis 'GNUtoo' Carikli
2022-11-05 0:29 ` tor Denis 'GNUtoo' Carikli
2022-11-07 19:24 ` tor Gottfried
2022-11-07 20:14 ` tor Wojtek Kosior via
2022-11-07 23:19 ` tor Denis 'GNUtoo' Carikli
-- strict thread matches above, loose matches on Subject: below --
2022-09-23 16:36 tor Gottfried
2020-09-17 12:32 Tor Rasa Gulla via
2020-09-17 13:15 ` Tor Julien Lepiller
2020-09-17 13:18 ` Tor Rasa Gulla
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=20220901162735.785a14c9@primary_laptop \
--to=gnutoo@cyberdimension.org \
--cc=gottfried@posteo.de \
--cc=help-guix@gnu.org \
--cc=raingloom@riseup.net \
/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).