Just refer to the smb module documentation for the smb* script args rather than

duplicating it in every script. This may not be the way we keep doing it, but
it's needed for now to keep from having excessive duplication in the printed
output.

scripts/smb-enumdomains.nse

@@ -39,33 +39,9 @@ After the initial <code>bind()</code> to SAMR, the sequence of calls is:
 -- |     |_  Password complexity requirements do not exist
 -- |_    |_  Administrator account cannot be locked out
 -- 
---@args  smbusername The SMB username to log in with. The forms "DOMAIN\username" and "username@DOMAIN"
+-- @args smb* This script supports the <code>smbusername</code>,
---                   are not understood. To set a domain, use the <code>smbdomain</code> argument. 
+-- <code>smbpassword</code>, <code>smbhash</code>, <code>smbguest</code>, and
---@args  smbdomain   The domain to log in with. If you aren't in a domained environment, then anything
+-- <code>smbtype</code> script arguments of the <code>smb</code> module.
---                   will (should?) be accepted by the server. 
---@args  smbpassword The password to connect with. Be cautious with this, since some servers will lock
---                   accounts if the incorrect password is given. Although it's rare that the
---                   Administrator account can be locked out, in the off chance that it can, you could
---                   get yourself in trouble. 
---@args  smbhash     A password hash to use when logging in. This is given as a single hex string (32
---                   characters) or a pair of hex strings (both 32 characters, optionally separated by a 
---                   single character). These hashes are the LanMan or NTLM hash of the user's password,
---                   and are stored on disk or in memory. They can be retrieved from memory
---                   using the fgdump or pwdump tools. 
---@args  smbguest    If this is set to <code>true</code> or <code>1</code>, a guest login will be attempted if the normal one 
---                   fails. This should be harmless, but I thought I would disable it by default anyway
---                   because I'm not entirely sure of any possible consequences. 
---@args  smbtype     The type of SMB authentication to use. These are the possible options:
--- * <code>v1</code>: Sends LMv1 and NTLMv1.
--- * <code>LMv1</code>: Sends LMv1 only.
--- * <code>NTLMv1</code>: Sends NTLMv1 only (default).
--- * <code>v2</code>: Sends LMv2 and NTLMv2.
--- * <code>LMv2</code>: Sends LMv2 only.
---                   The default, <code>NTLMv1</code>, is a pretty
---                   decent compromise between security and compatibility. If you are paranoid, you might 
---                   want to use <code>v2</code> or <code>lmv2</code> for this. (Actually, if you're paranoid, you should be 
---                   avoiding this protocol altogether :P). If you're using an extremely old system, you 
---                   might need to set this to <code>v1</code> or <code>lm</code>, which are less secure but more compatible. 
 -----------------------------------------------------------------------
 
 author = "Ron Bowes"

scripts/smb-enumsessions.nse

@@ -38,33 +38,9 @@ idea to write this one.
 -- |  Active SMB Sessions:
 -- |_ |_ ADMINISTRATOR is connected from 10.100.254.138 for [just logged in, it's probably you], idle for [not idle]
 -- 
---@args  smbusername The SMB username to log in with. The forms "DOMAIN\username" and "username@DOMAIN"
+-- @args smb* This script supports the <code>smbusername</code>,
---                   are not understood. To set a domain, use the <code>smbdomain</code> argument. 
+-- <code>smbpassword</code>, <code>smbhash</code>, <code>smbguest</code>, and
---@args  smbdomain   The domain to log in with. If you aren't in a domained environment, then anything
+-- <code>smbtype</code> script arguments of the <code>smb</code> module.
---                   will (should?) be accepted by the server. 
---@args  smbpassword The password to connect with. Be cautious with this, since some servers will lock
---                   accounts if the incorrect password is given. Although it's rare that the
---                   Administrator account can be locked out, in the off chance that it can, you could
---                   get yourself in trouble. 
---@args  smbhash     A password hash to use when logging in. This is given as a single hex string (32
---                   characters) or a pair of hex strings (both 32 characters, optionally separated by a 
---                   single character). These hashes are the LanMan or NTLM hash of the user's password,
---                   and are stored on disk or in memory. They can be retrieved from memory
---                   using the fgdump or pwdump tools. 
---@args  smbguest    If this is set to <code>true</code> or <code>1</code>, a guest login will be attempted if the normal one 
---                   fails. This should be harmless, but I thought I would disable it by default anyway
---                   because I'm not entirely sure of any possible consequences. 
---@args  smbtype     The type of SMB authentication to use. These are the possible options:
--- * <code>v1</code>: Sends LMv1 and NTLMv1.
--- * <code>LMv1</code>: Sends LMv1 only.
--- * <code>NTLMv1</code>: Sends NTLMv1 only (default).
--- * <code>v2</code>: Sends LMv2 and NTLMv2.
--- * <code>LMv2</code>: Sends LMv2 only.
---                   The default, <code>NTLMv1</code>, is a pretty
---                   decent compromise between security and compatibility. If you are paranoid, you might 
---                   want to use <code>v2</code> or <code>lmv2</code> for this. (Actually, if you're paranoid, you should be 
---                   avoiding this protocol altogether :P). If you're using an extremely old system, you 
---                   might need to set this to <code>v1</code> or <code>lm</code>, which are less secure but more compatible. 
 -----------------------------------------------------------------------
 
 id = "MSRPC: NetSessEnum()"

scripts/smb-enumshares.nse

@@ -58,33 +58,9 @@ doing an authenticated test.
 -- |     |_ Users: 0, Max: <unlimited>
 -- |_    |_ Path: C:\
 -- 
---@args  smbusername The SMB username to log in with. The forms "DOMAIN\username" and "username@DOMAIN"
+-- @args smb* This script supports the <code>smbusername</code>,
---                   are not understood. To set a domain, use the <code>smbdomain</code> argument. 
+-- <code>smbpassword</code>, <code>smbhash</code>, <code>smbguest</code>, and
---@args  smbdomain   The domain to log in with. If you aren't in a domained environment, then anything
+-- <code>smbtype</code> script arguments of the <code>smb</code> module.
---                   will (should?) be accepted by the server. 
---@args  smbpassword The password to connect with. Be cautious with this, since some servers will lock
---                   accounts if the incorrect password is given. Although it's rare that the
---                   Administrator account can be locked out, in the off chance that it can, you could
---                   get yourself in trouble. 
---@args  smbhash     A password hash to use when logging in. This is given as a single hex string (32
---                   characters) or a pair of hex strings (both 32 characters, optionally separated by a 
---                   single character). These hashes are the LanMan or NTLM hash of the user's password,
---                   and are stored on disk or in memory. They can be retrieved from memory
---                   using the fgdump or pwdump tools. 
---@args  smbguest    If this is set to <code>true</code> or <code>1</code>, a guest login will be attempted if the normal one 
---                   fails. This should be harmless, but I thought I would disable it by default anyway
---                   because I'm not entirely sure of any possible consequences. 
---@args  smbtype     The type of SMB authentication to use. These are the possible options:
--- * <code>v1</code>: Sends LMv1 and NTLMv1.
--- * <code>LMv1</code>: Sends LMv1 only.
--- * <code>NTLMv1</code>: Sends NTLMv1 only (default).
--- * <code>v2</code>: Sends LMv2 and NTLMv2.
--- * <code>LMv2</code>: Sends LMv2 only.
---                   The default, <code>NTLMv1</code>, is a pretty
---                   decent compromise between security and compatibility. If you are paranoid, you might 
---                   want to use <code>v2</code> or <code>lmv2</code> for this. (Actually, if you're paranoid, you should be 
---                   avoiding this protocol altogether :P). If you're using an extremely old system, you 
---                   might need to set this to <code>v1</code> or <code>lm</code>, which are less secure but more compatible. 
 -----------------------------------------------------------------------
 
 author = "Ron Bowes"

scripts/smb-enumusers.nse

@@ -110,33 +110,9 @@ the code I wrote for this is largely based on the techniques used by them.
 -- |    |_ Type: Alias
 -- |_   |_ Domain: LOCALSYSTEM
 -- 
---@args  smbusername The SMB username to log in with. The forms "DOMAIN\username" and "username@DOMAIN"
+-- @args smb* This script supports the <code>smbusername</code>,
---                   are not understood. To set a domain, use the <code>smbdomain</code> argument. 
+-- <code>smbpassword</code>, <code>smbhash</code>, <code>smbguest</code>, and
---@args  smbdomain   The domain to log in with. If you aren't in a domained environment, then anything
+-- <code>smbtype</code> script arguments of the <code>smb</code> module.
---                   will (should?) be accepted by the server. 
---@args  smbpassword The password to connect with. Be cautious with this, since some servers will lock
---                   accounts if the incorrect password is given. Although it's rare that the
---                   Administrator account can be locked out, in the off chance that it can, you could
---                   get yourself in trouble. 
---@args  smbhash     A password hash to use when logging in. This is given as a single hex string (32
---                   characters) or a pair of hex strings (both 32 characters, optionally separated by a 
---                   single character). These hashes are the LanMan or NTLM hash of the user's password,
---                   and are stored on disk or in memory. They can be retrieved from memory
---                   using the fgdump or pwdump tools. 
---@args  smbguest    If this is set to <code>true</code> or <code>1</code>, a guest login will be attempted if the normal one 
---                   fails. This should be harmless, but I thought I would disable it by default anyway
---                   because I'm not entirely sure of any possible consequences. 
---@args  smbtype     The type of SMB authentication to use. These are the possible options:
--- * <code>v1</code>: Sends LMv1 and NTLMv1.
--- * <code>LMv1</code>: Sends LMv1 only.
--- * <code>NTLMv1</code>: Sends NTLMv1 only (default).
--- * <code>v2</code>: Sends LMv2 and NTLMv2.
--- * <code>LMv2</code>: Sends LMv2 only.
---                   The default, <code>NTLMv1</code>, is a pretty
---                   decent compromise between security and compatibility. If you are paranoid, you might 
---                   want to use <code>v2</code> or <code>lmv2</code> for this. (Actually, if you're paranoid, you should be 
---                   avoiding this protocol altogether :P). If you're using an extremely old system, you 
---                   might need to set this to <code>v1</code> or <code>lm</code>, which are less secure but more compatible. 
 -----------------------------------------------------------------------
 
 author = "Ron Bowes"

scripts/smb-os-discovery.nse

@@ -18,33 +18,9 @@ they likely won't change the outcome in any meaningful way.
 -- |  Name: WORKGROUP\TEST1
 -- |_ System time: 2008-09-09 20:55:55 UTC-5
 -- 
---@args  smbusername The SMB username to log in with. The forms "DOMAIN\username" and "username@DOMAIN"
+-- @args smb* This script supports the <code>smbusername</code>,
---                   are not understood. To set a domain, use the <code>smbdomain</code> argument. 
+-- <code>smbpassword</code>, <code>smbhash</code>, <code>smbguest</code>, and
---@args  smbdomain   The domain to log in with. If you aren't in a domained environment, then anything
+-- <code>smbtype</code> script arguments of the <code>smb</code> module.
---                   will (should?) be accepted by the server. 
---@args  smbpassword The password to connect with. Be cautious with this, since some servers will lock
---                   accounts if the incorrect password is given. Although it's rare that the
---                   Administrator account can be locked out, in the off chance that it can, you could
---                   get yourself in trouble. 
---@args  smbhash     A password hash to use when logging in. This is given as a single hex string (32
---                   characters) or a pair of hex strings (both 32 characters, optionally separated by a 
---                   single character). These hashes are the LanMan or NTLM hash of the user's password,
---                   and are stored on disk or in memory. They can be retrieved from memory
---                   using the fgdump or pwdump tools. 
---@args  smbguest    If this is set to <code>true</code> or <code>1</code>, a guest login will be attempted if the normal one 
---                   fails. This should be harmless, but I thought I would disable it by default anyway
---                   because I'm not entirely sure of any possible consequences. 
---@args  smbtype     The type of SMB authentication to use. These are the possible options:
--- * <code>v1</code>: Sends LMv1 and NTLMv1.
--- * <code>LMv1</code>: Sends LMv1 only.
--- * <code>NTLMv1</code>: Sends NTLMv1 only (default).
--- * <code>v2</code>: Sends LMv2 and NTLMv2.
--- * <code>LMv2</code>: Sends LMv2 only.
---                   The default, <code>NTLMv1</code>, is a pretty
---                   decent compromise between security and compatibility. If you are paranoid, you might 
---                   want to use <code>v2</code> or <code>lmv2</code> for this. (Actually, if you're paranoid, you should be 
---                   avoiding this protocol altogether :P). If you're using an extremely old system, you 
---                   might need to set this to <code>v1</code> or <code>lm</code>, which are less secure but more compatible. 
 -----------------------------------------------------------------------
 
 author = "Ron Bowes"

scripts/smb-security-mode.nse

@@ -48,33 +48,9 @@ set the username and password, etc.), but it probably won't ever require them.
 -- |  SMB Security: Challenge/response passwords supported
 -- |_ SMB Security: Message signing supported
 -- 
---@args  smbusername The SMB username to log in with. The forms "DOMAIN\username" and "username@DOMAIN"
+-- @args smb* This script supports the <code>smbusername</code>,
---                   are not understood. To set a domain, use the <code>smbdomain</code> argument. 
+-- <code>smbpassword</code>, <code>smbhash</code>, <code>smbguest</code>, and
---@args  smbdomain   The domain to log in with. If you aren't in a domained environment, then anything
+-- <code>smbtype</code> script arguments of the <code>smb</code> module.
---                   will (should?) be accepted by the server. 
---@args  smbpassword The password to connect with. Be cautious with this, since some servers will lock
---                   accounts if the incorrect password is given. Although it's rare that the
---                   Administrator account can be locked out, in the off chance that it can, you could
---                   get yourself in trouble. 
---@args  smbhash     A password hash to use when logging in. This is given as a single hex string (32
---                   characters) or a pair of hex strings (both 32 characters, optionally separated by a 
---                   single character). These hashes are the LanMan or NTLM hash of the user's password,
---                   and are stored on disk or in memory. They can be retrieved from memory
---                   using the fgdump or pwdump tools. 
---@args  smbguest    If this is set to <code>true</code> or <code>1</code>, a guest login will be attempted if the normal one 
---                   fails. This should be harmless, but I thought I would disable it by default anyway
---                   because I'm not entirely sure of any possible consequences. 
---@args  smbtype     The type of SMB authentication to use. These are the possible options:
--- * <code>v1</code>: Sends LMv1 and NTLMv1.
--- * <code>LMv1</code>: Sends LMv1 only.
--- * <code>NTLMv1</code>: Sends NTLMv1 only (default).
--- * <code>v2</code>: Sends LMv2 and NTLMv2.
--- * <code>LMv2</code>: Sends LMv2 only.
---                   The default, <code>NTLMv1</code>, is a pretty
---                   decent compromise between security and compatibility. If you are paranoid, you might 
---                   want to use <code>v2</code> or <code>lmv2</code> for this. (Actually, if you're paranoid, you should be 
---                   avoiding this protocol altogether :P). If you're using an extremely old system, you 
---                   might need to set this to <code>v1</code> or <code>lm</code>, which are less secure but more compatible. 
 -----------------------------------------------------------------------
 
 author = "Ron Bowes"

scripts/smb-serverstats.nse

@@ -25,33 +25,9 @@ the numbers that Windows returns. Take the values here with a grain of salt.
 -- |  |_ Print jobs spooled: 0
 -- |_ |_ Files opened (including pipes): 18
 -- 
---@args  smbusername The SMB username to log in with. The forms "DOMAIN\username" and "username@DOMAIN"
+-- @args smb* This script supports the <code>smbusername</code>,
---                   are not understood. To set a domain, use the <code>smbdomain</code> argument. 
+-- <code>smbpassword</code>, <code>smbhash</code>, <code>smbguest</code>, and
---@args  smbdomain   The domain to log in with. If you aren't in a domained environment, then anything
+-- <code>smbtype</code> script arguments of the <code>smb</code> module.
---                   will (should?) be accepted by the server. 
---@args  smbpassword The password to connect with. Be cautious with this, since some servers will lock
---                   accounts if the incorrect password is given. Although it's rare that the
---                   Administrator account can be locked out, in the off chance that it can, you could
---                   get yourself in trouble. 
---@args  smbhash     A password hash to use when logging in. This is given as a single hex string (32
---                   characters) or a pair of hex strings (both 32 characters, optionally separated by a 
---                   single character). These hashes are the LanMan or NTLM hash of the user's password,
---                   and are stored on disk or in memory. They can be retrieved from memory
---                   using the fgdump or pwdump tools. 
---@args  smbguest    If this is set to <code>true</code> or <code>1</code>, a guest login will be attempted if the normal one 
---                   fails. This should be harmless, but I thought I would disable it by default anyway
---                   because I'm not entirely sure of any possible consequences. 
---@args  smbtype     The type of SMB authentication to use. These are the possible options:
--- * <code>v1</code>: Sends LMv1 and NTLMv1.
--- * <code>LMv1</code>: Sends LMv1 only.
--- * <code>NTLMv1</code>: Sends NTLMv1 only (default).
--- * <code>v2</code>: Sends LMv2 and NTLMv2.
--- * <code>LMv2</code>: Sends LMv2 only.
---                   The default, <code>NTLMv1</code>, is a pretty
---                   decent compromise between security and compatibility. If you are paranoid, you might 
---                   want to use <code>v2</code> or <code>lmv2</code> for this. (Actually, if you're paranoid, you should be 
---                   avoiding this protocol altogether :P). If you're using an extremely old system, you 
---                   might need to set this to <code>v1</code> or <code>lm</code>, which are less secure but more compatible. 
 -----------------------------------------------------------------------
 
 author = "Ron Bowes"

scripts/smb-systeminfo.nse

@@ -39,33 +39,9 @@ I don't know it), so this doesn't support Vista at all.
 -- |  |_ Internet Explorer 7.0000
 -- |_ |_ Firefox 3.0.3 (en-US)
 -- 
---@args  smbusername The SMB username to log in with. The forms "DOMAIN\username" and "username@DOMAIN"
+-- @args smb* This script supports the <code>smbusername</code>,
---                   are not understood. To set a domain, use the <code>smbdomain</code> argument. 
+-- <code>smbpassword</code>, <code>smbhash</code>, <code>smbguest</code>, and
---@args  smbdomain   The domain to log in with. If you aren't in a domained environment, then anything
+-- <code>smbtype</code> script arguments of the <code>smb</code> module.
---                   will (should?) be accepted by the server. 
---@args  smbpassword The password to connect with. Be cautious with this, since some servers will lock
---                   accounts if the incorrect password is given. Although it's rare that the
---                   Administrator account can be locked out, in the off chance that it can, you could
---                   get yourself in trouble. 
---@args  smbhash     A password hash to use when logging in. This is given as a single hex string (32
---                   characters) or a pair of hex strings (both 32 characters, optionally separated by a 
---                   single character). These hashes are the LanMan or NTLM hash of the user's password,
---                   and are stored on disk or in memory. They can be retrieved from memory
---                   using the fgdump or pwdump tools. 
---@args  smbguest    If this is set to <code>true</code> or <code>1</code>, a guest login will be attempted if the normal one 
---                   fails. This should be harmless, but I thought I would disable it by default anyway
---                   because I'm not entirely sure of any possible consequences. 
---@args  smbtype     The type of SMB authentication to use. These are the possible options:
--- * <code>v1</code>: Sends LMv1 and NTLMv1.
--- * <code>LMv1</code>: Sends LMv1 only.
--- * <code>NTLMv1</code>: Sends NTLMv1 only (default).
--- * <code>v2</code>: Sends LMv2 and NTLMv2.
--- * <code>LMv2</code>: Sends LMv2 only.
---                   The default, <code>NTLMv1</code>, is a pretty
---                   decent compromise between security and compatibility. If you are paranoid, you might 
---                   want to use <code>v2</code> or <code>lmv2</code> for this. (Actually, if you're paranoid, you should be 
---                   avoiding this protocol altogether :P). If you're using an extremely old system, you 
---                   might need to set this to <code>v1</code> or <code>lm</code>, which are less secure but more compatible. 
 -----------------------------------------------------------------------