From: "Francisco Blas Izquierdo Riera (klondike)" <klondike@gentoo.org>
To: "Michał Górny" <mgorny@gentoo.org>
Cc: Gentoo Development <gentoo-dev@lists.gentoo.org>
Subject: [gentoo-dev] Re: [gentoo-dev-announce] Last rites: net-analyzer/{libnasl/nessus*,prelude-nessus}, sec-policy/selinux-nessus
Date: Sat, 16 Mar 2019 20:09:59 +0100 [thread overview]
Message-ID: <0ee6f261-c0c2-1f9f-e717-4acb4f8ec94c@gentoo.org> (raw)
In-Reply-To: <c7525da90f301b6c0f22c9b9e032f6f6a2f547d0.camel@gentoo.org>
[-- Attachment #1.1: Type: text/plain, Size: 733 bytes --]
Hi Michał
El 16/3/19 a las 20:06, Michał Górny escribió:
> # The current Gentoo version of Nessus is from 2006 (!). It does
> # not build for quite some time (#590226), also -client fails with new
> # openssl (#674424). Upstream has stopped releasing non-proprietary
> # versions. While at it, remove prelude-nessus that practically
> # has not been touched since 2003.
> # Removal in 30 days. Bug #680636.
> net-analyzer/libnasl
> net-analyzer/nessus-client
> net-analyzer/nessus-core
> net-analyzer/nessus-libraries
> net-analyzer/nessus-plugins
> net-analyzer/prelude-nessus
> sec-policy/selinux-nessus
You should comment that users can migrate to net-analyzer/nessus-bin or
net-analyzer/openvas.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-03-16 19:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-16 19:06 [gentoo-dev] Last rites: net-analyzer/{libnasl/nessus*,prelude-nessus}, sec-policy/selinux-nessus Michał Górny
2019-03-16 19:09 ` Francisco Blas Izquierdo Riera (klondike) [this message]
[not found] ` <CAJ2V=1qnCAypsbBTn9iZYP4yD5DP768gLNssvmyfL6g9_JbRqA@mail.gmail.com>
2019-03-16 20:37 ` [gentoo-dev] Re: [gentoo-dev-announce] " Francisco Blas Izquierdo Riera (klondike)
2019-03-16 20:47 ` Michał Górny
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=0ee6f261-c0c2-1f9f-e717-4acb4f8ec94c@gentoo.org \
--to=klondike@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=mgorny@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