What steps will reproduce the problem? 1. successfully cracked WPA2 key 2. delete_essid successfully completes that command 3. disk space remains the same
What is the expected output? What do you see instead? Pyrit is NOT removing the data from the DB, I need that disk space back. 30GB per ESSID adds up, I need that space back, I need delete_essid to actually delete the ESSID and all data associated with it.
What version of the product are you using? On what operating system? Debian 6 Pyrit svn r308
Comment #1
Posted on Mar 14, 2012 by Happy Giraffeyour better using innodb_file_per_table = 1, that way you can delete each individual table if need be.
You will need truncate the results table to to remove the data from it.
Status: New
Labels:
Type-Defect
Priority-Medium