Unable to decode arabic font of hex output oracle DB
04:11:07] [INFO] retrieved:
[04:11:08] [INFO] retrieved: \xc7\xe1\xda\xe1\xc7\xe6\xc9 \xc7\xe1\xc5\xcc\xca\xe3\xc7\xda\xed\xc9 \xe6\xc7\xe1\xc3\xe6\xe1\xc7\xcf
[04:11:08] [INFO] retrieved:
[04:11:08] [INFO] retrieved: 25-MAY-04
[04:11:09] [INFO] retrieved: 0411841
[04:11:09] [INFO] retrieved:
[04:11:09] [INFO] retrieved:
[04:11:10] [INFO] retrieved: \xca\xe3 \xd1\xdd\xd6 \xc7\xe1\xc5\xde\xca\xd1\xc7\xcd
[04:11:11] [INFO] retrieved:
[04:11:11] [INFO] retrieved: \xe3\xcd\xe3\xcf
[04:11:42] [INFO] retrieved: \xe3\xe4\xd5\xe6\xd1
Do you have any idea for it? or whats is the problem?
Best Regards,
shahzadmuh
Can you please first retrieve the latest revision? I pushed one minor patch related.
Then rerun everything with --fresh-queries --encoding=windows-1256? I assume that you are using Linux, as Windows console in most cases can't do this kind of stuff
@stamparm Thanks a lot, again i have same issue in linux and win. i test --fresh-queries --encoding=windows-1256 win 10 with latest version SQLMAP,
As said, Windows console is not a good option for displaying non-ASCII chars. Please retry in Linux (e.g. Kali)
@shahzadmuh
Try to run in powershell, in should (better) support unicode.
I run in Linux and Win (Poewrshell) i get same issue, with minor patch @stamparm
As you have an error based SQLi, you could make a traffic file (-t traffic.txt --fresh-queries) and send it to me ([email protected])
@stamparm please check your email sended,
Please send the traffic file for whole dump (... --dump -t traffic.txt --fresh-queries), not just a dummy sqlmap run. Or at least just let it dump until the first hex encoded chars start. Then press Ctrl-C and send it to me. Without useful traffic file I can't do anything
Hi @stamparm .
i test in python3 with encoding "cp1256" so i test with --encoding sqlmap i get same issue, please check agein of your patch
>>> d = b"\xcd\xd3\xed\xe4\xda\xe1\xec\xe4\xe6\xc7\xdd\xc7\xe1\xda\xe4\xd2\xec"
>>> d.decode("cp1256")
'حسينعلىنوافالعنزى'
Done. It should be ok now
@stamparm Yeah, Fixed Thanks,
@shahzadmuh @stamparm excuse me, what was the solution to that problem cause I'm stuck with the same problem.
@saifeldeeny explicit stating of encoding with usage of --encoding (e.g. --fresh-queries --encoding=windows-1256). Also, latest revision of sqlmap has to be used
Most helpful comment
Done. It should be ok now