From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Tim Cross <theophilusx@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Fwd: Should package.el support notifying on package security updates?
Date: Fri, 12 Aug 2022 17:40:55 -0400 [thread overview]
Message-ID: <jwv4jyhtaa1.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <86y1vul261.fsf@gmail.com> (Tim Cross's message of "Fri, 12 Aug 2022 10:29:22 +1000")
> - There are actually very few security issues reported for Elisp
> packages. This doesn't mean there aren't any, only that they are
> discovered and reported very rarely.
Agreed.
And I suspect that security issues are much more common than are reported.
[ Lots of Emacs packages are written under the implicit assumption that the
current buffer contains something mildly-trustworthy. ]
> - It would require package maintainers to somehow flag that an update is
> a security update rather than just a standard update. As it is already
> somewhat challenging to get many package maintainers to include
> consistent change logs in their packages, I suspect then also asking
> them to distinguish security updates from normal updatges may be
> asking too much.
I'm not sure it would be a big problem. But I'm not sure it would be an
improvement either. Especially because I suspect it might give the
false impression that the code of ELisp packages is somewhat
security-conscious, whereas in my experience, the vast majority of Emacs
packages isn't (they may end up secure by accident, of course).
Stefan
next prev parent reply other threads:[~2022-08-12 21:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-12 20:54 Should package.el support notifying on package security updates? Gulshan Singh
2022-08-08 1:46 ` Fwd: " Gulshan Singh
2022-08-12 0:04 ` Matt Armstrong
2022-08-12 0:29 ` Tim Cross
2022-08-12 13:18 ` Stefan Kangas
2022-08-13 0:44 ` Tim Cross
2022-08-12 21:40 ` Stefan Monnier [this message]
2022-08-13 0:58 ` Tim Cross
2022-08-13 4:58 ` tomas
2022-08-13 14:00 ` Stefan Monnier
2022-08-14 3:23 ` Richard Stallman
2022-08-14 3:29 ` Gulshan Singh
2022-08-16 2:52 ` Richard Stallman
2022-08-25 3:32 ` Richard Stallman
2022-08-25 4:33 ` Tim Cross
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=jwv4jyhtaa1.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=theophilusx@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 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.