unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Leo Famulari <leo@famulari.name>
Cc: 53461@debbugs.gnu.org
Subject: [bug#53461] [kiasoc5@tutanota.com: Rust CVE]
Date: Mon, 24 Jan 2022 16:31:25 -0500	[thread overview]
Message-ID: <87ee4w6csy.fsf@gmail.com> (raw)
In-Reply-To: <Ye2sclMdhTU/E5xE@jasmine.lan> (Leo Famulari's message of "Sun, 23 Jan 2022 14:28:50 -0500")

Hi,

Leo Famulari <leo@famulari.name> writes:

> On Sat, Jan 22, 2022 at 10:33:52PM -0500, Maxim Cournoyer wrote:
>> The rust-1.57 variable should probably be made private or hidden now.
>> 
>> Also, unless we rebuild all crates with rust-1.58, it seems to me like
>> we won't be addressing the problem, as the CVE touches the
>> 'remove_dir_all' procedure part of the standard library of Rust (and we
>> all know Rust likes to build things statically).
>> 
>> Am I missing something?
>
> I don't know about Rust things! I just forwarded this message from the
> private list to the public list.

OK!  I just asked in #rust and they confirmed what I thought (all crates
-- well the ones using 'std::fs::remove_dir_all' but we can't easily
know) needs to be rebuilt if we are to patch that CVE.

Maxim




  reply	other threads:[~2022-01-24 21:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-23  0:29 [bug#53461] [kiasoc5@tutanota.com: Rust CVE] Leo Famulari
2022-01-23  3:33 ` Maxim Cournoyer
2022-01-23 19:28   ` Leo Famulari
2022-01-24 21:31     ` Maxim Cournoyer [this message]
2022-01-25  4:30       ` Leo Famulari
2022-01-25 23:06         ` Maxim Cournoyer
2022-01-26  2:57           ` Leo Famulari
2022-01-27 21:59             ` Maxim Cournoyer
2022-02-26  6:07 ` kiasoc5--- via Guix-patches via
2022-02-26 10:35   ` Maxime Devos
2022-02-27  6:50     ` kiasoc5--- via Guix-patches via

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=87ee4w6csy.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=53461@debbugs.gnu.org \
    --cc=leo@famulari.name \
    /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).