#6 SOCKS Error, again

[Anonymous]

I still have the issue using TOR socks:

Attack thread 2 started
Attack thread 3 started
Attack thread 4 started
Attack thread 5 started
Attack thread 6 started
Attack thread 7 started
Attack thread 8 started
Attack thread 9 started
[ERROR]: Could not connect. 'ascii' codec can't decode byte 0xea in position 1: ordinal not in range(128).
[ERROR]: Could not connect. 'ascii' codec can't decode byte 0xea in position 1: ordinal not in range(128).
[ERROR]: Could not connect. 'ascii' codec can't decode byte 0xea in position 1: ordinal not in range(128).
Attack thread 10 started

[Motoma]

Hi there.

On the surface this appears to be an issue with the older SOCKS library I was using based off of Dan Haim's SocksiPy.

The latest version of Pyloris should not have this decoding problem, as it uses a Mario Vilas socksipy-branch.

If you are indeed using the latest release of Pyloris (3.1) along with it's socks.py module, please add the following lines to libloris.py after line 126 (at the same indentation level:
import traceback
traceback.print_exc()

This should print out a stack trace when the error is encountered. Post this trace and I will address the issue as best I can.

Thanks,
Motoma

[Motoma]

This bug is fixed in the current release.

[Motoma]

I found the source of this issue in the Socksipy module, and I have since become a maintainer for that project as well. If you find more issues in the SOCKS functionality, please do not hesitate to post them here.

[Anonymous]

error errno 10053

after a few starts a thread 200+

[Anonymous]

socket closed