[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <5d44b6375dde695754f2603faaf6b4f30a76b9f6.camel@bzed.de>
Date: Sat, 09 Mar 2024 23:38:13 +0100
From: Bernd Zeimetz <bernd@...d.de>
To: oss-security@...ts.openwall.com
Subject: Re: help wanted - bring more issues in here
On Thu, 2024-03-07 at 17:17 -0800, Alan Coopersmith wrote:
>
> I also notice far more than I can send on myself, so tend to filter
> both
> for those projects that are more likely to be distributed directly by
> distros and more widely installed on systems, and for issues that
> seem
> to have a higher level of impact. So I'm not sending on notice of
> every
> bug in every WordPress plugin, nor every npm module.
imho: For such things and "random" relevant findings it might make
sense to have some simple feed of affected program/thing, short
description and url(s), maybe as simple table and rss feed? adding new
lines from the cli with a post request is all I need I guess. So the
info doesn't get lost, but it also doesn't make a chaos on the list.
--
Bernd Zeimetz Debian GNU/Linux Developer
http://bzed.de http://www.debian.org
GPG Fingerprint: ECA1 E3F2 8E11 2432 D485 DD95 EB36 171A 6FF9 435F
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.
