Mailing List Archive

Michael,
What do you mean by funky? Have you had problems with nmap OS ID?

-Tony

-----Original Message-----
From: owner-nessus-devel@list.nessus.org
[mailto:owner-nessus-devel@list.nessus.org]On Behalf Of Michael
Scheidell
Sent: Monday, February 24, 2003 11:32 AM
To: nessus-devel@list.nessus.org
Subject: Folloeing 1.3.4?


I just got happy with 1.3.4 and was planning on following that branch for
a while, and just noticed it got called 2.0.

I also noticed that there looks like no CVS for 1.3.x?

queso was removed and replaced with an nmap 3.0 style plugin, and a assume
that will get 'funky' every once and a while.

Is there any way to follow 1.3.4 with bugfixes or are we 'bleeders' going
to be following 2.0?

--
Michael Scheidell, CEO
SECNAP Network Security, LLC
Sales: 866-SECNAPNET / (1-866-732-6276)
Main: 561-368-9561 / www.secnap.net
Looking for a career in Internet security?
http://www.secnap.net/employment/

On Mon, Feb 24, 2003 at 11:32:07AM -0500, Michael Scheidell wrote:
> I just got happy with 1.3.4 and was planning on following that branch for
> a while, and just noticed it got called 2.0.

Yes. Nessus 2.0.0 will be released later on today.

> I also noticed that there looks like no CVS for 1.3.x?

The 1.3.x branch was considered unstable (odd number). Now that we
consider it "stable" we renamed it 2.0.0 (that should have been 1.4.x,
but given the amount of code changed, it would make no sense to keep the
same major version).

> queso was removed and replaced with an nmap 3.0 style plugin, and a assume
> that will get 'funky' every once and a while.

No it won't. It will be stable. When the 2.0.x tree will be considered
"stable enough" by everyone then I'll open the branch NESSUS_2_0, as I
did for NESSUS_1_2, and we'll move onto the developement of Nessus 2.2.x
(very soon hopefully - 2.0.x is the first 90% of a major cleanup the
daemon part badly needed, but I still want to clean the remaining 10%
and to start tackling the GUI).

> Is there any way to follow 1.3.4 with bugfixes or are we 'bleeders' going
> to be following 2.0?

The next "bleeding edge" will be named 2.1.x.


-- Renaud