From: "Ludovic Courtès" <ludo@gnu.org>
To: Bengt Richter <bokr@bokr.com>
Cc: 37744@debbugs.gnu.org
Subject: bug#37744: Per-user profile directory hijack (CVE-2019-17365 for Nix)
Date: Fri, 18 Oct 2019 16:36:30 +0200 [thread overview]
Message-ID: <877e5215ox.fsf@gnu.org> (raw)
In-Reply-To: <20191018022128.GA1765@PhantoNv4ArchGx.localdomain> (Bengt Richter's message of "Thu, 17 Oct 2019 19:21:28 -0700")
Bengt Richter <bokr@bokr.com> skribis:
> On +2019-10-17 22:25:58 +0200, Ludovic Courtès wrote:
[...]
>> > Imperialist nitpick: why list the foreigners first? :-)
>> >
>> > Anti-imperialist nitpick: reversing the two allows using ‘other
>> > distributions’ instead of ‘foreign’ which always sounds a bit
>> > dismissive to my ears.
>> >
>> > End nitpick.
>>
>> That makes sense to me; I’m not satisfied with “foreign” either (I think
>> the inspiration came from FFIs, but still). Maybe “fellow distros”?
>> :-)
>
> Is not the important distinction whether the "foreign distro" can be generated
> with pure guix libre components using a pure guix tool chain vs not?
“Foreign distro” designates any distro other than Guix System. From a
technical viewpoint, it’s sometimes useful to be able to make that
distinction.
HTH,
Ludo’.
next prev parent reply other threads:[~2019-10-18 14:37 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-14 7:47 bug#37744: Per-user profile directory hijack (CVE-2019-17365 for Nix) Ludovic Courtès
2019-10-14 7:58 ` Ludovic Courtès
2019-10-14 11:53 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2019-10-14 16:37 ` Maxim Cournoyer
2019-10-15 12:34 ` Ludovic Courtès
2019-10-15 14:31 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2019-10-16 6:57 ` Ludovic Courtès
2019-10-16 10:22 ` Ludovic Courtès
2019-10-16 13:25 ` Ludovic Courtès
2019-10-16 14:22 ` pelzflorian (Florian Pelz)
2019-10-16 15:16 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2019-10-16 15:19 ` pelzflorian (Florian Pelz)
2019-10-16 15:23 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2019-10-16 17:05 ` Ludovic Courtès
2019-10-16 19:50 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2019-10-16 19:55 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2019-10-16 21:40 ` Ludovic Courtès
2019-10-16 21:41 ` Ludovic Courtès
2019-10-16 19:58 ` Julien Lepiller
2019-10-16 21:38 ` Ludovic Courtès
2019-10-16 15:37 ` pelzflorian (Florian Pelz)
2019-10-16 21:39 ` Ludovic Courtès
2019-10-17 2:58 ` pelzflorian (Florian Pelz)
2019-10-17 3:01 ` pelzflorian (Florian Pelz)
2019-10-16 20:28 ` Ludovic Courtès
2019-10-17 16:18 ` Ludovic Courtès
2019-10-17 19:01 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2019-10-17 20:25 ` Ludovic Courtès
2019-10-18 2:21 ` Bengt Richter
2019-10-18 14:36 ` Ludovic Courtès [this message]
2019-10-19 1:32 ` Bengt Richter
2019-10-16 14:12 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2019-10-16 20:01 ` Ludovic Courtès
2019-10-16 16:28 ` Julien Lepiller
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=877e5215ox.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=37744@debbugs.gnu.org \
--cc=bokr@bokr.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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).