unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Giovanni Biscuolo <g@xelera.eu>
Cc: guix-devel@gnu.org
Subject: Re: "Trojan Source" (CVE-2021-42574 and CVE-2021-42694): can 'guix lint' help someway?
Date: Tue, 09 Nov 2021 18:05:26 +0100	[thread overview]
Message-ID: <87tugli7jd.fsf@gnu.org> (raw)
In-Reply-To: <87fssgi04h.fsf@xelera.eu> (Giovanni Biscuolo's message of "Mon,  01 Nov 2021 12:30:38 +0100")

Hi!

Giovanni Biscuolo <g@xelera.eu> skribis:

> The details are published here: https://www.trojansource.codes/

[...]

> Is there a way for "guix lint" to check for the listed (other?)
> "dangerous" codepoints and warn code reviewers?

That would be an expensive operation since that means unpacking the
source and reading each and every file.  ‘guix lint’ usually does
inexpensive checks.

> Is it possible for the Guix community to start a coordinated effort to
> analyze all the source code (ever?!?) published in out git repo to check
> for the presence of this attack?

That sounds unreasonable to me.

> AFAIU there is not much Guix can do for the "Homoglyph attacks"
> (CVE-2021-42694).

Right.  :-)

Guile itself could be “vulnerable” to this, though.  (I’m cautious about
terminology; for example, the ‘sayHello’ example on their web site uses
CYRILLIC CAPITAL LETTER EN vs. LATIN CAPITAL LETTER H.  Sure, their
glyphs are almost “visually indistinguishable”, but they belong to
different alphabets, and I’m wary of the implicit imperialist suggestion
that all things that roughly look like H should be replaced by H.)

Thanks,
Ludo’.


  parent reply	other threads:[~2021-11-09 17:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-01 11:30 "Trojan Source" (CVE-2021-42574 and CVE-2021-42694): can 'guix lint' help someway? Giovanni Biscuolo
2021-11-01 13:38 ` Leo Famulari
2021-11-01 15:04   ` Bengt Richter
2021-11-09 17:05 ` Ludovic Courtès [this message]
2021-11-15 17:20   ` zimoun
2021-11-16 10:06   ` Giovanni Biscuolo

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=87tugli7jd.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=g@xelera.eu \
    --cc=guix-devel@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.
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).