diff --git a/doc/ChangeLog b/doc/ChangeLog index 1a3cb438d..860921e1a 100644 --- a/doc/ChangeLog +++ b/doc/ChangeLog @@ -21,6 +21,8 @@ sqlmap (0.9-1) stable; urgency=low * Added support to fetch unicode data (Bernardo and Miroslav). * Added support to use persistent HTTP(s) connection for speed improvement, --keep-alive switch (Miroslav). + * Implemented several optimization switches to speed up the exploitation + of SQL injections (Bernardo and Miroslav). * Support to test and inject against HTTP Referer header (Miroslav). * Implemented HTTP(s) proxy authentication support, --proxy-cred switch (Miroslav). diff --git a/doc/README.html b/doc/README.html index ae8ab131e..ef1899571 100644 --- a/doc/README.html +++ b/doc/README.html @@ -359,8 +359,9 @@ list of specific parameter(s) to test.
Cookie header string support, useful when the
web application requires authentication based upon cookies and you have
@@ -1051,21 +1052,28 @@ Options:
This switch can be used to set the verbosity level of output messages. There exist seven levels of verbosity. -The default level is 1 in which information, warning, error and critical messages and Python tracebacks (if any occur) will be displayed.
+The default level is 1 in which information, warning, error and +critical messages and Python tracebacks (if any occur) will be displayed.
0: Show only Python tracebacks, error and critical messages.1: Show also information and warning messages.2: Show also debug messages.3: Show also payloads injected.4: Show also HTTP requests.5: Show also HTTP responses' headers.6: Show also HTTP responses' page content.A reasonable level of verbosity to further understand what sqlmap does under the hood is level 2, primarily for the detection phase and the take-over functionalities. Whereas if you want to see the SQL payloads the tools sends, level 3 is your best choice. -In order to further debug potential bugs or unexpected behaviours, we recommend you to set the verbosity to level 4 or above. This level is recommended to be used when you feed the developers with a bug report too.
+A reasonable level of verbosity to further understand what sqlmap does +under the hood is level 2, primarily for the detection phase and +the take-over functionalities. Whereas if you want to see the SQL payloads +the tools sends, level 3 is your best choice. +In order to further debug potential bugs or unexpected behaviours, we +recommend you to set the verbosity to level 4 or above. This +level is recommended to be used when you feed the developers with a bug +report too.
Switch: -u or --url
Run sqlmap against a single target URL. This switch requires an argument
-which is the target URL in the form http(s)://targeturl/[...].
http(s)://targeturl[:port]/[...].
Switch: -o
This switch is an alias that implicitly sets the following:
+This switch is an alias that implicitly sets the following switches:
--keep-aliveRead below for details about every single switch.
+Read below for details about each switch.
If, for any reason, this operation fails, try with a manual svn
-update from your sqlmap working copy. It will perform the exact same
-operation of switch --update.
+
If, for any reason, this operation fails, run svn update from
+your sqlmap working copy. It will perform the exact same operation of
+switch --update.
If you are running sqlmap on Windows, you can use the TartoiseSVN client
-by right-clicking in Windows Explorer into your local sqlmap working copy
-and Update.
Update.
+
+This is strongly recommended before reporting any bug to the +mailing lists.