From: Julien Lepiller <julien@lepiller.eu>
To: luhux <luhux@outlook.com>,42996@debbugs.gnu.org
Subject: bug#42996: icecat can escape from `guix environment --container`
Date: Sun, 23 Aug 2020 11:38:47 -0400 [thread overview]
Message-ID: <0A2DC743-BCC0-4585-8249-938A8632ACC1@lepiller.eu> (raw)
In-Reply-To: <PSXP216MB0136758B6506DFDE10277085A0590@PSXP216MB0136.KORP216.PROD.OUTLOOK.COM>
[-- Attachment #1: Type: text/plain, Size: 1111 bytes --]
One possibility is that you're seeing the virtual root filesystem, that thwuld only have a few direccories and the structure up to the directory you created your container in. Are you sure you can access files outside of the directory you started icecat in?
Another possiblity is that you had a running icecat outside of the container. In that case, calling icecat from tge container only opens a new window in the un-containerized icecat. Could it be what's happening?
Le 23 août 2020 06:18:49 GMT-04:00, luhux <luhux@outlook.com> a écrit :
>I am using guix environment --container to isolate some programs that
>are prone to leak information. guix environment --container works well
>in freerdp and other programs until I use guix environment --container
>to containerize icecat,
>
>Steps to reproduce:
>
>guix environmnt --container (...some options...) --ad-hoc icecat
>
>Select the address bar and write:'file://' and then access, icecat can
>still access the content outside the container.
>
>Please forgive me for some inappropriate words. My English is not very
>good.
>
>luhux
[-- Attachment #2: Type: text/html, Size: 1376 bytes --]
next prev parent reply other threads:[~2020-08-23 15:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-23 10:18 bug#42996: icecat can escape from `guix environment --container` luhux
2020-08-23 15:38 ` Julien Lepiller [this message]
[not found] ` <PSXP216MB013647CD5DB04CD7F1A49873A0560@PSXP216MB0136.KORP216.PROD.OUTLOOK.COM>
2020-08-24 11:17 ` Julien Lepiller
2020-08-23 16:45 ` Leo Famulari
2020-08-23 16:55 ` Leo Famulari
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0A2DC743-BCC0-4585-8249-938A8632ACC1@lepiller.eu \
--to=julien@lepiller.eu \
--cc=42996@debbugs.gnu.org \
--cc=luhux@outlook.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.