From: Stefan Kangas <stefankangas@gmail.com>
To: Tim Cross <theophilusx@gmail.com>, emacs-devel@gnu.org
Subject: Re: Fwd: Should package.el support notifying on package security updates?
Date: Fri, 12 Aug 2022 06:18:52 -0700 [thread overview]
Message-ID: <CADwFkmmDiZJO0kJZVbHvM+8RQ6Nw=Jx1h8KZyOG6syg__i7W0g@mail.gmail.com> (raw)
In-Reply-To: <86y1vul261.fsf@gmail.com>
Tim Cross <theophilusx@gmail.com> writes:
> - 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.
If they are rare, that doesn't make them less important.
> - It would require package maintainers to somehow flag that an update is
> a security update
I find the maintainers of important packages to be highly conscientious
people, and that goes in particular the GNU ELPA maintainers. So I
don't share your concerns.
> I suspect if we added the functionality to flag an update as a security
> update, it is something which happens so rarely, nobody will use it and
> when they do, nobody will recognise what it really meant.
I think people will know the meaning, because it will presumably say
"security update" somewhere.
next prev parent reply other threads:[~2022-08-12 13:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87r12qm4q5.fsf@gmail.com>
2022-08-08 1:46 ` Fwd: Should package.el support notifying on package security updates? Gulshan Singh
2022-08-12 0:04 ` Matt Armstrong
2022-08-12 0:29 ` Tim Cross
2022-08-12 13:18 ` Stefan Kangas [this message]
2022-08-13 0:44 ` Tim Cross
2022-08-12 21:40 ` Stefan Monnier
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
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='CADwFkmmDiZJO0kJZVbHvM+8RQ6Nw=Jx1h8KZyOG6syg__i7W0g@mail.gmail.com' \
--to=stefankangas@gmail.com \
--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 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).