You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sqlmap overwrite previous dumped table if start the same scan again, needed a switch which let deside user verwrite or not
If i dump table for example named "test" where are 70.000 entries and start dump the same table or use --dump-all, sqlmap got stucked on this table for long time, needed to skip already full dumped tables, and if a table not full dumped then start dump from last entry
If OS where running python is restarting, shutdown or get Blue Screen of Death, now imaging what sqlmap runned for dumping 1 tables with 1.000.000 entries and do this for last 5 days, and dump most of them but not all, so when start sqlmap after thoose issues sqlmap cant resume scaning, because sqlmap in this way do everithing from beginning. But session.sqlite seems like contain already dumped info but ..... So needed what sqlmap saving to dump file not to session.sqlite each 10 min and not waiting for full dump to save results to file.
The text was updated successfully, but these errors were encountered:
and if a table not full dumped then start dump from last entry -> sqlmap resumes queries stored in session file to minimize number of repeated requests. We can't use "resume from last entry" as sqlmap sees everything as query<->reply
can't write to a dump file before the last row is retrieved because of formatting and filtering.
I can feel your frustration, but writing a partial table dump which would be totally different from the end formatted and filtered output would just start new issues.
The text was updated successfully, but these errors were encountered: