Describe the bug
When I try to dump a target, and the tool starts attempting to crack passwords hashes, every attempt generates [10:07:03] [CRITICAL] there was a problem while hashing entry: '!N33D@B' ('AttributeError: 'StreamHandler' object has no attribute 'colorize''). Please report by e-mail to 'dev@sqlmap.org'
To Reproduce
Run a --dump or --dump-all scan in cmd with disable-coloring on a target where you can exfiltrate and crack passwords. When the process reaches the hash cracking stage the error should manifest itself.
See relevant_info.txt for detailed guide on commands used and how to replicate enviroment.
Expected behavior
I expected it to perform the same as with color enabled or when I save the result directly to file.
See manually_saved_output_with_coloring_enabled and directly_saved_output for expected behavior.
Screenshots
N/A
Running environment:
- sqlmap version 1.10.9.12#dev
- Installation method github clone
- Operating system: Windows 10 Pro
- Python version 3.14
Target details:
vulnerables/web-dvwa docker image
Additional context
Here I have 4 txt files. One is called manually_saved_output_with_coloring_disabled, where I copied my stdout showing the errors, then you have manually_saved_output_with_coloring_enabled, where you can see the expected behaviour, directly_saved_output is an example of the same command that generated the error in stdout working correctly and relevant_info contains all the relevant info of how to replicate enviroment and error with the commands I specifically used
directly_saved_output.txt
manually_saved_output_with_coloring_disabled.txt
manyally_saved_output_with_coloring_enabled.txt
relevant_info.txt
Describe the bug
When I try to dump a target, and the tool starts attempting to crack passwords hashes, every attempt generates
[10:07:03] [CRITICAL] there was a problem while hashing entry: '!N33D@B' ('AttributeError: 'StreamHandler' object has no attribute 'colorize''). Please report by e-mail to 'dev@sqlmap.org'To Reproduce
Run a --dump or --dump-all scan in cmd with disable-coloring on a target where you can exfiltrate and crack passwords. When the process reaches the hash cracking stage the error should manifest itself.
See relevant_info.txt for detailed guide on commands used and how to replicate enviroment.
Expected behavior
I expected it to perform the same as with color enabled or when I save the result directly to file.
See manually_saved_output_with_coloring_enabled and directly_saved_output for expected behavior.
Screenshots
N/A
Running environment:
Target details:
vulnerables/web-dvwa docker image
Additional context
Here I have 4 txt files. One is called manually_saved_output_with_coloring_disabled, where I copied my stdout showing the errors, then you have manually_saved_output_with_coloring_enabled, where you can see the expected behaviour, directly_saved_output is an example of the same command that generated the error in stdout working correctly and relevant_info contains all the relevant info of how to replicate enviroment and error with the commands I specifically used
directly_saved_output.txt
manually_saved_output_with_coloring_disabled.txt
manyally_saved_output_with_coloring_enabled.txt
relevant_info.txt