From: lux <lx@shellcodes.org>
To: Lynn Winebarger <owinebar@gmail.com>, Troy Hinckley <comms@dabrev.com>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: Request to backport fix for CVE-2022-45939 to Emacs 28
Date: Fri, 17 Feb 2023 10:35:43 +0800 [thread overview]
Message-ID: <tencent_98A7C14C7A4D650DC75D823C72B872F03506@qq.com> (raw)
In-Reply-To: <CAM=F=bDa1hqmoSzFdZ1wR2Zewx_HfFKtzgk+gNf-yEYZsV935g@mail.gmail.com>
On Thu, 2023-02-16 at 20:44 -0500, Lynn Winebarger wrote:
> On Tue, Feb 14, 2023 at 12:06 PM Troy Hinckley <comms@dabrev.com>
> wrote:
> >
> > If the commit was cherry picked to the emacs-28 branch, does that
> > mean it’s just unreleased changes for Emacs 28? We are building
> > from source, so that might be enough. I didn’t realize cutting a
> > release was high effort.
>
> FWIW, I suspect a lot of users get automated updates from their
> packager of choice, whether it's linux distro, Cygwin, MSYS2, or
> whatever. If you look at their source packages, they routinely apply
> these kinds of changes as updates to older releases. Even if you
> don't use that packager, you can still use their source package for
> Emacs to get a version with the relevant security patches.
Most Linux distributions rely on public CVE information for security
updates, I fixed 4 vulnerabilities[1], but to date, only one
vulnerability has been assigned a CVE number (CVE-2022-45939), so most
Linux distributions have not fixed the other three vulnerabilities.
Depending on the distro security updates are only available for Linux,
BSD etc, while Windows users cannot update automatically.
[1] patches:
-
https://git.savannah.gnu.org/cgit/emacs.git/commit/?id=d48bb4874bc6cd3e69c7a15fc3c91cc141025c51
-
https://git.savannah.gnu.org/cgit/emacs.git/commit/?id=01a4035c869b91c153af9a9132c87adb7669ea1c
-
https://git.savannah.gnu.org/cgit/emacs.git/commit/?id=9a3b08061feea14d6f37685ca1ab8801758bfd1c
-
https://git.savannah.gnu.org/cgit/emacs.git/commit/?id=1b4dc4691c1f87fc970fbe568b43869a15ad0d4c
next prev parent reply other threads:[~2023-02-17 2:35 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <85f35c42-cfe8-44a7-a9c1-307acc5c17d4@Spark>
2023-02-13 18:15 ` Request to backport fix for CVE-2022-45939 to Emacs 28 Troy Hinckley
2023-02-13 20:47 ` Eli Zaretskii
2023-02-14 5:07 ` lux
2023-02-14 13:19 ` Eli Zaretskii
2023-02-14 16:09 ` Troy Hinckley
2023-02-14 17:04 ` Eli Zaretskii
2023-02-17 1:44 ` Lynn Winebarger
2023-02-17 2:35 ` lux [this message]
2023-02-14 20:10 ` Tim Cross
2023-02-15 8:32 ` Robert Pluim
2023-02-18 4:19 ` Richard Stallman
2023-02-15 12:28 ` Eli Zaretskii
2023-02-16 17:50 ` Richard Stallman
2023-02-16 20:02 ` Eli Zaretskii
2023-02-16 20:41 ` Jim Porter
2023-02-16 20:52 ` Eli Zaretskii
2023-02-17 10:26 ` Stefan Kangas
2023-02-17 10:38 ` Robert Pluim
2023-02-17 12:33 ` Eli Zaretskii
2023-02-17 14:01 ` Stefan Kangas
2023-02-17 17:37 ` lux
2023-02-18 6:54 ` lux
2023-02-19 20:33 ` Corwin Brust
2023-02-21 14:54 ` Michael Albinus
2023-02-19 4:47 ` Richard Stallman
2023-02-19 7:05 ` Eli Zaretskii
2023-02-14 8:13 ` Robert Pluim
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=tencent_98A7C14C7A4D650DC75D823C72B872F03506@qq.com \
--to=lx@shellcodes.org \
--cc=comms@dabrev.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=owinebar@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).