From: "Hanno Böck" <hanno@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Packages up for grabs: openvas
Date: Wed, 12 Dec 2018 13:09:48 +0100 [thread overview]
Message-ID: <20181212130948.6b5f3e88@computer> (raw)
Hi,
I practically haven't maintained openvas for quite a long time, yet
unfortunately am still listed as the maintainer. It's a security scanner
and a fork of nessus.
It needs version bumps, updated ebuilds are in bugzilla, but I don't
know if they're for the very latest version [1].
In my experience upstream changes things often and makes the usability
more complex with every new release while providing little value (I
mostly got false positives out of it in the past).
The following packages belong to it:
net-analyzer/openvas
net-analyzer/openvas-manager
net-analyzer/openvas-cli
net-analyzer/openvas-tools
net-analyzer/openvas-libraries
net-analyzer/openvas-scanner
net-analyzer/greenbone-security-assistant
net-analyzer/ospd
Feel free to take it and remove me, otherwise I'll remove myself soon
and make it "maintainer-needed".
[1] https://bugs.gentoo.org/590324
--
Hanno Böck
https://hboeck.de/
mail/jabber: hanno@hboeck.de
GPG: FE73757FA60E4E21B937579FA5880072BBB51E42
reply other threads:[~2018-12-12 12:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181212130948.6b5f3e88@computer \
--to=hanno@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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