Alerts Are Not Correctly Parsed or Saved

[mdaines-r7]

Alerts are not correctly parsed from site configurations when loading them from a Nexpose console. An attempt to save a site which contains an alert will fail to save with a 'name cannot be null' error.

The underlying XML is not correctly parsed or used.

Here is an example of the three kinds of alerts.

SMTP

<Alert name="Scan Completion e-mail" enabled="1" maxAlerts="1">
  <scanFilter scanStart="0" scanStop="1" scanFailed="0" scanResumed="0" scanPaused="0"/>
  <vulnFilter severityThreshold="1" confirmed="0" unconfirmed="0" potential="0"/>
  <smtpAlert sender="from@company.com" server="smtp.company.com" limitText="0">
    <recipient>to@company.com</recipient>
  </smtpAlert>
</Alert>

Syslog

<Alert name="syslog attempt" enabled="1" maxAlerts="1">
  <scanFilter scanStart="1" scanStop="0" scanFailed="0" scanResumed="0" scanPaused="0"/>
  <vulnFilter severityThreshold="1" confirmed="0" unconfirmed="1" potential="1"/>
  <syslogAlert server="syslog.company.com"/>
</Alert>      

SNMP

<Alert name="snmp" enabled="1" maxAlerts="2">
  <scanFilter scanStart="0" scanStop="0" scanFailed="0" scanResumed="0" scanPaused="1"/>
  <vulnFilter severityThreshold="8" confirmed="1" unconfirmed="0" potential="0"/>
  <snmpAlert community="communityname" server="managementserver"/>
</Alert>

[mdaines-r7]

0.1.14 of the gem should fix this issue.

Right now, the configuration just works off 0 and 1 for the booleans, which could be cleaned up in the future.