all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Björn Bidar" <bjorn.bidar@thaodan.de>
To: Daniel Fleischer <danflscr@gmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: is melpa just unsigned?
Date: Mon, 29 May 2023 16:12:05 +0300	[thread overview]
Message-ID: <87ilcbb7tm.fsf@thaodan.de> (raw)
In-Reply-To: <m2jzwz2b3u.fsf@gmail.com> (Daniel Fleischer's message of "Tue, 23 May 2023 20:47:49 +0300")

Daniel Fleischer <danflscr@gmail.com> writes:

> Samuel Wales [2023-05-22 Mon 19:53] wrote:
>
>> of course i am aware signing is only part of ensuring security,
>> and melpa does curating, and authors or computers could turn evil, but
>> where there is a chain that reliably goes back to an author from the
>> code you dled, it's a pretty good feeling.
>
> Not a security expert but signing helps with downloading files from
> questionable hosting (usually you download the signature from the same
> website, thus you solve nothing). You can skip the middleman melpa.org
> and install packages directly from their respective forges, e.g. github,
> gitlab, sourcehut using either something like quelpa or built-in
> package-vc-install.

Another alternative is borg + magit + epkg.

The workflow makes it quite easy to contribute and test changes in
packages.



      parent reply	other threads:[~2023-05-29 13:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-18  4:21 is melpa just unsigned? Samuel Wales
2023-05-19  0:02 ` Michael Heerdegen
2023-05-20 19:00   ` Emanuel Berg
2023-05-21 23:36     ` Michael Heerdegen
2023-05-23  2:53       ` Samuel Wales
2023-05-23  3:17         ` Platon Pronko
2023-05-23  3:21         ` [External] : " Drew Adams
2023-05-23 17:47         ` Daniel Fleischer
2023-05-26  6:07           ` Samuel Wales
2023-05-29 13:12           ` Björn Bidar [this message]

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=87ilcbb7tm.fsf@thaodan.de \
    --to=bjorn.bidar@thaodan.de \
    --cc=danflscr@gmail.com \
    --cc=help-gnu-emacs@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.