If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

NESSUS 2.0.0 has been released

The focus of Nessus 2.0 was to clean up the code and greatly improve the speed of nessusd. As a result, the major changes are :

- Brand new NASL interpretor, totally re-written from scratch

- Extended the NASL language to support new operators and functions

- Smarter plugin scheduling algorithms, for better parallelism

- New ways to perform service detection - each plugin which positively
identifies a service registers it in the knowledge base. At the end
of the scan, services which have not been recognized are flagged and
appear in the report

- Greatly reduced memory usage

- Support for multiple CVE ids per plugin

- Support for Bugtraq IDs in the plugins

- New port scanner (synscan.nes) which computes the round trip time to
the remote host. As a result, scanning firewalled hosts is faster

- Slightly improved the HTML reporting

What is *not* new in Nessus 2.0
--------------------------------

We did not change the GUI, so if you expect shiny new buttons, they're not there. We prefered to focus on the engine for this release, the rest will
follow during the 2.1.x developement cycle.

MacOS X is supported, provided you installed the developer tools, Apple's X11
server and optionally GTK. Because of the very limited number of BPFs, you
may want to disable the 'ping host' plugin and use the tcp connect() port
scanner, as there is no easy way to increase those. Nessus includes a
workaround but we suggest you avoid using it at this time.

o Solaris

Be sure to use Bison 1.75 and gnu M4 when compiling Nessus

o IRIX

Packet capture does not work, so the 'ping host' plugin will always
return every host as being dead. Disable it, and use the tcp connect()
port scanner.

Thanks
------

I would like to thank everyone who took part to the developement process of Nessus 2.0, and in particular :