OpenVAS - Revision history

Paul Blankenbaker: Verified that instructions work on NST 30

2019-07-19T10:28:44Z

Verified that instructions work on NST 30

← Older revision		Revision as of 06:28, 19 July 2019
Line 21:		Line 21:
	# Run Task.		# Run Task.

	= '''NST 26 and NST 28 Setup''' =		= '''NST 30, NST 28 and NST 26 Setup''' =

	Getting OpenVAS (http://openvas.org) and Greenbone (https://www.greenbone.net/) set up and working on a NST 26 or Fedora 26 based system is a non-trivial task and involves some time (plan on 60 minutes). While the instructions below are based on a successful set up, due to the dynamic nature of all the packages and systems involved adjustments may need to be made in the future. Repeated use of the ''openvas-check-setup'' tool is highly recommended as you set up your system as it will not only indicate what is wrong, but will also provide useful instructions on what to do next to correct the issue.		Getting OpenVAS (http://openvas.org) and Greenbone (https://www.greenbone.net/) set up and working on a NST 26 or Fedora 26 based system is a non-trivial task and involves some time (plan on 60 minutes). While the instructions below are based on a successful set up, due to the dynamic nature of all the packages and systems involved adjustments may need to be made in the future. Repeated use of the ''openvas-check-setup'' tool is highly recommended as you set up your system as it will not only indicate what is wrong, but will also provide useful instructions on what to do next to correct the issue.

Paul Blankenbaker at 14:54, 27 May 2018

2018-05-27T14:54:51Z

@@ Line 95: / Line 95: @@
   systemctl start openvas-scanner.service
   systemctl enable openvas-scanner.service # To enable at boot
-  # Wait for CPU to settle, eventually the following message should go
+  # NOTE: It takes a LONG TIME for the openvas-scanner.service to start
-  # away from the openvas-check-setup - may take a long time:
+ # up the first time dues to loading of a large number of NVTs.
   openvas-check-setup --v9

Paul Blankenbaker at 15:11, 8 May 2018

2018-05-08T15:11:10Z

← Older revision		Revision as of 11:11, 8 May 2018
Line 21:		Line 21:
	# Run Task.		# Run Task.

	= '''NST 26 Setup''' =		= '''NST 26 and NST 28 Setup''' =

	Getting OpenVAS (http://openvas.org) and Greenbone (https://www.greenbone.net/) set up and working on a NST 26 or Fedora 26 based system is a non-trivial task and involves some time (plan on 60 minutes). While the instructions below are based on a successful set up, due to the dynamic nature of all the packages and systems involved adjustments may need to be made in the future. Repeated use of the ''openvas-check-setup'' tool is highly recommended as you set up your system as it will not only indicate what is wrong, but will also provide useful instructions on what to do next to correct the issue.		Getting OpenVAS (http://openvas.org) and Greenbone (https://www.greenbone.net/) set up and working on a NST 26 or Fedora 26 based system is a non-trivial task and involves some time (plan on 60 minutes). While the instructions below are based on a successful set up, due to the dynamic nature of all the packages and systems involved adjustments may need to be made in the future. Repeated use of the ''openvas-check-setup'' tool is highly recommended as you set up your system as it will not only indicate what is wrong, but will also provide useful instructions on what to do next to correct the issue.
Line 65:		Line 65:
	GNUTLSSTRING=--gnutls-priorities=SECURE128:-AES-128-CBC:-CAMELLIA-128-CBC:-VERS-SSL3.0:-VERS-TLS1.0		GNUTLSSTRING=--gnutls-priorities=SECURE128:-AES-128-CBC:-CAMELLIA-128-CBC:-VERS-SSL3.0:-VERS-TLS1.0

	Add a symlink so that the manager will be able to find certificates when accepting connections on port 9390:		Add a symlink so that the manager will be able to find certificates when accepting connections on port 9390 (you only need to do this if the symbolic link is missing):

	ln -s /var/lib/openvas /etc/pki		ln -s /var/lib/openvas /etc/pki

Paul Blankenbaker: /* Installation and Setup */

2018-02-28T15:09:02Z

Installation and Setup

← Older revision		Revision as of 11:09, 28 February 2018
Line 28:		Line 28:
	== Installation and Setup ==		== Installation and Setup ==

	NOTE: After NST 26 was release, the openvas packages were updated to version 9. The steps below assume that unix sockets (not TCP connections) will be ~~used to communicate~~ between the scanner (openvas-scanner service), manager (openvas-manager) and web interface (gsa-service). The ~~only~~ TCP port open should be 9443 after setup for the web interface. In order to accomplish this you will need to edit (comment) several lines in the /etc/sysconfig/openvas-* files.		NOTE: After NST 26 was release, the openvas packages were updated to version 9. The steps below assume that unix sockets (not TCP connections) will be preferred when communicating between the scanner (openvas-scanner service), manager (openvas-manager) and web interface (gsa-service). The main TCP port open should be 9443 after setup for the web interface. In order to accomplish this you will need to edit (comment) several lines in the /etc/sysconfig/openvas-* files.

	Log into a terminal as ''root'' and make sure the following packages are installed (alien, nsis and texlive-collection-latexextra are optional, but you will be missing some functionality if you do not include them):		Log into a terminal as ''root'' and make sure the following packages are installed (alien, nsis and texlive-collection-latexextra are optional, but you will be missing some functionality if you do not include them):
Line 34:		Line 34:
	dnf install openvas-libraries openvas-scanner openvas-manager openvas-cli openvas-gsa gnutls-utils redis alien nsis texlive-collection-latexextra		dnf install openvas-libraries openvas-scanner openvas-manager openvas-cli openvas-gsa gnutls-utils redis alien nsis texlive-collection-latexextra

	Edit the file /etc/sysconfig/openvas-manager and comment out the TCP connection to the scanner ~~and TCP listen configuration~~ so that unix sockets are used by ~~default~~:		Edit the file /etc/sysconfig/openvas-manager and comment out the TCP connection to the scanner so that unix sockets are used by the manager when talking to the scanner:

	#Manager listens on given address - by default manager listens on all addresses		#Manager listens on given address - by default manager listens on all addresses
	#MANAGER_LISTEN=--listen=127.0.0.1		MANAGER_LISTEN=--listen=127.0.0.1

	#Manager listens on given port - by default 9390		#Manager listens on given port - by default 9390
	#MANAGER_PORT=--port=9390		MANAGER_PORT=--port=9390

	#Contact scanner on given address		#Contact scanner on given address
Line 48:		Line 48:
	#SCANNER_PORT=--scanner-port=9391		#SCANNER_PORT=--scanner-port=9391

	Edit the file /etc/sysconfig/openvas-gsa and ~~comment out the TCP connection~~ to the ~~manager so that unix sockets are used by default~~:		Edit the file /etc/sysconfig/openvas-gsa and make sure it looks similar to the following:

			#GSA listens on given address - by default GSA listens on all addresses
			#GSA_LISTEN=--listen=127.0.0.1

			#GSA listens on given port - by default 443
			GSA_PORT=--port=9443

	#Contact manager on given address		#Contact manager on given address
	#MANAGER_LISTEN=--mlisten=127.0.0.1		MANAGER_LISTEN=--mlisten=127.0.0.1

	#Manager listens on given port - by default 9390		#Manager listens on given port - by default 9390
	#MANAGER_PORT=--mport=9390		MANAGER_PORT=--mport=9390

			#GNUTLSSTRING
			GNUTLSSTRING=--gnutls-priorities=SECURE128:-AES-128-CBC:-CAMELLIA-128-CBC:-VERS-SSL3.0:-VERS-TLS1.0

			Add a symlink so that the manager will be able to find certificates when accepting connections on port 9390:

			ln -s /var/lib/openvas /etc/pki

	Use the openvas-check-setup command as a diagnostic and guide during the installation process. We will be running this command a lot and it will report an ERROR until we complete the setup!		Use the openvas-check-setup command as a diagnostic and guide during the installation process. We will be running this command a lot and it will report an ERROR until we complete the setup!

Paul Blankenbaker: /* Accessing OpenVAS on an NST Probe */

2018-02-28T14:58:17Z

Accessing OpenVAS on an NST Probe

← Older revision		Revision as of 10:58, 28 February 2018
Line 122:		Line 122:

	You should be able to log in as ''admin'' using the initially generated password. After logging in, select ''User'' under the ''Administration'' menu and update your password (if desired).		You should be able to log in as ''admin'' using the initially generated password. After logging in, select ''User'' under the ''Administration'' menu and update your password (if desired).

	~~From the main page, you can perform a quick scan on the NST system itself by entering the IPv4 address of your NST system and pressing the ''Start Scan'' button:~~

	~~[[Image:openvas-quickscan.png]]~~

	When the scan completes it should only include informational entries in the vulnerability report (Log issues describing things discovered that are not necessarily vulnerabilities). Also, if you scan ''127.0.0.1'' instead of the IPv4 address associated with your network interface, you may find more issues.

	You should also be able to verify that the OpenVAS Command Line Interface (CLI) by running:		You should also be able to verify that the OpenVAS Command Line Interface (CLI) by running:

Paul Blankenbaker at 14:40, 28 February 2018

2018-02-28T14:40:06Z

← Older revision		Revision as of 10:40, 28 February 2018
Line 24:		Line 24:

	Getting OpenVAS (http://openvas.org) and Greenbone (https://www.greenbone.net/) set up and working on a NST 26 or Fedora 26 based system is a non-trivial task and involves some time (plan on 60 minutes). While the instructions below are based on a successful set up, due to the dynamic nature of all the packages and systems involved adjustments may need to be made in the future. Repeated use of the ''openvas-check-setup'' tool is highly recommended as you set up your system as it will not only indicate what is wrong, but will also provide useful instructions on what to do next to correct the issue.		Getting OpenVAS (http://openvas.org) and Greenbone (https://www.greenbone.net/) set up and working on a NST 26 or Fedora 26 based system is a non-trivial task and involves some time (plan on 60 minutes). While the instructions below are based on a successful set up, due to the dynamic nature of all the packages and systems involved adjustments may need to be made in the future. Repeated use of the ''openvas-check-setup'' tool is highly recommended as you set up your system as it will not only indicate what is wrong, but will also provide useful instructions on what to do next to correct the issue.


	== Installation and Setup ==		== Installation and Setup ==

			NOTE: After NST 26 was release, the openvas packages were updated to version 9. The steps below assume that unix sockets (not TCP connections) will be used to communicate between the scanner (openvas-scanner service), manager (openvas-manager) and web interface (gsa-service). The only TCP port open should be 9443 after setup for the web interface. In order to accomplish this you will need to edit (comment) several lines in the /etc/sysconfig/openvas-* files.

	Log into a terminal as ''root'' and make sure the following packages are installed (alien, nsis and texlive-collection-latexextra are optional, but you will be missing some functionality if you do not include them):		Log into a terminal as ''root'' and make sure the following packages are installed (alien, nsis and texlive-collection-latexextra are optional, but you will be missing some functionality if you do not include them):

	dnf install openvas-libraries openvas-scanner openvas-manager openvas-cli openvas-gsa gnutls-utils redis alien nsis texlive-collection-latexextra		dnf install openvas-libraries openvas-scanner openvas-manager openvas-cli openvas-gsa gnutls-utils redis alien nsis texlive-collection-latexextra

			Edit the file /etc/sysconfig/openvas-manager and comment out the TCP connection to the scanner and TCP listen configuration so that unix sockets are used by default:

			#Manager listens on given address - by default manager listens on all addresses
			#MANAGER_LISTEN=--listen=127.0.0.1

			#Manager listens on given port - by default 9390
			#MANAGER_PORT=--port=9390

			#Contact scanner on given address
			#SCANNER_LISTEN=--scanner-host=127.0.0.1

			#Scanner listens on given port - by default 9391
			#SCANNER_PORT=--scanner-port=9391

			Edit the file /etc/sysconfig/openvas-gsa and comment out the TCP connection to the manager so that unix sockets are used by default:

			#Contact manager on given address
			#MANAGER_LISTEN=--mlisten=127.0.0.1

			#Manager listens on given port - by default 9390
			#MANAGER_PORT=--mport=9390

	Use the openvas-check-setup command as a diagnostic and guide during the installation process. We will be running this command a lot and it will report an ERROR until we complete the setup!		Use the openvas-check-setup command as a diagnostic and guide during the installation process. We will be running this command a lot and it will report an ERROR until we complete the setup!
Line 43:		Line 68:

	systemctl restart redis.service		systemctl restart redis.service
	systemctl enable redis.service		systemctl enable redis.service # To enable at boot
	openvas-check-setup --v9		openvas-check-setup --v9

	Update the security checks using the ''greenbone~~-nvt-sync~~'' ~~tool~~:		Update the security checks using the ''greenbone'' tools:

	greenbone-nvt-sync		greenbone-nvt-sync
Line 53:		Line 78:
	openvas-check-setup --v9		openvas-check-setup --v9

	~~Enable signature checking of OpenVAS NVTs is optional, see http://www.openvas.org/trusted-nvts.html for details (WARNING - this has not been verified for OpenVAS 9).~~

	~~install -d -m 700 /etc/openvas/gnupg~~
	~~gpg --homedir=/etc/openvas/gnupg --gen-key~~
	~~wget http://www.openvas.org/OpenVAS_TI.asc~~
	~~gpg --homedir=/etc/openvas/gnupg --import OpenVAS_TI.asc~~

	~~# List keys to determine ID of imported key~~
	~~gpg --homedir=/etc/openvas/gnupg --list-keys~~
	~~# Substitute ID of imported key for KEY_ID shown below~~
	~~gpg --homedir=/etc/openvas/gnupg --lsign-key KEY_ID~~

	~~# Turn on NVT signature checking in OpenVAS configuration~~
	~~sed -i -e 's,^\(nasl_no_signature_check =\).*,\1 no,' /etc/openvas/openvassd.conf~~
	~~openvas-check-setup --v9~~
	Start and enable the OpenVAS scanner service to initialize NVT cache:		Start and enable the OpenVAS scanner service to initialize NVT cache:

	systemctl start openvas-scanner.service		systemctl start openvas-scanner.service
	systemctl enable openvas-scanner.service		systemctl enable openvas-scanner.service # To enable at boot
	# Wait for CPU to settle, eventually the following message should go		# Wait for CPU to settle, eventually the following message should go
	# away from the openvas-check-setup - may take a long time:		# away from the openvas-check-setup - may take a long time:
	~~openvas-check-setup --v9~~

	~~Create a client certificate:~~

	~~# SKIP FOR NOW~~
	~~openvas-mkcert-client -n -i~~
	openvas-check-setup --v9		openvas-check-setup --v9

Line 99:		Line 103:

	openvas-manage-certs -a		openvas-manage-certs -a
			openvas-check-setup --v9

	Start and enable the OpenVAS manager service:		Start and enable the OpenVAS manager service:

	systemctl start openvas-manager.service		systemctl start openvas-manager.service
	systemctl enable openvas-manager.service		systemctl enable openvas-manager.service # To enable at boot
	openvas-check-setup		openvas-check-setup --v9

	Start and enable the Greenbone Security Assistant (GSA) service:		Start and enable the Greenbone Security Assistant (GSA) service:

	systemctl start openvas-gsa.service		systemctl start openvas-gsa.service
	systemctl enable openvas-gsa.service		systemctl enable openvas-gsa.service # To enable at boot
	openvas-check-setup		openvas-check-setup --v9

	== Accessing OpenVAS on an NST Probe ==		== Accessing OpenVAS on an NST Probe ==

Paul Blankenbaker at 14:12, 28 February 2018

2018-02-28T14:12:04Z

← Older revision		Revision as of 10:12, 28 February 2018
Line 31:		Line 31:
	dnf install openvas-libraries openvas-scanner openvas-manager openvas-cli openvas-gsa gnutls-utils redis alien nsis texlive-collection-latexextra		dnf install openvas-libraries openvas-scanner openvas-manager openvas-cli openvas-gsa gnutls-utils redis alien nsis texlive-collection-latexextra

	Use the openvas-check-setup command as a diagnostic and guide during the installation process. We will be running this command a lot!		Use the openvas-check-setup command as a diagnostic and guide during the installation process. We will be running this command a lot and it will report an ERROR until we complete the setup!

	openvas-check-setup		openvas-check-setup --v9

	Edit the ''/etc/redis.conf'' file and make certain that the following two lines are uncommented (NOTE: We are not entirely certain that this step is required):		Edit the ''/etc/redis.conf'' file and make certain that the following two lines are uncommented (NOTE: We are not entirely certain that this step is required):
Line 44:		Line 44:
	systemctl restart redis.service		systemctl restart redis.service
	systemctl enable redis.service		systemctl enable redis.service
	openvas-check-setup		openvas-check-setup --v9

	Update the security checks using the ''greenbone-nvt-sync'' tool:		Update the security checks using the ''greenbone-nvt-sync'' tool:

	~~openvas~~-nvt-sync		greenbone-nvt-sync
	openvas-check-setup		greenbone-scapdata-sync
			greenbone-certdata-sync
			openvas-check-setup --v9

	Enable signature checking of OpenVAS NVTs is optional, see http://www.openvas.org/trusted-nvts.html for details.		Enable signature checking of OpenVAS NVTs is optional, see http://www.openvas.org/trusted-nvts.html for details (WARNING - this has not been verified for OpenVAS 9).

	install -d -m 700 /etc/openvas/gnupg		install -d -m 700 /etc/openvas/gnupg
Line 65:		Line 67:
	# Turn on NVT signature checking in OpenVAS configuration		# Turn on NVT signature checking in OpenVAS configuration
	sed -i -e 's,^\(nasl_no_signature_check =\).*,\1 no,' /etc/openvas/openvassd.conf		sed -i -e 's,^\(nasl_no_signature_check =\).*,\1 no,' /etc/openvas/openvassd.conf
	openvas-check-setup		openvas-check-setup --v9

	Start and enable the OpenVAS scanner service to initialize NVT cache:		Start and enable the OpenVAS scanner service to initialize NVT cache:

Line 73:		Line 74:
	# Wait for CPU to settle, eventually the following message should go		# Wait for CPU to settle, eventually the following message should go
	# away from the openvas-check-setup - may take a long time:		# away from the openvas-check-setup - may take a long time:
	~~# "NVT cache has not yet been generated" message should go away~~		openvas-check-setup --v9
	openvas-check-setup

	Create a client certificate:		Create a client certificate:

			# SKIP FOR NOW
	openvas-mkcert-client -n -i		openvas-mkcert-client -n -i
	openvas-check-setup		openvas-check-setup --v9

	Rebuild the openvas manager database:		Rebuild the openvas manager database:

			install -D -d -m 755 /var/lib/openvas/openvasmd/gnupg
	rm -f /var/lib/openvas/mgr/tasks.db		rm -f /var/lib/openvas/mgr/tasks.db
	openvasmd -f -v --rebuild		openvasmd -f -v --rebuild
	openvas-check-setup		openvas-check-setup --v9

	Create a user account (''admin'' in this example). Make sure you remember or copy/paste the password that is displayed (it will be a long string of random characters). Or, set it to a preferred password		Create a user account (''admin'' in this example). Make sure you remember or copy/paste the password that is displayed (it will be a long string of random characters). Or, set it to a preferred password
Line 92:		Line 94:
	# To change the password after creation, use:		# To change the password after creation, use:
	openvasmd --user=admin --new-password=PASSWORD		openvasmd --user=admin --new-password=PASSWORD
	openvas-check-setup		openvas-check-setup --v9

	~~Intialize the OpenVAS SCAP database (takes awhile).~~

	~~openvas~~-~~scapdata~~-~~sync~~
	~~openvas-check-setup~~

	~~Initialize~~ the ~~OpenVAS CERT database.~~		Update the certificates:

	openvas-~~certdata~~-~~sync~~		openvas-manage-certs -a
	~~openvas~~-~~check-setup~~

	Start and enable the OpenVAS manager service:		Start and enable the OpenVAS manager service:

Paul Blankenbaker: Added NST 26 set up instructions

2017-08-06T14:04:26Z

Added NST 26 set up instructions

← Older revision		Revision as of 10:04, 6 August 2017
Line 21:		Line 21:
	# Run Task.		# Run Task.

			= '''NST 26 Setup''' =

			Getting OpenVAS (http://openvas.org) and Greenbone (https://www.greenbone.net/) set up and working on a NST 26 or Fedora 26 based system is a non-trivial task and involves some time (plan on 60 minutes). While the instructions below are based on a successful set up, due to the dynamic nature of all the packages and systems involved adjustments may need to be made in the future. Repeated use of the ''openvas-check-setup'' tool is highly recommended as you set up your system as it will not only indicate what is wrong, but will also provide useful instructions on what to do next to correct the issue.

			== Installation and Setup ==

			Log into a terminal as ''root'' and make sure the following packages are installed (alien, nsis and texlive-collection-latexextra are optional, but you will be missing some functionality if you do not include them):

			dnf install openvas-libraries openvas-scanner openvas-manager openvas-cli openvas-gsa gnutls-utils redis alien nsis texlive-collection-latexextra

			Use the openvas-check-setup command as a diagnostic and guide during the installation process. We will be running this command a lot!

			openvas-check-setup

			Edit the ''/etc/redis.conf'' file and make certain that the following two lines are uncommented (NOTE: We are not entirely certain that this step is required):

			unixsocket /tmp/redis.sock
			unixsocketperm 700

			Start and enable the ''redis'' service (restart if already running and you modified the configuration file):

			systemctl restart redis.service
			systemctl enable redis.service
			openvas-check-setup

			Update the security checks using the ''greenbone-nvt-sync'' tool:

			openvas-nvt-sync
			openvas-check-setup

			Enable signature checking of OpenVAS NVTs is optional, see http://www.openvas.org/trusted-nvts.html for details.

			install -d -m 700 /etc/openvas/gnupg
			gpg --homedir=/etc/openvas/gnupg --gen-key
			wget http://www.openvas.org/OpenVAS_TI.asc
			gpg --homedir=/etc/openvas/gnupg --import OpenVAS_TI.asc

			# List keys to determine ID of imported key
			gpg --homedir=/etc/openvas/gnupg --list-keys
			# Substitute ID of imported key for KEY_ID shown below
			gpg --homedir=/etc/openvas/gnupg --lsign-key KEY_ID

			# Turn on NVT signature checking in OpenVAS configuration
			sed -i -e 's,^\(nasl_no_signature_check =\).*,\1 no,' /etc/openvas/openvassd.conf
			openvas-check-setup

			Start and enable the OpenVAS scanner service to initialize NVT cache:

			systemctl start openvas-scanner.service
			systemctl enable openvas-scanner.service
			# Wait for CPU to settle, eventually the following message should go
			# away from the openvas-check-setup - may take a long time:
			# "NVT cache has not yet been generated" message should go away
			openvas-check-setup

			Create a client certificate:

			openvas-mkcert-client -n -i
			openvas-check-setup

			Rebuild the openvas manager database:

			rm -f /var/lib/openvas/mgr/tasks.db
			openvasmd -f -v --rebuild
			openvas-check-setup

			Create a user account (''admin'' in this example). Make sure you remember or copy/paste the password that is displayed (it will be a long string of random characters). Or, set it to a preferred password

			openvasmd --create-user=admin --role=Admin
			# To change the password after creation, use:
			openvasmd --user=admin --new-password=PASSWORD
			openvas-check-setup

			Intialize the OpenVAS SCAP database (takes awhile).

			openvas-scapdata-sync
			openvas-check-setup

			Initialize the OpenVAS CERT database.

			openvas-certdata-sync
			openvas-check-setup

			Start and enable the OpenVAS manager service:

			systemctl start openvas-manager.service
			systemctl enable openvas-manager.service
			openvas-check-setup

			Start and enable the Greenbone Security Assistant (GSA) service:

			systemctl start openvas-gsa.service
			systemctl enable openvas-gsa.service
			openvas-check-setup

			== Accessing OpenVAS on an NST Probe ==

			You should now be able to access the Greenbone Security Assistant at https://127.0.0.1:9443 (you can substitute the IP address of your NST system for the ''127.0.0.1'' if accessing remotely).

			You should be able to log in as ''admin'' using the initially generated password. After logging in, select ''User'' under the ''Administration'' menu and update your password (if desired).

			From the main page, you can perform a quick scan on the NST system itself by entering the IPv4 address of your NST system and pressing the ''Start Scan'' button:

			[[Image:openvas-quickscan.png]]

			When the scan completes it should only include informational entries in the vulnerability report (Log issues describing things discovered that are not necessarily vulnerabilities). Also, if you scan ''127.0.0.1'' instead of the IPv4 address associated with your network interface, you may find more issues.

			You should also be able to verify that the OpenVAS Command Line Interface (CLI) by running:

			omp --ping
			omp -p 9390 --username=admin --password=YOUR_PASSWORD --xml="<help/>"
			...

			Refer to the http://openvas.org/ web site for instructions on using OpenVAS and the Greenbone Security Assistant.

	= '''NST 22 Setup''' =		= '''NST 22 Setup''' =

Paul Blankenbaker at 09:49, 11 December 2015

2015-12-11T09:49:39Z

← Older revision		Revision as of 05:49, 11 December 2015
Line 34:		Line 34:
	openvas-nvt-sync		openvas-nvt-sync

	Edit the ''/etc/redis.conf'' file and make certain that the following two lines are uncommented:		Edit the ''/etc/redis.conf'' file and make certain that the following two lines are uncommented (NOTE: We are not entirely certain that this step is required):

	unixsocket /tmp/redis.sock		unixsocket /tmp/redis.sock
Line 85:		Line 85:

	[[Image:openvas-quickscan.png]]		[[Image:openvas-quickscan.png]]

			When the scan completes it may report a few medium severity issues related to the ''openvasmd'' process on port 9390.

	You should also be able to verify that the OpenVAS Command Line Interface (CLI) by running:		You should also be able to verify that the OpenVAS Command Line Interface (CLI) by running:

Paul Blankenbaker at 09:40, 11 December 2015

2015-12-11T09:40:59Z

Show changes