@@ -448,8 +448,9 @@ $ svn checkout https://svn.sqlmap.org/sqlmap/trunk/sqlmap sqlmap-dev
448448</verb></tscreen>
449449
450450<p>
451- Either way you downloaded sqlmap, you can update it to the latest
452- development version anytime by running:
451+ If you download a source package (gzip, bzip2 or zip) or sqlmap from the
452+ Subversion repository, you can update it to the latest development version
453+ anytime by running:
453454
454455<tscreen><verb>
455456$ python sqlmap.py --update
461462$ svn update
462463</verb></tscreen>
463464
465+ <p>
466+ Viceversa if you download a binary package (deb, rpm or exe), the
467+ update feature is disabled.
468+
469+ <p>
470+ There are some differences between each package:
471+
472+ <itemize>
473+ <item>The source packages (gzip, bzip2 and zip) have all features. They
474+ contains the working copy from the Subversion repository updated at the
475+ time the sqlmap new version has been released.
476+ <item>The Debian and Red Hat installation packages (deb and rpm) are
477+ compliant with the Linux distributions' packaging guidelines. This implies
478+ that they do not support the update features and do not include
479+ third-party softwares Churrasco (for token kidnapping, see below) and UPX.
480+ <item>The Windows binary package (exe) can't update itself and does not
481+ support the takeover out-of-band features because they rely on Metasploit
482+ and Metasploit's msfconsole and msfcli are not supported on the native
483+ Windows Ruby interpreter.
484+ </itemize>
485+
464486
465487<sect>License and copyright
466488
0 commit comments