Author: jan
Date: 2007-10-16 22:26:28 +0200 (Tue, 16 Oct 2007)
New Revision: 442
Modified:
trunk/openvas-libnasl/ChangeLog
trunk/openvas-libnasl/doc/signatures-howto.txt
Log:
* doc/signatures-howto.txt: Fixed description: Unlike
Nessus, for OpenVAS plugins rules: no sig present hence
not executed.
Modified: trunk/openvas-libnasl/ChangeLog
===================================================================
--- trunk/openvas-libnasl/ChangeLog 2007-10-16 09:35:47 UTC (rev 441)
+++ trunk/openvas-libnasl/ChangeLog 2007-10-16 20:26:28 UTC (rev 442)
@@ -1,3 +1,9 @@
+2007-10-16 Jan-Oliver Wagner <[EMAIL PROTECTED]>
+
+ * doc/signatures-howto.txt: Fixed description: Unlike
+ Nessus, for OpenVAS plugins rules: no sig present hence
+ not executed.
+
2007-10-15 Jan-Oliver Wagner <[EMAIL PROTECTED]>
Post-release version bump.
Modified: trunk/openvas-libnasl/doc/signatures-howto.txt
===================================================================
--- trunk/openvas-libnasl/doc/signatures-howto.txt 2007-10-16 09:35:47 UTC
(rev 441)
+++ trunk/openvas-libnasl/doc/signatures-howto.txt 2007-10-16 20:26:28 UTC
(rev 442)
@@ -67,8 +67,8 @@
If any of the signatures does not meet all of these criteria, the file
is considered untrustworthy and will not be exectuded at all. If all
signatures meet the criteria, the script is trusted fully and may
-execute restricted functions like fwrite. If no signature file exists,
-the script is executed but may not execute restricted functions.
+execute any functions. If no signature file exists, the script is not
+executed.
To verify signatures on the command line, you can either run GnuPG:
_______________________________________________
Openvas-commits mailing list
[email protected]
http://lists.wald.intevation.org/mailman/listinfo/openvas-commits
