unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars-Dominik Braun <lars@6xq.net>
To: Ryan Prior <ryanprior@hey.com>
Cc: Development of GNU Guix and the GNU System distribution
	<guix-devel@gnu.org>
Subject: Re: Mitigating "dependency confusion" attacks on Guix users
Date: Wed, 10 Feb 2021 08:48:25 +0100	[thread overview]
Message-ID: <YCOPyaByLzk2MRik@noor.fritz.box> (raw)
In-Reply-To: <461926c3d053474dd7196c9ed8f59a45b8c9c82f@hey.com>

Hi,

very interesting read.

> However, I'm still thinking about how to attack Guix users. Somebody who
> adds an internal channel for their own packages could still be
> vulnerable to a dependency confusion attack via a compromised or
> manipulated Guix maintainer. The target of the attack could install
> packages they believed would be provided by their internal channel but
> actually get another package provided upstream.
Usually you’d use module imports and variable names inside your
channel’s packages. Wouldn’t that defeat this attack? (Depending on
Guix’/Guile’s module loading order of course.)

What about substitute servers? As far as I understand as soon as they’re
authorized they can deliver substitutes for *any* package.

Lars



  reply	other threads:[~2021-02-10  7:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-10  0:08 Mitigating "dependency confusion" attacks on Guix users Ryan Prior
2021-02-10  7:48 ` Lars-Dominik Braun [this message]
2021-02-10  7:51 ` Christopher Baines
2021-02-10 14:33   ` Jonathan Frederickson
2021-02-10 15:12   ` Efraim Flashner
2021-02-10 11:28 ` zimoun

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=YCOPyaByLzk2MRik@noor.fritz.box \
    --to=lars@6xq.net \
    --cc=guix-devel@gnu.org \
    --cc=ryanprior@hey.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).