From: phillip.lord@russet.org.uk (Phillip Lord)
To: "Etienne Prud’homme" <e.e.f.prudhomme@gmail.com>
Cc: Emacs Devel <emacs-devel@gnu.org>,
"Perry E. Metzger" <perry@piermont.com>
Subject: Re: Alerting users to new releases
Date: Thu, 21 Sep 2017 21:05:20 +0100 [thread overview]
Message-ID: <87377f24xr.fsf@russet.org.uk> (raw)
In-Reply-To: <87mv5zsd6e.fsf@x230.lts> ("Etienne Prud’homme"'s message of "Tue, 12 Sep 2017 19:35:37 -0400")
Etienne Prud’homme <e.e.f.prudhomme@gmail.com> writes:
> "Perry E. Metzger" <perry@piermont.com> writes:
>
>> Would it be reasonable if a feature was added to Emacs to alert the
>> user that a newer version of Emacs existed? Or would the potential
>> privacy issues, even if the check could be turned off, exceed the
>> benefit?
>
> I was actually thinking about the same thing!
>
> We could of course allow an opt-in variable that would allow checking
> for any vulnerability in the current GNU Emacs version installed, but
> most people won’t be aware of it or won’t bother using it.
>
> One way to get around it would be to use the ELPA protocol. When
> downloading packages, there could be a file describing current
> vulnerabilities and affected versions. The client will then warn the
> user accordingly and allow displaying a custom message.
There has already been a discussion about a security patches
package. Surely this is the same thing? I mean, you add a "release"
package. New release happens, "release" on ELPA gets updated.
If 26.0 checked for new packages and auto-upgraded "security" and
"release", then we would have everything we need.
Phil
next prev parent reply other threads:[~2017-09-21 20:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-12 21:59 Alerting users to new releases Perry E. Metzger
2017-09-12 23:35 ` Etienne Prud’homme
2017-09-21 20:05 ` Phillip Lord [this message]
2017-09-12 23:37 ` Clément Pit-Claudel
2017-09-13 5:29 ` Sebastian Christ
2017-09-13 12:18 ` Stefan Monnier
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=87377f24xr.fsf@russet.org.uk \
--to=phillip.lord@russet.org.uk \
--cc=e.e.f.prudhomme@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=perry@piermont.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.