I am trying to create two sessions within nessuswx (1.4.5d) to connect to two separate, remote scanners (3.0.5), authenticating using client certificates. I wish to use session-specific connection information for each session (so that I can schedule the scans using nessusWX command-line options), but I'm having problems in that nessuswx ignores the session-specific certificate setting and instead, 'remembers' the last certificate specified for the console connection (Communications - Connect etc). Is this by design, or is it a bug? The nessus scanners are running on SLES9, but I'm inclined to think that this is an issue specific to the nessusWX executable. Any help appreciated. Regards Prys
_______________________________________________ Nessus mailing list [email protected] http://mail.nessus.org/mailman/listinfo/nessus
