From: Troy Hinckley <comms@dabrev.com>
To: emacs-devel@gnu.org
Subject: Request to backport fix for CVE-2022-45939 to Emacs 28
Date: Mon, 13 Feb 2023 12:15:50 -0600 [thread overview]
Message-ID: <09998122-0110-454f-94d1-e29c37b833f4@Spark> (raw)
In-Reply-To: 85f35c42-cfe8-44a7-a9c1-307acc5c17d4@Spark
[-- Attachment #1: Type: text/plain, Size: 327 bytes --]
My company will not allow an install of Emacs 28 due to CVE-2022-45939. There is a patch for this in the master branch, but it did not make it in time for Emacs 28.2. We have many Emacs users who would like to upgrade to 28. What would be the effort to back port this fix and do an Emacs 28.3 release?
- Troy Hinckley
[-- Attachment #2: Type: text/html, Size: 821 bytes --]
next parent reply other threads:[~2023-02-13 18:15 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 ` Troy Hinckley [this message]
2023-02-13 20:47 ` Request to backport fix for CVE-2022-45939 to Emacs 28 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
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=09998122-0110-454f-94d1-e29c37b833f4@Spark \
--to=comms@dabrev.com \
--cc=emacs-devel@gnu.org \
/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).