From: chad <yandros@gmail.com>
To: rms@gnu.org
Cc: Eli Zaretskii <eliz@gnu.org>,
yantar92@posteo.net, stefankangas@gmail.com, husain@alshehhi.io,
emacs-devel@gnu.org
Subject: Re: Security in the emacs package ecosystem
Date: Mon, 20 Feb 2023 12:38:03 -0500 [thread overview]
Message-ID: <CAO2hHWZ6mz6oCmeFrxKj9KN1J2=Y_wCe94LzjBcNMr3WPy2p6g@mail.gmail.com> (raw)
In-Reply-To: <E1pTyZW-00006P-AE@fencepost.gnu.org>
[-- Attachment #1: Type: text/plain, Size: 503 bytes --]
On Mon, Feb 20, 2023 at 12:19 AM Richard Stallman <rms@gnu.org> wrote:
> Alternatively, we could use Autoconf to check for GPG or PGP
> when building Emacs.
>
Practically speaking, I expect this concern to apply mostly when users
install but don't build their own emacs, plus it is likely to misfire when
distributors build emacs.
Separately, if we think this is important enough to *want* GPG/PGP/etc more
often, we could ask the distros to add it as an optional dependency.
Hope that helps,
~Chad
[-- Attachment #2: Type: text/html, Size: 900 bytes --]
next prev parent reply other threads:[~2023-02-20 17:38 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
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 [this message]
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='CAO2hHWZ6mz6oCmeFrxKj9KN1J2=Y_wCe94LzjBcNMr3WPy2p6g@mail.gmail.com' \
--to=yandros@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=husain@alshehhi.io \
--cc=rms@gnu.org \
--cc=stefankangas@gmail.com \
--cc=yantar92@posteo.net \
/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).