sqlmap version: 1.0-dev (r4542)
Python version: 2.6.5
Operating system: posix
Command line: ./sqlmap.py -u ***************************************
--batch --privileges --forms --technique=U -pXXXXXX --dump -T ****** -D
****************
Technique: UNION
Back-end DBMS: MySQL (fingerprinted)
Traceback (most recent call last):
File "/pentest/database/sqlmap/_sqlmap.py", line 86, in main
start()
File "/pentest/database/sqlmap/lib/controller/controller.py", line 580,
in start
action()
File "/pentest/database/sqlmap/lib/controller/action.py", line 109, in
action
conf.dbmsHandler.dumpTable()
File "/pentest/database/sqlmap/plugins/generic/enumeration.py", line
1774, in dumpTable
attackDumpedTable()
File "/pentest/database/sqlmap/lib/utils/hash.py", line 366, in
attackDumpedTable
results = dictionaryAttack(attack_dict)
File "/pentest/database/sqlmap/lib/utils/hash.py", line 721, in
dictionaryAttack
conf.hashDB.write(hash_, word)
File "/pentest/database/sqlmap/lib/utils/hashdb.py", line 79, in write
self.flush()
File "/pentest/database/sqlmap/lib/utils/hashdb.py", line 94, in flush
self.beginTransaction()
File "/pentest/database/sqlmap/lib/utils/hashdb.py", line 111, in
beginTransaction
self.cursor.execute('BEGIN TRANSACTION')
OperationalError: cannot start a transaction within a transaction
This error seemed to occur after the cracking press had successfully
completed.
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure
contains a definitive record of customers, application performance,
security threats, fraudulent activity, and more. Splunk takes this
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
_______________________________________________
sqlmap-users mailing list
sqlmap-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sqlmap-users
