From: Anders Munch <ajm@flonidan.dk>
To: help-gnu-emacs <help-gnu-emacs@gnu.org>
Subject: RE: Need information regarding Emacs application
Date: Mon, 12 Feb 2024 10:35:46 +0000 [thread overview]
Message-ID: <VI1PR05MB10680F88110AA0FCB83977F78B4482@VI1PR05MB10680.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <ZcdQilIQjLOmcriA@lco.syogm.com>
Jean Louis <bugs@gnu.support> wrote:
> When I keep reading those CVE reports, the more I read, the more it looks like it only serves some business purposes, not the real security.
CVEs vary in quality. Even for the good CVEs, severity levels tend to be way inflated.
But when a for real serious vuln does occur, it will also end up on the CVE list. So it's still a good thing to follow.
Srinivasan wanted to know how to be notified of future issues. Subscribing to notifications about GNU Emacs on opencve.io is a way to do that.
regards, Anders
prev parent reply other threads:[~2024-02-12 10:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-09 8:51 Need information regarding Emacs application Srinivasan Santhanam via Users list for the GNU Emacs text editor
2024-02-09 15:12 ` Anders Munch
2024-02-10 10:31 ` Jean Louis
2024-02-10 11:07 ` Thibaut Verron
2024-02-12 10:35 ` Anders Munch [this message]
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=VI1PR05MB10680F88110AA0FCB83977F78B4482@VI1PR05MB10680.eurprd05.prod.outlook.com \
--to=ajm@flonidan.dk \
--cc=help-gnu-emacs@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.
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).