Mailing List Archive

On Tue Mar 22 2005 at 13:51, Paul Johnston wrote:

> This file produces errors like this, with Nessus 2.0.7:

Upgrade to Nessus 2.2

> I've replaces '\0' with chr(0) and that seems to work here. Perhaps
> this could be done to the mainline plugin?

No. Nessus 2.0 is dead.

On Tue, Mar 22, 2005 at 02:21:32PM +0100, Michel Arboi wrote:
> > I've replaces '\0' with chr(0) and that seems to work here. Perhaps
> > this could be done to the mainline plugin?
>
> No. Nessus 2.0 is dead.

Strictly speaking, Nessus 2.0.12 is maintained until the end of this
month. After that, we don't make any garantee on wether new plugins will
be parsed properly or not.

smb_func.inc has been tested with 2.0.12 with no problem.


-- Renaud

On Mar 22, 2005, at 7:48 AM, Renaud Deraison wrote:
> On Tue, Mar 22, 2005 at 02:21:32PM +0100, Michel Arboi wrote:
>>> I've replaces '\0' with chr(0) and that seems to work here. Perhaps
>>> this could be done to the mainline plugin?
>>
>> No. Nessus 2.0 is dead.
>
> Strictly speaking, Nessus 2.0.12 is maintained until the end of this
> month. After that, we don't make any garantee on wether new plugins
> will
> be parsed properly or not.

Is there a list of improvements of 2.2 over 2.0? I know I can go
through the change logs, but if it is already listed it would make my
life easier. Justification for management for upgrading something that
works.

Thanks

On Tue, Mar 22, 2005 at 03:20:30PM -0600, MadHat wrote:
> Is there a list of improvements of 2.2 over 2.0? I know I can go
> through the change logs, but if it is already listed it would make my
> life easier. Justification for management for upgrading something that
> works.

In a nutshell :

- Better KB management (KB items are stored in a hash table instead of
a linked list, arbitrary amounts of data can be stored instead of 65k
per item) ;

- Better inter-process communication (Nessus communicates with itself in
a much more robust way. In 2.0.x IPC was CPU intensive and had no
robust delivery mecanism) ;

- Built-in crypto functions which make possible the implementation of
SSH in NASL ;

- Changes in the NASL syntax : more functions and a change in the way
functions handle anonymous arguments have been introduced in 2.2.x.
When we start using this syntax for some scripts, they won't work
with 2.0.x ;

- Support for signed NASL checks which can execute local commands and
are used in lieu of all the .nes plugins ;

- Reduced CPU usage in the scheduler (2.2.4 only) ;


Finally, the killer argument is :

- 2.2.x is maintained, whereas 2.0.x is not. There are subtle bugs
in the 2.x SSL code which may cause incomplete reads and as a result
may produce false negatives, and it won't be fixed in 2.0.x.



-- Renaud