From: Ihor Radchenko <yantar92@posteo.net>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: Husain Alshehhi <husain@alshehhi.io>, emacs-devel@gnu.org
Subject: Re: Security in the emacs package ecosystem
Date: Sat, 18 Feb 2023 10:57:34 +0000 [thread overview]
Message-ID: <87a61bkzq9.fsf@localhost> (raw)
In-Reply-To: <CADwFkm=7XcgxNoAN380sYpq+xJRH8_tJSkachv6tE4bdtJ9oyw@mail.gmail.com>
Stefan Kangas <stefankangas@gmail.com> writes:
>> 2. Allow users to demand package.el to verify signatures when
>> downloading packages. Interested users can then increase their
>> security by rejecting packages without .sig file.
>
> Maybe I'm missing something, but isn't that `package-check-signature'?
It is. I found it shortly after sending my message.
> Its current default is `allow-unsigned', however, which is about as
> useful for security purposes as if it was nil. I think we should
> consider changing it to t in Emacs 30.
If the default is t, users will be forced to have OpenPGP installed.
Maybe the default should be like t, but only when OpenPGP is available.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2023-02-18 10:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-15 20:53 Security in the emacs package ecosystem Husain Alshehhi
2023-02-04 13:12 ` Ihor Radchenko
2023-02-04 16:59 ` Stefan Kangas
2023-02-17 10:21 ` Ihor Radchenko
2023-02-17 10:23 ` Ihor Radchenko
2023-02-17 15:54 ` Stefan Kangas
2023-02-18 10:57 ` Ihor Radchenko [this message]
2023-02-18 11:49 ` Eli Zaretskii
2023-02-20 5:18 ` Richard Stallman
2023-02-20 6:23 ` Po Lu
2023-02-20 17:38 ` chad
2023-03-11 19:45 ` Thomas Koch
2023-03-14 4:00 ` Richard Stallman
2023-02-18 11:54 ` Making `package-check-signature' more restrictive by default 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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a61bkzq9.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-devel@gnu.org \
--cc=husain@alshehhi.io \
--cc=stefankangas@gmail.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/emacs.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).