|
From: | GNU bug Tracking System |
Subject: | bug#61858: closed (Undisclosed vulnerability) |
Date: | Mon, 04 Sep 2023 21:14:02 +0000 |
Your message dated Mon, 4 Sep 2023 14:13:24 -0700 with message-id <CADwFkmkuL5MLT32v9HSNLMH7zCstPF5cfS15C_LZvLATuzbL+A@mail.gmail.com> and subject line Re: bug#61858: Undisclosed vulnerability has caused the debbugs.gnu.org bug report #61858, regarding Undisclosed vulnerability to be marked as done. (If you believe you have received this mail in error, please contact help-debbugs@gnu.org.) -- 61858: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=61858 GNU Bug Tracking System Contact help-debbugs@gnu.org with problems
--- Begin Message ---Subject: Undisclosed vulnerability Date: Mon, 27 Feb 2023 22:39:24 +0100 User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.8.0 Hi,What is the proper channel for reporting a security vulnerability related to emacs?Regards, Gabriel CoronaOpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---Subject: Re: bug#61858: Undisclosed vulnerability Date: Mon, 4 Sep 2023 14:13:24 -0700 Gabriel Corona <gabriel.corona@free.fr> writes: > What is the proper channel for reporting a security vulnerability related to > emacs? I'm not sure if it's still relevant, but you can email me and eliz@gnu.org. Closing the bug for now, thanks.
--- End Message ---
[Prev in Thread] | Current Thread | [Next in Thread] |