This commit is contained in:
Bernardo Damele 2010-03-04 17:38:00 +00:00
parent 5bd8504f21
commit 5209b5929f

View File

@ -448,8 +448,9 @@ $ svn checkout https://svn.sqlmap.org/sqlmap/trunk/sqlmap sqlmap-dev
</verb></tscreen> </verb></tscreen>
<p> <p>
Either way you downloaded sqlmap, you can update it to the latest If you download a source package (gzip, bzip2 or zip) or sqlmap from the
development version anytime by running: Subversion repository, you can update it to the latest development version
anytime by running:
<tscreen><verb> <tscreen><verb>
$ python sqlmap.py --update $ python sqlmap.py --update
@ -461,6 +462,27 @@ Or:
$ svn update $ svn update
</verb></tscreen> </verb></tscreen>
<p>
Viceversa if you download a binary package (deb, rpm or exe), the
update feature is disabled.
<p>
There are some differences between each package:
<itemize>
<item>The source packages (gzip, bzip2 and zip) have all features. They
contains the working copy from the Subversion repository updated at the
time the sqlmap new version has been released.
<item>The Debian and Red Hat installation packages (deb and rpm) are
compliant with the Linux distributions' packaging guidelines. This implies
that they do not support the update features and do not include
third-party softwares Churrasco (for token kidnapping, see below) and UPX.
<item>The Windows binary package (exe) can't update itself and does not
support the takeover out-of-band features because they rely on Metasploit
and Metasploit's msfconsole and msfcli are not supported on the native
Windows Ruby interpreter.
</itemize>
<sect>License and copyright <sect>License and copyright