Changeset 3269

Timestamp:

07/31/08 16:27:23 (5 years ago)

Author:

boltrix

Message:

Fixed a bug that was re-loading target and profile before scanning, overriding any manual changes made to the command. Working on scanning documentation also.

Location:

trunk

Files:

• share/doc/umit/help.html (modified) (1 diff)
• share/doc/umit/scanning/scanning.xml (modified) (1 diff)
• umitGUI/ScanNotebook.py (modified) (2 diffs)
• umitGUI/TargetCombo.py (modified) (1 diff)

trunk/share/doc/umit/help.html

@@ -16 +16 @@
 
       <ul>
-        <li><a href="nse_facilitator.html">NSE Facilitator</a></li>
         <li><a href="comparing_results.html">Comparing Results</a></li>
         <li><a href="profile_editor.html">Profile Editor</a></li>

trunk/share/doc/umit/scanning/scanning.xml

@@ -94 +94 @@
     <title>Conducting a scan</title>
     
-    <para># Selecting the profile</para>
-    <para># Customizing the command that is going to be executed</para>
+    <para>A profile is a set of options that is going to be used during the scan
+    process against the target(s) specified. Profiles are customizable through the
+    <emphasis>Profile Editor Window</emphasis>. After specifying a target, select
+    one of the profiles in the profile list, and watch the command in the field
+    get changed according to the profile selected. This is awesome if you always
+    have to run a scan with the same set of options. If you are a newbie, this is
+    awesome too, because you can use one of the preset profiles according to your
+    need.</para>
+    <para>Sometimes we need to fine tune a specific profile for a specific occasion
+    that is not likely to occour very often. In this case, it is not a good idea to
+    create a new profile, or to change an existing one. After selecting a target and 
+    a profile, you can customize the command that will actually run, by editing it
+    directly in the command field.</para>
+    <para>There is a known issue regarding</para>
     <para># Nmap Output refresh</para>
     <section>

trunk/umitGUI/ScanNotebook.py

@@ -345 +345 @@
         self.empty_target = _("<target>")
         
-        self.toolbar.target_entry.connect('changed', 
-            self.refresh_command_target)
+        self.toolbar.target_entry.changed_handler = self.toolbar.target_entry.\
+            connect('changed', self.refresh_command_target)
         self.toolbar.profile_entry.connect('changed', self.refresh_command)
 
@@ -486 +486 @@
             self.set_tab_label(profile)
 
-        if target != '':    
+        if target != '':
             self.toolbar.add_new_target(target)
+            
+            # TODO: Fix this workarround. The following line will set back the
+            # correct command to be executed after the refresh_command_target
+            # method that will be called by the targetcombo update method.
+            self.command_toolbar.command = command
 
         if (command.find("-iR") == -1 and command.find("-iL") == -1):

trunk/umitGUI/TargetCombo.py

@@ -33 +33 @@
         self.completion.set_model(self.get_model())
         self.completion.set_text_column(0)
+        self.changed_handler = None
 
         self.update()