From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Ted Zlatanov Newsgroups: gmane.emacs.devel Subject: Re: security-patches package Date: Sat, 16 Sep 2017 11:50:02 -0400 Organization: =?utf-8?B?0KLQtdC+0LTQvtGAINCX0LvQsNGC0LDQvdC+0LI=?= @ Cienfuegos Message-ID: <87tw02hcd1.fsf@lifelogs.com> References: <87wp55t0un.fsf@petton.fr> <87tw07kikp.fsf@gnu.org> <161eff40ff05df7d5577e2456baa1676.squirrel@cloud103.planethippo.com> <87a81xhxh0.fsf_-_@lifelogs.com> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1505577073 7875 195.159.176.226 (16 Sep 2017 15:51:13 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sat, 16 Sep 2017 15:51:13 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.0.50 (gnu/linux) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Sep 16 17:51:10 2017 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dtFN7-0001tR-V9 for ged-emacs-devel@m.gmane.org; Sat, 16 Sep 2017 17:51:10 +0200 Original-Received: from localhost ([::1]:57719 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dtFND-0000y1-Nr for ged-emacs-devel@m.gmane.org; Sat, 16 Sep 2017 11:51:15 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:39311) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dtFME-0000vP-0N for emacs-devel@gnu.org; Sat, 16 Sep 2017 11:50:16 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dtFMA-0002Sv-3z for emacs-devel@gnu.org; Sat, 16 Sep 2017 11:50:14 -0400 Original-Received: from [195.159.176.226] (port=43580 helo=blaine.gmane.org) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1dtFM9-0002S5-To for emacs-devel@gnu.org; Sat, 16 Sep 2017 11:50:10 -0400 Original-Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1dtFM0-0008HH-GF for emacs-devel@gnu.org; Sat, 16 Sep 2017 17:50:00 +0200 X-Injected-Via-Gmane: http://gmane.org/ Mail-Followup-To: emacs-devel@gnu.org Original-Lines: 35 Original-X-Complaints-To: usenet@blaine.gmane.org X-Face: bd.DQ~'29fIs`T_%O%C\g%6jW)yi[zuz6; d4V0`@y-~$#3P_Ng{@m+e4o<4P'#(_GJQ%TT= D}[Ep*b!\e,fBZ'j_+#"Ps?s2!4H2-Y"sx" Mail-Copies-To: never Cancel-Lock: sha1:p1Rt+GthRiJmAvzpVBDxQJPJ7nc= X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 195.159.176.226 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:218366 Archived-At: On Fri, 15 Sep 2017 08:32:16 -0400 Stefan Monnier wrote: SM> having a "security-patches" package might make sense. >> I would love to see that as well, especially if it was well tested in a >> CI system against various versions of Emacs. >> What needs to happen so the experience is seamless? SM> Step one is to create this package in elpa.git, putting the fix for the SM> enriched.el bug. A package is pretty easy but I have a few questions before putting that out: * how do we prevent accidental or malicious commits to this package? Could it maybe live in a special "GNU ELPA security updates" archive separate from elpa.git? * should it be signed+released in a special way? How do we test it? * what version of Emacs will begin to check for this package? * Can we do push notifications somehow or are we limited to polling? * should there be a special mailing list for internal discussions? * how do we make the experience seamless (on startup, during a long-running session, unattended, for a whole site)? In a related vein, I mentioned a while ago that it would be really nice to see the changes (from what's installed) to all the code in a package before upgrading it. I think for security updates that would be especially useful. Thanks Ted