unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: "Philip McGrath" <philip@philipmcgrath.com>
To: "Felix Lechner via" <help-guix@gnu.org>
Subject: Re: Icecat and ungoogled chromium in a container
Date: Fri, 03 Mar 2023 09:52:33 -0500	[thread overview]
Message-ID: <d88b3efb-7b24-466f-933a-c160ecbc1616@app.fastmail.com> (raw)
In-Reply-To: <4153f91f-a6f6-8e69-0a87-57227e2312b9@posteo.de>

Hi,

On Wed, Mar 1, 2023, at 11:30 AM, Gottfried wrote:
> (I am using Icecat with the Tor browser)

I’m not sure I understand your configuration, and I rarely use Tor myself, but I wanted to make sure you’re aware that changing even innocuous-seeming settings can expose you to fingerprinting risks:

https://blog.torproject.org/browser-fingerprinting-introduction-and-challenges-ahead/

There’s an especially concise summary at
<https://support.torproject.org/tbb/tbb-14/>:

> If your copy of Tor Browser has a unique fingerprint, your browsing activities can be deanonymized and tracked even though you are using Tor Browser.
>
> Basically, each browser's settings and features create what is called a "browser fingerprint". Most browsers inadvertently create a unique fingerprint for each user which can be tracked across the internet. Tor Browser is specifically engineered to have a nearly identical (we're not perfect!) fingerprint across its users. This means each Tor Browser user looks like every other Tor Browser user, making it difficult to track any individual user.

-Philip


      parent reply	other threads:[~2023-03-03 14:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-01 16:30 Icecat and ungoogled chromium in a container Gottfried
2023-03-01 17:04 ` Dr. Arne Babenhauserheide
2023-03-02 14:27   ` Gottfried
2023-03-02 19:43     ` Wojtek Kosior via
2023-03-27 13:00       ` Dr. Arne Babenhauserheide
2023-03-03 14:52 ` Philip McGrath [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=d88b3efb-7b24-466f-933a-c160ecbc1616@app.fastmail.com \
    --to=philip@philipmcgrath.com \
    --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).