From f8714ae9ffa40c3b9cbb6f821a2eead324100d8a Mon Sep 17 00:00:00 2001 From: david Date: Tue, 2 Nov 2010 17:46:41 +0000 Subject: [PATCH] Fix some documentation typos in rmi-dumpregistry.nse, split the first paragraph so the summary is shorter. --- scripts/rmi-dumpregistry.nse | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/scripts/rmi-dumpregistry.nse b/scripts/rmi-dumpregistry.nse index bc61814d0..37d47f11b 100644 --- a/scripts/rmi-dumpregistry.nse +++ b/scripts/rmi-dumpregistry.nse @@ -1,13 +1,16 @@ description = [[ -This script connects to ta remote RMI registry, and attempts to dump all objects from an RMI Registry. First it tries to +This script connects to a remote RMI registry and attempts to dump all +its objects. + +First it tries to determine the names of all objects bound in the registry, and then it tries to determine information about the objects, such as the the class names of the superclasses and interfaces. This may, depending on what the registry is used for, give -valuable information about the service. E.g, if the app uses JMX (Java Management eXtensions, you should see an object +valuable information about the service. E.g, if the app uses JMX (Java Management eXtensions), you should see an object called "jmxconnector" on it. It also gives information about where the objects are located, (marked with @:port in the output). -Some apps give away the classpath, which this scripts catches in so called "Custom data". +Some apps give away the classpath, which this scripts catches in so-called "Custom data". ]] -- @usage nmap --script "rmi-dumpregistry.nse" -p 1098