Re: Restore Sessions vs. Manage Reports on Server

On Mon, Nov 01, 2004 at 04:41:12PM +0100, Jan-Oliver Wagner wrote:
> On Mon, Nov 01, 2004 at 04:13:57PM +0100, Jan-Oliver Wagner wrote:
> > I am currently refactoring the "Restore/Delete Session" feature.
> > 
> > My idea was that actually this will be a "Manage Reports on Server"
> > feature where you have the options to import one to your local client
> > software or to delete one on the server side.
> > 
> > In the code I see that there is a lot handling of options and plugin
> > configuration just for restoring a session.
> > Shouldn't it be as simple as just retrieving the attack results
> > alone?
> > My preference would be to just load the results an not have even
> > the monitoring dialog running.
> > 
> > Would it be correct to follow this idea of just getting the result
> > data?
> 
> my first approach to this would be ignore nessus/attack.c:
> restore_attack() and instead call comm_restore_session() 
> directly from nessus/monitor_dialog.c:monitor_dialog_setup().
> Coarse test show that this seems to work.
> 
> However, the questions remains: what was the stuff in restore_attack()
> good for?

I further tried to understand the current concept of saving sessions.

The Nessus book says that it is in principle a feature to pick up
a scan that was interrrupted due to a (server) crash and continue where
it was stopped.

But as far as I read the code of the client, all the current paramters
are send to the server for this "restoring".
Unfortunately there is no guarantee that these are the same parameters
used to initially start the scan.
So, I get the feeling that the design of this feature is somehow broken.

I really need some discussion about this feature to improve the client!

Best

	Jan
-- 
Jan-Oliver Wagner               http://intevation.de/~jan/

Intevation GmbH                      http://intevation.de/
FreeGIS                                http://freegis.org/
_______________________________________________
Nessus-devel mailing list
[email protected]
http://mail.nessus.org/mailman/listinfo/nessus-devel