Hi,
we are currently intensively testing the 2.3.0 version
(mostly current CVS) and we faced a serious problem
that unfortunately appears very hard to track.
Using 2.3.0 or current CVS using only Local Security
Checks plugin (ie. only uname -a) does only occasionally work.
Whether it works or not seems to change with using
different servers that have different plugin sets.
We even observed that, when using many plugins, only
a portion of it is really executed (no error messages).
Debugging is difficult, but it seems that the SSH access
sometimes really happens but the results don't make it
back to Nessus Server. Sometime even SSH access did
not happen and, alas, sometimes everything works.
If someone of you is interested in helping us to track
down the problem it would be most helpful for us
if you try to reproduce the problem.
For this, basically you need to:
- install everything from CVS into a new location
(with a new Nessuse Server users and a new Cert)
- use a new user for Nessus GTK Client
- Create and place the SSH certificate properly
- Select only "Local Security Checks" plugin
and switch on dependencies consideration.
- Enter the SSH properties in the Plugin Prefs.
- Run the test multiple times.
If you just have a idea where we might have to look for in
the code this would be equally welcome.
One of our suspects is the hashing. We'll remove it and see
if it works better.
Best
Jan
--
Jan-Oliver Wagner http://intevation.de/~jan/
Intevation GmbH http://intevation.de/
we are currently intensively testing the 2.3.0 version
(mostly current CVS) and we faced a serious problem
that unfortunately appears very hard to track.
Using 2.3.0 or current CVS using only Local Security
Checks plugin (ie. only uname -a) does only occasionally work.
Whether it works or not seems to change with using
different servers that have different plugin sets.
We even observed that, when using many plugins, only
a portion of it is really executed (no error messages).
Debugging is difficult, but it seems that the SSH access
sometimes really happens but the results don't make it
back to Nessus Server. Sometime even SSH access did
not happen and, alas, sometimes everything works.
If someone of you is interested in helping us to track
down the problem it would be most helpful for us
if you try to reproduce the problem.
For this, basically you need to:
- install everything from CVS into a new location
(with a new Nessuse Server users and a new Cert)
- use a new user for Nessus GTK Client
- Create and place the SSH certificate properly
- Select only "Local Security Checks" plugin
and switch on dependencies consideration.
- Enter the SSH properties in the Plugin Prefs.
- Run the test multiple times.
If you just have a idea where we might have to look for in
the code this would be equally welcome.
One of our suspects is the hashing. We'll remove it and see
if it works better.
Best
Jan
--
Jan-Oliver Wagner http://intevation.de/~jan/
Intevation GmbH http://intevation.de/