unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Gottfried <gottfried@posteo.de>
To: "Dr. Arne Babenhauserheide" <arne_bab@web.de>
Cc: help-guix@gnu.org
Subject: Re: Icecat and ungoogled chromium in a container
Date: Thu,  2 Mar 2023 14:27:41 +0000	[thread overview]
Message-ID: <58703857-f21c-f3b6-c96d-76da2afcc655@posteo.de> (raw)
In-Reply-To: <87k0009z9e.fsf@web.de>


[-- Attachment #1.1.1: Type: text/plain, Size: 890 bytes --]

Hi,

thank you.

I downloaded this file with wget.

But how can I now use it? What do I have to do?

Is it only for icecat? or can I use it also for chromium?

Kind regards

Gottfried


Am 01.03.23 um 18:04 schrieb Dr. Arne Babenhauserheide:
> 
> Gottfried <gottfried@posteo.de> writes:
>> would it be a significant improvement for security if I used
>> Icecat and ungoogled chromium always in a container?
>> (I am using Icecat with the Tor browser)
> 
> I’m not sure about security of a container there — it could help if
> there’s an unpatched vulnerability in icecat, but not so much otherwise.
> 
> But what can already help a lot is having a separate profile. Here’s an
> example script that creates a locked-down profile on the fly:
> 
> https://github.com/hyphanet/browser/blob/main/freenetbrowser.in#L177
> 
> Best wishes,
> Arne

-- 



[-- 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 --]

  reply	other threads:[~2023-03-02 14:28 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 [this message]
2023-03-02 19:43     ` Wojtek Kosior via
2023-03-27 13:00       ` Dr. Arne Babenhauserheide
2023-03-03 14:52 ` Philip McGrath

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=58703857-f21c-f3b6-c96d-76da2afcc655@posteo.de \
    --to=gottfried@posteo.de \
    --cc=arne_bab@web.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).