‫Here is an other example source of an end map script.
‫In addition to the code part, which is to execute the job of the script, it includes some additional
‫sections such as description categories, usage, author, license type, etc..
‫Instead of probing the script code to understand the details of an end map script, you can use script
‫that help parameter of in map command.
‫You will see the name, the categories, the link to deep search and the description sections as the
‫result of the script.
‫Dash helped query.
‫So you've heard me say before, but I really need to emphasize the importance of the service and version
‫detection once again in this and map scripting lecture.
‫As you know, if you don't run the version, detection and maps supposes that the default service is
‫running on that port.
‫In a script, scan and Maps opposes the default services running on the port, so it runs the scripts
‫as if they are suitable for that service.
‫It's easy to see it in an end map query.
‫OK, open a terminal screen and collie.
‫I use netstat command to see the listening ports as you see state services running, but it's not running
‫on Port 22.
‫Instead, it's running on Port 443 and as you know, four four three is the default port of the HTTPS
‫service.
‫So if I run a port scan for my colleagues Port 443 without adding the version detection option.
‫And Maps signs the port is running in service.
‫Now, if I had the same scripts in this query using script ss h asterisk.
‫Without diversion detection, not any of the scripts run because and Matt thinks that the service is
‫aged itbs, not as age and is not run the same age scripts.
‫So I call the latest map query and add version detection using the uppercase V this time.
‫Like that, associate scripts are started with a version detection option, and Map finds that the service
‫is sage and not HTTPS.
‫Very important.
‫OK, so sage root script takes a long time to run.
‫We already got the point, so no need to wait for the results of the scripts.