From: Gottfried <gottfried@posteo.de>
To: Julien Lepiller <julien@lepiller.eu>, help-guix@gnu.org
Subject: Re: how can I use "tor"
Date: Mon, 25 Jul 2022 09:33:22 +0000 [thread overview]
Message-ID: <39dafe2e-d18e-2d4b-a295-fa130f403988@posteo.de> (raw)
In-Reply-To: <9709CA1A-ACEF-40C8-9436-52F56B076AEB@lepiller.eu>
[-- Attachment #1.1.1: Type: text/plain, Size: 919 bytes --]
Hi,
thanks for all Information, I am very happy.
Would it be a little bit safer to have Icecat in a container?
If so, how to set it up?
and will Guix automatically upgrade it, when it's in a container?
Gottfried
Am 24.07.22 um 12:47 schrieb Julien Lepiller:
> Two issues:
>
> First, the tor project is asking distros not to build the tor browser themselves. That includes Guix. That is because a build with Guix will make it distinguishable from the tor-browser built by the tor project.
>
> Second, the tor-browser built by the tor project assumes FHS (/bir, /lib, etc) which guix doesn.t provide, so you can't run it directly.
>
> Of course it's not great for anonymity since icecat is way more distinguishable than the tor-browser built by guix would be.
>
> You could use different profiles in icecat, one with tor settings, one without. You can run icecat -P to select profiles.
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3191 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
prev parent reply other threads:[~2022-07-25 9:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-21 17:49 how can I use "tor" Gottfried
2022-07-21 17:57 ` (
2022-07-21 20:35 ` Julien Lepiller
2022-07-22 14:57 ` Gottfried
2022-07-22 15:20 ` Julien Lepiller
2022-07-22 20:59 ` Csepp
2022-07-24 10:04 ` Gottfried
2022-07-24 10:13 ` Julien Lepiller
2022-07-24 10:20 ` Gottfried
2022-07-24 10:47 ` Julien Lepiller
2022-07-25 9:33 ` Gottfried [this message]
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=39dafe2e-d18e-2d4b-a295-fa130f403988@posteo.de \
--to=gottfried@posteo.de \
--cc=help-guix@gnu.org \
--cc=julien@lepiller.eu \
/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).