Help Irongeek.com pay for bandwidth and research equipment:
Man page of NASL
Section: Nessus Attack Scripting Language (1)
Updated: May 2006
Index of this MAN page
Back To MAN Pages From BackTrack 5 R1 Master List
openvas-nasl - Nessus Attack Scripting Language
<[-vh] [-T tracefile] [-s] [-t target] [-sX] > files...
executes a set of NASL scripts against a given target host. It can
also be used to determine if a NASL script has any syntax errors by running
it in parse (-p) or lint (-L) mode.
- -T tracefile
Makes nasl write verbosely what the script does in the file
, ala 'set -x' under sh
- -t target
Apply the NASL script to
which may be a single host (127.0.0.1), a whole subnet (192.168.1.0/24)
or several subnets (192.168.1.0/24, 192.168.243.0/24)
Sets the return value of safe_checks() to 1. (See the OpenVAS documentation to know
what the safe checks are)
Only run the description part of the script.
the script (run extended checks).
Run the script in
mode. For more information see the nasl reference manual
Show the version of NASL.
The NASL2 reference manual
NASL comes from a private project called 'pkt_forge', which was written in late 1998 by Renaud Deraison and which was an interactive shell to forge and send raw IP packets (this pre-dates Perl's Net::RawIP by a couple of weeks). It was then extended to do a wide range of network-related operations and integrated into Nessus as 'NASL'.
The parser was completely hand-written and a pain to work with. In Mid-2002, Michel Arboi wrote a bison parser for NASL, and he and Renaud Deraison re-wrote NASL from scratch. Although the "new" NASL was nearly working as early as
August 2002, Michel's lazyness made us wait for early 2003 to have it working completely.
Most of the engine is (C) 2003 Michel Arboi, most of the built-in functions
are (C) 2003 Renaud Deraison
- SEE ALSO
This document was created by
using the manual pages.
Time: 07:34:21 GMT, September 13, 2011
Printable version of this article
15 most recent posts on Irongeek.com:
If you would like to republish one of the articles from this site on your
webpage or print journal please contact IronGeek.
Copyright 2016, IronGeek
Louisville / Kentuckiana Information Security Enthusiast