@@ -105,9 +105,9 @@ <H2><A NAME="ss1.1">1.1</A> <A HREF="#toc1.1">Requirements</A>
105
105
Windows users can download and install the Python setup-ready installer
106
106
for x86, AMD64 and Itanium too.</ P >
107
107
< P > sqlmap relies on the
108
- < A HREF ="http://metasploit.com/framework/ "> Metasploit Framework</ A > for some of its post-exploitation takeover
108
+ < A HREF ="http://metasploit.com "> Metasploit Framework</ A > for some of its post-exploitation takeover
109
109
features. You need to grab a copy of it from the
110
- < A HREF ="http://metasploit.com/framework/ download/ "> download</ A >
110
+ < A HREF ="http://metasploit.com/download/ "> download</ A >
111
111
page - the required version is < B > 3.5</ B > or higher.
112
112
For the ICMP tunneling out-of-band takeover technique, sqlmap requires
113
113
< A HREF ="http://corelabs.coresecurity.com/index.php?module=Wiki&action=view&type=tool&name=Impacket "> Impacket</ A > library too.</ P >
@@ -418,7 +418,7 @@ <H2><A NAME="ss2.1">2.1</A> <A HREF="#toc2.1">Generic features</A>
418
418
message to the user.
419
419
</ LI >
420
420
< LI > Integration with other IT security open source projects,
421
- < A HREF ="http://metasploit.com/framework/ "> Metasploit</ A > and
421
+ < A HREF ="http://metasploit.com "> Metasploit</ A > and
422
422
< A HREF ="http://w3af.sourceforge.net/ "> w3af</ A > .</ LI >
423
423
</ UL >
424
424
</ P >
@@ -727,7 +727,7 @@ <H2><A NAME="ss3.4">3.4</A> <A HREF="#toc3.4">2008</A>
727
727
< LI > < B > October 20</ B > , sqlmap first point release, < B > 0.6.1</ B > , goes
728
728
public. This includes minor bug fixes and the first contact between the
729
729
tool and
730
- < A HREF ="http://metasploit.com/framework "> Metasploit</ A > :
730
+ < A HREF ="http://metasploit.com "> Metasploit</ A > :
731
731
an auxiliary module to launch sqlmap from within Metasploit Framework.
732
732
The
733
733
< A HREF ="https://svn.sqlmap.org/sqlmap/trunk/sqlmap/ "> subversion development repository</ A > goes public again.
@@ -1445,16 +1445,16 @@ <H3>Output prediction</H3>
1445
1445
< P > Switch: < CODE > -</ CODE > < CODE > -predict-output</ CODE > </ P >
1446
1446
1447
1447
< P > This switch is used in inference algorithm for sequential statistical
1448
- prediction of characters of value being retrieved. Based on items given in
1449
- < CODE > txt/common-outputs.txt </ CODE > together with the knowledge of current
1450
- enumeration used statistical table with the most promising values is being
1451
- built . In case that the value can be found among the common output values,
1452
- as the process progresses, subsequent character tables are being narrowed
1453
- more and more. If used in combination with retrieval of common DBMS
1454
- entities, as with system table names and privileges, speed up is
1455
- significant. Of course, you can edit the common outputs file according to
1456
- your needs if, for instance, you notice common patterns in database table
1457
- names or similar.</ P >
1448
+ prediction of characters of value being retrieved. Statistical table with
1449
+ the most promising character values is being built based on items given in
1450
+ < CODE > txt/common-outputs.txt </ CODE > combined with the knowledge of current
1451
+ enumeration used . In case that the value can be found among the common
1452
+ output values, as the process progresses, subsequent character tables are
1453
+ being narrowed more and more. If used in combination with retrieval of
1454
+ common DBMS entities, as with system table names and privileges, speed up
1455
+ is significant. Of course, you can edit the common outputs file according
1456
+ to your needs if, for instance, you notice common patterns in database
1457
+ table names or similar.</ P >
1458
1458
1459
1459
< P > Note that this switch is not compatible with < CODE > -</ CODE > < CODE > -threads</ CODE >
1460
1460
switch.</ P >
@@ -1507,9 +1507,8 @@ <H3>Concurrent HTTP(S) requests</H3>
1507
1507
when that character is retrieved - it takes up to 7 HTTP(S) requests with
1508
1508
the bisection algorithm implemented in sqlmap.</ P >
1509
1509
1510
- < P > Note that the multi-threading switch does not affect any other SQL
1511
- injection technique. The maximum number of concurrent requests is set to
1512
- < B > 10</ B > for performance and site reliability reasons.</ P >
1510
+ < P > The maximum number of concurrent requests is set to < B > 10</ B > for
1511
+ performance and site reliability reasons.</ P >
1513
1512
1514
1513
< P > Note that this switch is not compatible with
1515
1514
< CODE > -</ CODE > < CODE > -predict-output</ CODE > switch.</ P >
@@ -1682,7 +1681,7 @@ <H3>Tamper injection data</H3>
1682
1681
from lib.core.enums import PRIORITY
1683
1682
1684
1683
# Define which is the order of application of tamper scripts against the payload
1685
- __priority__ = PRIORITY.HIGHEST
1684
+ __priority__ = PRIORITY.NORMAL
1686
1685
1687
1686
def tamper(payload):
1688
1687
'''
@@ -1691,8 +1690,9 @@ <H3>Tamper injection data</H3>
1691
1690
1692
1691
retVal = payload
1693
1692
1694
- # your code to tamper the original payload (retVal)
1693
+ # your code to tamper the original payload
1695
1694
1695
+ # return the tampered payload
1696
1696
return retVal
1697
1697
</ PRE >
1698
1698
</ CODE > </ BLOCKQUOTE >
@@ -1701,12 +1701,12 @@ <H3>Tamper injection data</H3>
1701
1701
< P > You can check valid and usable tamper scripts in the < CODE > tamper/</ CODE >
1702
1702
directory.</ P >
1703
1703
1704
- < P > Example against a MySQL target assuming < CODE > ></ CODE > character, spaces and
1705
- < CODE > SELECT</ CODE > string are banned:</ P >
1704
+ < P > Example against a MySQL target assuming that < CODE > ></ CODE > character,
1705
+ spaces and capital < CODE > SELECT</ CODE > string are banned:</ P >
1706
1706
< P >
1707
1707
< BLOCKQUOTE > < CODE >
1708
1708
< PRE >
1709
- $ python sqlmap.py -u "http://debiandev /sqlmap/mysql/get_int.php?id=1" --tamper \
1709
+ $ python sqlmap.py -u "http://192.168.136.131 /sqlmap/mysql/get_int.php?id=1" --tamper \
1710
1710
tamper/between.py,tamper/randomcase.py,tamper/space2comment.py -v 3
1711
1711
1712
1712
[hh:mm:03] [DEBUG] cleaning up configuration parameters
@@ -1816,7 +1816,7 @@ <H3>Page comparison</H3>
1816
1816
This way the distinction will be based upon string presence or regular
1817
1817
expression match.</ P >
1818
1818
1819
- < P > In cases with lot of active (e.g. scripts, embeds, etc.) content in the
1819
+ < P > In cases with lot of active content (e.g. scripts, embeds, etc.) in the
1820
1820
HTTP responses' body, you can filter pages (< CODE > -</ CODE > < CODE > -text-only</ CODE >
1821
1821
switch) just for their textual content. This way, in a good number of
1822
1822
cases, you can automatically tune the detection engine.</ P >
@@ -2987,7 +2987,7 @@ <H3>Replicate dumped data into a sqlite3 database</H3>
2987
2987
2988
2988
< P > You can then use sqlmap itself to read and query the locally created
2989
2989
SQLite 3 file. For instance, < CODE > python sqlmap.py -d
2990
- sqlite:///tmp/sqlmap/output/debiandev /dump/testdb.sqlite3 --table</ CODE > .</ P >
2990
+ sqlite:///tmp/sqlmap/output/192.168.136.131 /dump/testdb.sqlite3 --table</ CODE > .</ P >
2991
2991
2992
2992
2993
2993
< H3 > Simple wizard interface for beginner users</ H3 >
0 commit comments