PenTest/sqlmap
1
0
Fork 0
mirror of https://github.com/sqlmapproject/sqlmap.git synced 2025-12-25 00:49:02 +00:00
Code Issues Projects Releases Wiki Activity

Minor bug fix to --dbms, updated user's manual

Browse Source
This commit is contained in:
Bernardo Damele
2009-07-09 11:05:24 +00:00
parent 4b622ed860
commit 24a3a23159
5 changed files with 2736 additions and 2782 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
doc/README.html
View File

@@ -1571,11 +1571,13 @@ At the moment the fully supported database management system are four:</P>
</UL>
</P>
<P>It is possible to force the name if you already know it so that sqlmap
will skip the fingerprint with an exception for MySQL to only identify if
it is MySQL &lt; 5.0 or MySQL &gt;= 5.0.
To avoid also this check you can provide instead <CODE>MySQL 4</CODE> or
<CODE>MySQL 5</CODE>.</P>
<P>It is possible to force the DBMS name if you already know it so that sqlmap
will skip the fingerprint with an exception for MySQL and Microsoft SQL
Server to only identify the version.
To avoid also this check you can provide instead <CODE>MySQL VERSION</CODE> or
<CODE>Microsoft SQL Server VERSION</CODE> where version is a valid version for
the DBMS, for instance <CODE>5.0</CODE> for MySQL and <CODE>2005</CODE> for
Microsoft SQL Server.</P>
<P>Example on a <B>PostgreSQL 8.3.5</B> target:</P>
<P>
<BLOCKQUOTE><CODE>

5457
doc/README.pdf
View File

File diff suppressed because it is too large Load Diff

12
doc/README.sgml
View File

@@ -1507,11 +1507,13 @@ At the moment the fully supported database management system are four:
</itemize>
<p>
It is possible to force the name if you already know it so that sqlmap
will skip the fingerprint with an exception for MySQL to only identify if
it is MySQL &lt; 5.0 or MySQL &gt;= 5.0.
To avoid also this check you can provide instead <tt>MySQL 4</tt> or
<tt>MySQL 5</tt>.
It is possible to force the DBMS name if you already know it so that sqlmap
will skip the fingerprint with an exception for MySQL and Microsoft SQL
Server to only identify the version.
To avoid also this check you can provide instead <tt>MySQL VERSION</tt> or
<tt>Microsoft SQL Server VERSION</tt> where version is a valid version for
the DBMS, for instance <tt>5.0</tt> for MySQL and <tt>2005</tt> for
Microsoft SQL Server.
Example on a <bf>PostgreSQL 8.3.5</bf> target: