Everything went as planned and the scanned seems to have completed normally. So thanks for the help! I never did get down and dirty in the nessus logs as the other post suggested since this fix was easier to try and seems to have worked. I'll post more if needed.
I realize you guys are busy, but please try to keep some more details in the release notes about things like this. It caused a couple weeks of grief and concern while I had to stop work and trouble shoot why an upgrade broke my scanner.
P.S. in another thread about upgades, I support keeping older copies on hand just for this reason, I will keep my downloads even if you do not. But I wouldn't expect you to be supporting them too much other than maintaining the list you do now for historical Q&A's.
Again thanks for the help, and a great service to the open source community.
As a matter of fact I am the same session since last Oct, 2004. As NessusWx has changed I just >keep using the same database. I'll try this and post the results.
Are you using a session configuration from NessusWX 1.4.4 ?
Since 1.4.4b session config file changed. Sorry about that but it was the only way to remove a >critical bug in NessusWX.
I forget to include a session file conversion tool in NessusWX 1.4.4b (and later) to convert session >files to the new format.
I suggest you to recreate full new sessions under NessusWX 1.4.5b.
Regards,
Nicolas
_______________________________________________ Nessus mailing list [email protected] http://mail.nessus.org/mailman/listinfo/nessus
