[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAH0iFcZaZtAfhVwopR1vFgXuQJSvugL8Bz8OmQYS+kpq4VqGiA@mail.gmail.com>
Date: Wed, 3 Apr 2024 14:01:11 -0400
From: Michael Dawson <midawson@...hat.com>
To: Solar Designer <solar@...nwall.com>
Cc: oss-security@...ts.openwall.com
Subject: Re: Fwd: Node.js security update for all active
release lines
Sorry I don't remember the context as to why we agreed to send this forward
in the first place.
As opposed to expanding any work that's a one off for the community
security stewards, since it sounds like it may not be meeting your needs,
I'd propose that we just remove it from our security release steps and you
can subscribe to the nodejs-sec mailing list like everybody else. From that
you could generate some automation to pull down the content from the
original post.
On Wed, Apr 3, 2024 at 12:55 PM Solar Designer <solar@...nwall.com> wrote:
> On Wed, Apr 03, 2024 at 08:12:24AM -0700, midawson wrote:
> > The planned security releases are now available. You can read more about
> > the details in -
> > https://nodejs.org/en/blog/vulnerability/april-2024-security-releases/
>
> Thank you for bringing these to oss-security. Going forward, it'd be
> great if you post the actual detail - not only a title+link.
>
> I'm attaching to this message the Markdown content of the above blog
> post, as taken from
>
> https://github.com/nodejs/nodejs.org/blob/main/pages/en/blog/vulnerability/april-2024-security-releases.md
>
> Alexander
>
Powered by blists - more mailing lists
Please check out the
Open Source Software Security Wiki, which is counterpart to this
mailing list.
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
