Added and fixed README files

extra/udfhack/README.txt

@@ -0,0 +1,7 @@
+Files in this folder can be used to compile shared objects that define
+some user-defined functions for MySQL and PostgreSQL. They are licensed
+under the terms of the GNU Lesser General Public License and their
+compiled versions are available on the official sqlmap subversion
+repository[1].
+
+[1] https://svn.sqlmap.org/sqlmap/trunk/sqlmap/udf/

extra/udfhack/windows/README.txt

@@ -1,19 +1,25 @@
-1. Before compiling, certain enviroment variables have to be set, depending on the project used. for project lib_mysqludf_sys variables PLATFORM_SDK_DIR and MYSQL_SERVER_DIR have to be set, while for lib_postgresqludf_sys PLATFORM_SDK_DIR and POSTGRESQL_SERVER_DIR.
+Before compiling, certain enviroment variables have to be set,
+depending on the project used. For project lib_mysqludf_sys variables
+PLATFORM_SDK_DIR and MYSQL_SERVER_DIR have to be set, while for project
+lib_postgresqludf_sys variables PLATFORM_SDK_DIR and
+POSTGRESQL_SERVER_DIR.
+
+Variables:
 --------------------------------------------------------------------------
 Variable name			Variable description
 --------------------------------------------------------------------------
-PLATFORM_SDK_DIR		directory where the Platform SDK is installed
+PLATFORM_SDK_DIR		Directory where the Platform SDK is installed
-MYSQL_SERVER_DIR		directory where the MySQL is installed
+MYSQL_SERVER_DIR		Directory where the MySQL is installed
-POSTGRESQL_SERVER_DIR	directory where the PostgreSQL is installed
+POSTGRESQL_SERVER_DIR	Directory where the PostgreSQL is installed
 
-2. Procedure for setting environment variables:
+Procedure for setting environment variables:
 My Computer -> Properties -> Advanced -> Environment Variables
 User variables -> New
 
-3. Sample values:
+Sample values:
 --------------------------------------------------------------------------
-Variable name			Variable value 
+Variable name			Variable value
 --------------------------------------------------------------------------
 PLATFORM_SDK_DIR		C:\Program Files\Microsoft Platform SDK for Windows Server 2003 R2
 MYSQL_SERVER_DIR		C:\Program Files\MySQL\MySQL Server 5.1
-POSTGRESQL_SERVER_DIR	C:\Program Files\PostgreSQL\8.3
+POSTGRESQL_SERVER_DIR	C:\Program Files\PostgreSQL\8.4

lib/contrib/tokenkidnapping/README.txt

@@ -1,10 +1,11 @@
-Due to the anti-virus positive detection of executable stored inside this folder, 
+Due to the anti-virus positive detection of executable stored inside this
-we needed to somehow circumvent this. As from the plain sqlmap users perspective nothing
+folder, we needed to somehow circumvent this. As from the plain sqlmap
-has to be done prior to its usage by sqlmap, but if you want to have access to the
+users perspective nothing has to be done prior to its usage by sqlmap, but
-original executable use the decrypt functionality of the ../extra/cloak/cloak.py utility.
+if you want to have access to the original executable use the decrypt
+functionality of the ../extra/cloak/cloak.py utility.
 
 To prepare the executable to the cloaked form use this command:
 python ../extra/cloak/cloak.py -i Churrasco.exe
 
 To get back the original executable use this:
-python ../extra/cloak/cloak.py -d -i Churrasco.exe_
+python ../extra/cloak/cloak.py -d -i Churrasco.exe_

lib/contrib/upx/windows/README.txt

@@ -1,10 +1,11 @@
-Due to the anti-virus positive detection of executable stored inside this folder, 
+Due to the anti-virus positive detection of executable stored inside this
-we needed to somehow circumvent this. As from the plain sqlmap users perspective nothing
+folder,  we needed to somehow circumvent this. As from the plain sqlmap
-has to be done prior to its usage by sqlmap, but if you want to have access to the
+users perspective nothing has to be done prior to its usage by sqlmap, but
-original executable use the decrypt functionality of the ../../../../extra/cloak/cloak.py utility.
+if you want to have access to the original executable use the decrypt
+functionality of the ../../../../extra/cloak/cloak.py utility.
 
 To prepare the executable to the cloaked form use this command:
 python ../../../../extra/cloak/cloak.py -i upx.exe
 
 To get back the original executable use this:
-python ../../../../extra/cloak/cloak.py -d -i upx.exe_
+python ../../../../extra/cloak/cloak.py -d -i upx.exe_

shell/README.txt

@@ -1,10 +1,11 @@
-Due to the anti-virus positive detection of shell scripts stored inside this folder, 
+Due to the anti-virus positive detection of shell scripts stored inside
-we needed to somehow circumvent this. As from the plain sqlmap users perspective nothing
+this folder, we needed to somehow circumvent this. As from the plain
-has to be done prior to their usage by sqlmap, but if you want to have access to their
+sqlmap users perspective nothing has to be done prior to their usage by
-original source code use the decrypt functionality of the ../extra/cloak/cloak.py utility.
+sqlmap, but if you want to have access to their original source code use
+the decrypt functionality of the ../extra/cloak/cloak.py utility.
 
 To prepare the original scripts to the cloaked form use this command:
 find backdoor.* uploader.* -type f -exec python ../extra/cloak/cloak.py -i '{}' \;
 
 To get back them into the original form use this:
-find backdoor.*_ uploader.*_ -type f -exec python ../extra/cloak/cloak.py -d -i '{}' \;
+find backdoor.*_ uploader.*_ -type f -exec python ../extra/cloak/cloak.py -d -i '{}' \;

udf/README.txt

@@ -0,0 +1,6 @@
+Binary files in this folder are data files used by sqlmap on the target
+system, but not executed on the system running sqlmap. They are licensed
+under the terms of the GNU Lesser General Public License and their source
+code is available on the official sqlmap subversion repository[1].
+
+[1] https://svn.sqlmap.org/sqlmap/trunk/sqlmap/extra/udfhack/