NessusWC is a novel web-based client designed to function as an interface to a Nessus Daemon. Developed from the ground up, it enables users to access Nessus Daemon from a web browser.
NessusWC is a recently developed client that functions as a web frontend for Nessus Daemon, a security vulnerability scanner that is available for free. The key design goal of the Nessus Client software was to enable it to be compiled and installed independently of Nessus. The software package features a web interface that exclusively depends on CGI technology while striving for simplicity and robustness.
To ensure seamless installation, NessusWC requires the presence of key libraries, including Nessus, OpenSSL, libcgi, and headers. Setting up the software is quite easy but requires careful configuration of the necessary files such as the Makefiles in the root, and src/directories. Users can configure their URL location and default Nessus login parameters by checking the nessuswc.h file in the src/ directory.
To compile the NessusWC package, users must have OpenSSL libraries as well as libcgic from boutell.com. Common compilation issues arise from failing to install OpenSSL or libgcgic libraries in a nonstandard path or not running the appropriate functions such as ldconfig. However, users can avoid these problems by setting explicit paths to the libs and includes in the Makefile.
Users must also add the CGI path to the webserver configuration to facilitate installation. For Apache 1.3, this involves adding a line that matches the server configuration files. After compiling and installing the NessusWC package, users can create a user on the Nessus server by using the nessus-home/bin/nessus-mkcert-client option. They should then copy the client certificate to the NessusWC-home/etc directory and make it readable to the webserver. Besides, users will need to create a results directory that the webserver can write to.
The latest version of NessusWC features several improvements, including proper error handling if the plugin list exhausts the maximum number of plugins defined in NessusWC. Additionally, default MAXPLUGS value was raised from 20000 to 40000, ensuring that the software can handle a growing number of plugins.
To ensure seamless installation, NessusWC requires the presence of key libraries, including Nessus, OpenSSL, libcgi, and headers. Setting up the software is quite easy but requires careful configuration of the necessary files such as the Makefiles in the root, and src/directories. Users can configure their URL location and default Nessus login parameters by checking the nessuswc.h file in the src/ directory.
To compile the NessusWC package, users must have OpenSSL libraries as well as libcgic from boutell.com. Common compilation issues arise from failing to install OpenSSL or libgcgic libraries in a nonstandard path or not running the appropriate functions such as ldconfig. However, users can avoid these problems by setting explicit paths to the libs and includes in the Makefile.
Users must also add the CGI path to the webserver configuration to facilitate installation. For Apache 1.3, this involves adding a line that matches the server configuration files. After compiling and installing the NessusWC package, users can create a user on the Nessus server by using the nessus-home/bin/nessus-mkcert-client option. They should then copy the client certificate to the NessusWC-home/etc directory and make it readable to the webserver. Besides, users will need to create a results directory that the webserver can write to.
The latest version of NessusWC features several improvements, including proper error handling if the plugin list exhausts the maximum number of plugins defined in NessusWC. Additionally, default MAXPLUGS value was raised from 20000 to 40000, ensuring that the software can handle a growing number of plugins.
What's New
Version 1.2.2: N/A