1NASL(1) NASL Attack Scripting Language NASL(1)
2
3
4
6 openvas-nasl - NASL Attack Scripting Language
7
9 openvas-nasl <[-vh] [-T tracefile] [-s] [-t target] [-c config_file]
10 [-d] [-sX] > files...
11
13 openvas-nasl executes a set of NASL scripts against a given target
14 host. It can also be used to determine if a NASL script has any syntax
15 errors by running it in parse (-p) or lint (-L) mode.
16
17
18
20 -T tracefile
21 Makes nasl write verbosely what the script does in the file
22 tracefile , ala 'set -x' under sh
23
24
25 -t target
26 Apply the NASL script to target which may be a single host
27 (127.0.0.1), a whole subnet (192.168.1.0/24) or several subnets
28 (192.168.1.0/24, 192.168.243.0/24)
29
30
31 -e iface
32 Specifies the network interface to be used as the source for
33 established connections.
34
35
36 -s Sets the return value of safe_checks() to 1. (See the OpenVAS
37 Scanner documentation to know what the safe checks are) Implies
38 -B.
39
40
41 -D Only run the description part of the script.
42
43
44 -B Runs in description mode before running the script.
45
46
47 -L Lint the script (run extended checks).
48
49
50 -X Run the script with disabled signature verification.
51
52
53 -h Show help
54
55 -v Show the version of NASL.
56
57 -d Output debug information to stderr.
58
59
60 -k key=value
61 Set KB key to value. Can be used multiple times.
62
63
65 openvas(8).
66
68 NASL comes from a private project called 'pkt_forge', which was written
69 in late 1998 by Renaud Deraison and which was an interactive shell to
70 forge and send raw IP packets (this pre-dates Perl's Net::RawIP by a
71 couple of weeks). It was then extended to do a wide range of network-
72 related operations and integrated into the scanner as 'NASL'.
73
74 The parser was completely hand-written and a pain to work with. In
75 Mid-2002, Michel Arboi wrote a bison parser for NASL, and he and Renaud
76 Deraison re-wrote NASL from scratch. Although the "new" NASL was nearly
77 working as early as August 2002, Michel's laziness made us wait for
78 early 2003 to have it working completely.
79
80 After the original authors decided to stop the Open Source development
81 in 2005, most changes and maintenance works were done by Greenbone Net‐
82 works.
83
84
86 Most of the engine is (C) 2003 Michel Arboi, most of the built-in func‐
87 tions are (C) 2003 Renaud Deraison. Most new code since 2005 developed
88 by Greenbone Networks GmbH.
89
90
91
92Greenbone Vulnerability ManagementOctober 2018 NASL(1)