Author: jan
Date: 2007-09-13 10:45:42 +0200 (Thu, 13 Sep 2007)
New Revision: 378
Added:
trunk/openvas-client/doc/OpenVAS-Client.1
Removed:
trunk/openvas-client/doc/OpenVAS-Client.1.in
Modified:
trunk/openvas-client/ChangeLog
trunk/openvas-client/TODO
trunk/openvas-client/configure
trunk/openvas-client/configure.in
Log:
* doc/OpenVAS-Client.1.in: Renamed to OpenVAS-Client.1 since there
where no differences, so no need to let handle this by autotools.
* doc/OpenVAS-Client.1: New. Former OpenVAS-Client.1.in.
* configure.in: Don't handle OpenVAS-CLient.1.in anymore.
* configure, TODO: Updated.
Modified: trunk/openvas-client/ChangeLog
===================================================================
--- trunk/openvas-client/ChangeLog 2007-08-30 14:06:30 UTC (rev 377)
+++ trunk/openvas-client/ChangeLog 2007-09-13 08:45:42 UTC (rev 378)
@@ -1,3 +1,14 @@
+2007-09-13 Jan-Oliver Wagner <[EMAIL PROTECTED]>
+
+ * doc/OpenVAS-Client.1.in: Renamed to OpenVAS-Client.1 since there
+ where no differences, so no need to let handle this by autotools.
+
+ * doc/OpenVAS-Client.1: New. Former OpenVAS-Client.1.in.
+
+ * configure.in: Don't handle OpenVAS-CLient.1.in anymore.
+
+ * configure, TODO: Updated.
+
2007-08-30 Jan-Oliver Wagner <[EMAIL PROTECTED]>
* src/gui/error_dlg.h: Applied standard header.
Modified: trunk/openvas-client/TODO
===================================================================
--- trunk/openvas-client/TODO 2007-08-30 14:06:30 UTC (rev 377)
+++ trunk/openvas-client/TODO 2007-09-13 08:45:42 UTC (rev 378)
@@ -1,11 +1,6 @@
List of things that should/could be done
to improve OpenVAS-Client:
-2007-08-16 Jan-Oliver Wagner <[EMAIL PROTECTED]>
-
- * doc/OpenVAS-Client.1.in: Probably can be renamed to OpenVAS-Client.1
-
-
2006-01-23 Jan-Oliver Wagner <[EMAIL PROTECTED]>
* Explicit saving of preferences
Modified: trunk/openvas-client/configure
===================================================================
--- trunk/openvas-client/configure 2007-08-30 14:06:30 UTC (rev 377)
+++ trunk/openvas-client/configure 2007-09-13 08:45:42 UTC (rev 378)
@@ -10747,7 +10747,7 @@
-ac_config_files="$ac_config_files nessus.tmpl include/corevers.h
openvasclient-mkcert doc/OpenVAS-Client.1"
+ac_config_files="$ac_config_files nessus.tmpl include/corevers.h
openvasclient-mkcert"
cat >confcache <<\_ACEOF
# This file is a shell script that caches the results of configure
@@ -11306,7 +11306,6 @@
"nessus.tmpl") CONFIG_FILES="$CONFIG_FILES nessus.tmpl" ;;
"include/corevers.h") CONFIG_FILES="$CONFIG_FILES include/corevers.h" ;;
"openvasclient-mkcert") CONFIG_FILES="$CONFIG_FILES openvasclient-mkcert"
;;
- "doc/OpenVAS-Client.1") CONFIG_FILES="$CONFIG_FILES doc/OpenVAS-Client.1"
;;
*) { { echo "$as_me:$LINENO: error: invalid argument: $ac_config_target" >&5
echo "$as_me: error: invalid argument: $ac_config_target" >&2;}
Modified: trunk/openvas-client/configure.in
===================================================================
--- trunk/openvas-client/configure.in 2007-08-30 14:06:30 UTC (rev 377)
+++ trunk/openvas-client/configure.in 2007-09-13 08:45:42 UTC (rev 378)
@@ -552,7 +552,7 @@
dnl And we put everything in the appropriate files
-AC_OUTPUT(nessus.tmpl include/corevers.h openvasclient-mkcert
doc/OpenVAS-Client.1)
+AC_OUTPUT(nessus.tmpl include/corevers.h openvasclient-mkcert)
chmod +x openvasclient-mkcert
Copied: trunk/openvas-client/doc/OpenVAS-Client.1 (from rev 377,
trunk/openvas-client/doc/OpenVAS-Client.1.in)
Deleted: trunk/openvas-client/doc/OpenVAS-Client.1.in
===================================================================
--- trunk/openvas-client/doc/OpenVAS-Client.1.in 2007-08-30 14:06:30 UTC
(rev 377)
+++ trunk/openvas-client/doc/OpenVAS-Client.1.in 2007-09-13 08:45:42 UTC
(rev 378)
@@ -1,261 +0,0 @@
-.TH OPENVASCLIENT 1 "August 2007" "The OpenVAS Project" "Users Manuals"
-.SH NAME
-OpenVAS-Client \- The client part of the OpenVAS Security Scanner
-.SH SYNOPSIS
-.B OpenVAS-Client [\|-v\|] [\|-h\|] [\|-n\|] [\|-T\|
-.IB <type> \|]\ [\|-q\ [\|-pPS\|]\ "host port user password targets
results\|" ]
-.P
-.B OpenVAS-Client -i in.[nsr|nbe] -o out.[html|xml|nsr|nbe]
-
-.SH DESCRIPTION
-The
-.B OpenVAS Security Scanner
-is a security auditing tool made up of two parts: a server, and a client.
-The server,
-.B openvasd
-is in charge of the attacks, whereas the client
-.B OpenVAS-Client
-provides an interface to the user.
-
-.B OpenVAS-Client
-is an X11 client based on GTK+2.
-
-This man page explains how to use the client.
-
-
-.SH OPTIONS
-.TP
-.BI "-c " <config-file> ", --config-file=" <config-file>
-use another configuration file.
-
-.TP
-.B "-n, --no-pixmaps"
-no pixmaps. This is handy if you are running OpenVAS-Client on a remote
computer.
-
-.TP
-.B "-q, --batch-mode"
-quiet mode or batch mode. Setting this option makes OpenVAS-Client
-expect all of the following settings.
-.RS
-.RI -p
-.RS
- obtain list of plugins installed on the server.
-.RE
-.RI -P
-.RS
-obtain list of server and plugin preferences.
-.RE
-.RI -S
-.RS
-issue SQL output for -p and -P (experimental).
-.RE
-.RI \(bu\ host
-.RS
-is the
-.B openvasd
-host to whom you will connect.
-.RE
-.RI \(bu\ port
-.RS
-is the port to which you will connect on the remote
-.B openvasd
-host.
-.RE
-.RI \(bu\ user
-.RS
-is the user name to use to connect to
-.BR openvasd .
-.RE
-.RI \(bu\ password
-.RS
-is the password associated with this user name.
-.RE
-.RI \(bu\ targets
-.RS
-is the name of a file containing the target machines.
-.RE
-.RI \(bu\ results
-.RS
-is the name of the file where the results will be stored at the end of
-the test.
-.RE 1
-
-.TP
-.BI "-r " <report-file> ", --open-report=" <report-file>
-Using the GUI,
-.B OpenVAS-Client
-visualizes a report file from a previous session. Repeating this option,
-more files are displayed.
-
-.TP
-.BI "-T " <type> ", --output-type=" <type>"
-Save the data as <type>, where <type> can be \*(lqnbe\*(rq, \*(lqhtml\*(rq,
-\*(lqhtml_graph\*(rq, \*(lqtext\*(rq, \*(lqxml\*(rq, \*(lqold-xml\*(rq,
-\*(lqtex\*(rq or \*(lqnsr\*(rq
-
-.TP
-.B "-V, --verbose"
-make the batch mode display status messages to the screen.
-
-.TP
-.B "-x, --dont-check-ssl-cert"
-do not check SSL certificates.
-
-.TP
-.B "-v, --version"
-shows version number and quits
-
-.TP
-.B "-h, --help"
-lists the available options
-
-.SH The X11 interface
-
-The OpenVAS-Client interface is divided in several panels:
-.IP "\(bu The \*(lqOpenvasd host\*(rq section: "
-In this section, you must enter the
-.B openvasd
-host to whom you will connect, as well as the port. You must also enter your
-.B openvasd
-user name and your password (not the one of the system). Once you are done, you
-must click on the \*(lqLog in\*(rq button, which will establish the
-connection to the
-.B openvasd
-host.
-.br
-Once the connection is established,
-.B openvasd
-sends to the client the list of attacks it will perform, as well as the
-default preferences to use.
-
-.IP "\(bu The \*(lqTarget Selection\*(rq section: "
-\(bu In this section, you are required to enter the primary target. A
-primary target
-may be a single host (e.g. x.y.test), an IP (e.g. 192.168.1.1), a
-subnet (e.g. 192.168.1.1/24 or x.y.test), or a list of hosts,
-separated by commas (e.g. 192.168.1.1, 192.168.2.1/24, x.y.test,
-a.b.test).
-.br
-
-
-\(bu You can restrict the maximum number of hosts to test using the
-\*(lqMax Hosts\*(rq entry.
-This is a feature that prevents you from scanning too many machines;
-or accidentally scanning other machines.
-(For instance, if you only plan to test x.y.info and
-a.b.info, you can safely set this entry to \*(lq2\*(rq).
-.br
-
-
-\(bu This panel also allows you to enable the \*(lqPerform a DNS zone
-transfer\*(rq
-option. This option is dangerous and should be enabled with caution.
-For instance, if you want to test www.x.test, then if this option is set,
-.B openvasd
-will attempt to get the list of the hosts in the \*(lqx.test\*(rq
-domain.
-
-This option may be dangerous. For instance, if you enable it and you ask to
-test 192.168.1.1/24, then
-.B openvasd
-will do a reverse lookup on
-.I every
-IP, and will attempt a DNS zone transfer on every domain. That is, if
-192.168.1.1 is www.x.test, and 192.168.1.10 is mail.x.test, then
-a DNS zone transfer will be made on the domains \*(lqx.test\*(rq
-and \*(lqtest.x\*(rq.
-
-
-.IP "\(bu The \*(lqPlugins\*(rq section"
-Once you have successfully logged into the remote
-.B openvasd
-server,
-this section is filed with the list of the attacks that the server will
-perform. This panel is divided in two parts: the plugins families, and
-the plugins themselves. If you click on the name of a plugin, then
-a dialog will appear, showing you which will be the error message
-sent by the plugin if the attack is successful.
-
-.SH Report conversion
-.P
-You can use
-.B OpenVAS-Client
-to do conversion between formats used for reports. Nessus can take
-any NSR or NBE reports and change them into HTML, XML, NSR or NBE reports.
-.P
-Please note that the XML report provides usually more information
-about the scan itself NSR or NBE formats do not include in the report.
-.P
-Basically, XML is a merge between the .nbe reports and the .openvasrc
-configuration file. You won't get extra verbosity or diagnosis info in
-the XML report, but you'll know which plugins (and which version of
-these plugins) have been enabled during the scan.
-.P
-For more information on the report formats please read the files
-.B nsr_file_format.txt
-and
-.B nbe_file_format.txt
-provided along with the documentation.
-
-.SH "ENVIRONMENT VARIABLES"
-.TP
-.B HOME
-The path to the user's home directory which will hold the client
-configuration cache
-.IR .openvasrc .
-The path is refered to as
-.IR ~/ ,
-below.
-
-.TP
-.B OPENVASHOME
-If this environment variable is set, this path is used instead of the
-path defined by the
-.B HOME
-variable. This path is referred to as
-.IR ~/ ,
-below.
-
-% More examples should be included here (jfs)
-.SH EXAMPLES
-.P
-To run a batch scan from a cron job and publish it in a given
-web space (
-.B /var/www/html/openvas/
-) try the following:
-.P
-.B OpenVAS-Client -c /root/openvas/openvas.rc -T html -qx localhost 1241 batch
batch1
-.B /root/openvas/target /var/www/html/openvas/results.html
-.P
-Make sure that paranoia level is
-.B not
-set in your
-.B openvas.rc
-configuration file, otherwise the scan will not work
-
-.SH FILES
-.TP
-.I ~/.openvasrc
-is the client configuration file, which contains the options about which
-.B openvasd
-server to connect to, which plugins to activate, and so on. The file is
-created automatically if it does not exist.
-
-.SH "SEE ALSO"
-.BR openvasclient-mkcert (1)
-
-.SH MORE INFORMATION ABOUT THE OPENVAS PROJECT
-The canonical places where you will find more information
-about the OpenVAS project are:
-
-.RS
-.UR
-http://www.openvas.org/
-.RE
-
-.SH AUTHORS
-Author of developments prior to the fork from NessusClient
-is Renaud Deraison <[EMAIL PROTECTED]>.
-
-Several other people have been kind enough to send patches and bug reports.
-Thanks to them.
_______________________________________________
Openvas-commits mailing list
[email protected]
http://lists.wald.intevation.org/mailman/listinfo/openvas-commits
