HelloZeroNet/ZeroNet

ZeroNet seems to bomb Tor's SOCKS port with non-SOCKS requests

Open

#1,243 opened on Jan 15, 2018

View on GitHub
 (5 comments) (1 reaction) (1 assignee)JavaScript (2,245 forks)batch import
help wanted

Repository metrics

Stars
 (18,200 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

I run ZeroNet in --tor always mode. When ZeroNet is running, a lot of such log records appear in Tor's log:

Jan 14 23:37:43.000 [warn] Socks version -125 not recognized. (This port is not an HTTP proxy; did you want to use HTTPTunnelPort?)
Jan 14 23:37:43.000 [warn] Fetching socks handshake failed. Closing.

Stopping ZeroNet stops these errors too. zeronet-0.6.0 tor-0.3.2.9 FreeBSD 11.1

Contributor guide

Research direction
Inspect the code that handles outgoing connections via Tor to ensure it properly uses the SOCKS protocol instead of sending raw HTTP or other non SOCKS traffic to the SOCKS port.
Tech stack
python
Domain
backend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
PythonSOCKS protocol basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
45