From: Richard Stallman <rms@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 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 00:18:42 -0500 [thread overview]
Message-ID: <E1pTyZW-00006P-AE@fencepost.gnu.org> (raw)
In-Reply-To: <83edqnyz00.fsf@gnu.org> (message from Eli Zaretskii on Sat, 18 Feb 2023 13:49:35 +0200)
[[[ To any NSA and FBI agents reading my email: please consider ]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]
> > Maybe the default should be like t, but only when OpenPGP is available.
> We could also display a warning, once, when we detect that OpenPGP is
> not available and set the value to allow-unsigned. This way the user
> is alerted to the problem and can take action to fix it.
Alternatively, we could use Autoconf to check for GPG or PGP
when building Emacs.
--
Dr Richard Stallman (https://stallman.org)
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
next prev parent reply other threads:[~2023-02-20 5:18 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 [this message]
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=E1pTyZW-00006P-AE@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=husain@alshehhi.io \
--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).