You can clone with
HTTPS or Subversion.
Fix up comment splats with the correct URI
See the complaint on #4039. This doesn't fix that particular
issue (it's somewhat unrelated), but does solve around
a file parsing problem reported by @void-in
Land #2791, @morisson's support to remote dns resolution on sap_route…
Use RHOST, RPORT for the SAPROUTER options
Switch RHOSTS to TARGETS and add validation
fixed typo: innacurated -> inaccurate
Fixed default value for RESOLVE (local)
Cleanup, also split IP addresses separated by commas.
Prevent report_* when RESOLVE is remote, since hostname may be unknow…
…n and local resolution fail, thus spitting out an error and failing
Unreachable and time out error identification
commented out response packet vprint
RHOSTS can be a comma separated list of hostnames
msftidy - fixed
Dropped scanner mixin. Tried to maintain usage
RESOLVE option takes either "remote" or "local"
Keeping changes away from the "ip" variable
Option to perform host resolution on remote saprouter
Raise Msf::OptionValidateError when the PORTS option is invalid
Instead of print_error for invalid ports, modules should be raising
Msf::OptionValidateError to warn the user about the invalid input.
Redo the boilerplate / splat
Make msftidy happy
Add final cleanup for #2012
output as table, added info on ports, added comment with default port…
…s. msftidy cleanup.
output as table, added info on ports, added comment with default ports
added INSTANCES option, and support for it on PORTS
Added feedback, cleanup, and simplified modes
changed 2 vprint_error to print_error
added sap_router_portscanner module