NSCP

fixed: Workaround is back in 0.4.2.94. Will add and rebuild 0.4.3 as well in the next few days. Michael Medin

Merged back ignore perf flag from 0.4.1

In version 0.3.x, when running an unattended install you could exclude the firewall exception by doing the following: msiexec /i <<<MSI FILE>>> /quiet /norestart ADDLOCAL=ALL REMOVE="FireWallException" However in version 0.4.1 ... [More] this feature setting seems to have been removed. Running the following with logging turned on: msiexec /i NSCP-0.4.1.105-x64.msi /quiet /norestart /L*V nscp.log ADDLOCAL=ALL REMOVE="FireWallException" ...results in the following being logged in the nscp.log MSI log file and the install fails: DEBUG: Error 2711: The specified Feature name ('FireWallException') not found in Feature Table. MSI (s) (28:A4) [09:55:27:735]: Product: NSClient++ (x64) -- The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2711. The arguments are: FireWallException, , The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2711. The arguments are: FireWallException, , I then checked the Feature table using InstEd? and indeed this "feature" is missing. Here's the 0.3.9 MSI feature table: And this is the 0.4.1 MSI feature table, as you can see the FireWallException? feature is missing: I can work around this by deleting the "NSClient++ Monitoring Agent" firewall exception rule after the installer has completed, but it would be nice to have this installer feature put back in again. Thanks. [Less]

untested attempt at ubunto fixes (vagrant box)

Added insecure option to NRPE to disable certificate Fixed some minor tweaks to build without openssl

Added favicons to the webui

Fixed some bugs in the settings handling Improved the settings UI (WEB) a bit

Fixed bug in registry settings (accidental throw)

wontfix: I have looked into to this and can report that nsca use mcrypt and RIJNDAEL-256 which is NOT AES 256 (which NSClient++ use). RIJANDAEL is a generic algorithm which can be configured with multiple blocksizes and keysizes. But the only NIST ... [More] approved ones are all 128 bit block size where as the one NSCA use is a 256 bit block size (i.e. NOT AES and NOT NIST approved). I will most likely not add support for RIJNDAEL-256 since AES is (in my humble opinion) a better option but more importantly cryptopp which I use does not seem to support non AES version of RIJNDAEL. I think a better option would be to use NSClient++ as NSCA server on linux and use proper AES 256. Please let me know if this is a bad idea and if so why. Source: ​http://en.wikipedia.org/wiki/Advanced_Encryption_Standard For AES, NIST selected three members of the Rijndael family, each with a block size of 128 bits, but three different key lengths: 128, 192 and 256 bits. [Less]

Fixed some js issues for the log view