all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Kelly Dean <kelly@prtime.org>
To: Richard Stallman <rms@gnu.org>
Cc: 19479@debbugs.gnu.org
Subject: bug#19479: Package manager vulnerable
Date: Tue, 06 Jan 2015 06:38:12 +0000	[thread overview]
Message-ID: <7H65S0MOziz4Z4bzCiATJJDvxaiWHmPOI3K95M87DGM@local> (raw)
In-Reply-To: <E1Y8Bor-0003yH-Mu@fencepost.gnu.org>

Richard Stallman wrote:
> What do we need to do on ftp.gnu.org to avoid these dangers?

It depends on what you expect the user's responsibility to be.

If you expect him to know the latest version number of a package (without relying on the gnu.org webserver to find out, in case it's compromised), and you expect him to manually verify that his download is the latest version (in addition to verifying the signature, of course), and you give him the ability to do this by always including both the name and the version number in your packages (so far as I'm aware, you already do) and never re-using version numbers (I think you're ok here too), then you have no problem, so there's nothing you need to do.

Otherwise, the problems and solution are the same as for package distribution systems in general, as detailed at
https://www.cs.arizona.edu/stork/packagemanagersecurity/attacks-on-package-managers.html
https://www.cs.arizona.edu/stork/packagemanagersecurity/otherattacks.html





       reply	other threads:[~2015-01-06  6:38 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1Y8Bor-0003yH-Mu@fencepost.gnu.org>
2015-01-06  6:38 ` Kelly Dean [this message]
2015-01-07  4:27   ` bug#19479: Package manager vulnerable Richard Stallman
2015-02-24 18:11 bug#19479: Disclaimer is now on file at FSF Glenn Morris
2015-02-24 23:02 ` Kelly Dean
2015-02-25 21:09   ` Glenn Morris
2017-09-02 12:24     ` Eli Zaretskii
  -- strict thread matches above, loose matches on Subject: below --
2015-01-08  3:44 bug#19479: [PATCH] Re: bug#19479: Package manager vulnerable Glenn Morris
2015-01-08  5:29 ` Kelly Dean
2015-01-08 14:39   ` Stefan Monnier
2015-01-08 21:06     ` Kelly Dean
2015-01-09  2:37       ` Stefan Monnier
2015-01-08  3:31 bug#19479: [PATCH] " Kelly Dean
2015-01-08  5:50 ` bug#19536: [PATCH] package-upload-buffer-internal fails for tar files Stefan Monnier
2015-01-08 11:40   ` bug#19479: Package manager vulnerable Kelly Dean
2014-12-30 10:42 Emacs package manager vulnerable to replay attacks Kelly Dean
2015-01-01 12:38 ` bug#19479: Package manager vulnerable Kelly Dean
2015-01-04 20:00   ` Stefan Monnier
2015-01-05  1:11     ` Kelly Dean
2015-01-05  2:16       ` Stefan Monnier
2017-09-03  1:10   ` Glenn Morris
2019-10-04  9:49   ` Stefan Kangas
2020-05-06  0:55     ` Noam Postavsky
2020-09-06 23:59       ` Stefan Kangas
2020-09-07 14:14         ` Noam Postavsky
2020-09-07 18:11           ` Stefan Kangas
2020-09-07 17:19   ` Stefan Kangas
2020-09-07 23:54     ` Noam Postavsky
2020-09-08  8:10       ` Stefan Kangas

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=7H65S0MOziz4Z4bzCiATJJDvxaiWHmPOI3K95M87DGM@local \
    --to=kelly@prtime.org \
    --cc=19479@debbugs.gnu.org \
    --cc=rms@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.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.