netdev - Dealing with bugzilla

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <20240919091046.64cb49b6@hermes.local>
Date: Thu, 19 Sep 2024 09:10:46 -0700
From: Stephen Hemminger <stephen@...workplumber.org>
To: netdev@...r.kernel.org
Subject: Dealing with bugzilla

Up until now, I have been the volunteer screener of networking related bugzilla bugs.
I would like to get out of doing that.

The alternatives are:
   1. Change the bugzilla forwarding to netdev@...r.kernel.org (ie no screening)
   2. Get a new volunteer to screen
   3. Make a new mailing list target on vger (ie netdev-bugs@...r.kernel.org)
   4. Find someone to make a bot to use get_maintainer somehow to forward
   5. Blackhole the bugzilla reports.
   6. Bounce all the bugzilla reports somehow.

Any suggestions welcome.