Why it exists
µSOCKS5 was built as a small infrastructure experiment: a SOCKS5 proxy implementation that stays lightweight and resource-aware while remaining easy to run locally or in Docker.
Architecture
- The server listens on the standard SOCKS5 port 1080.
- Instead of spawning one thread per connection, it iterates over connection tuples.
- Pending data is forwarded incrementally in chunks.
- Docker support allows quick containerized execution.
- The current implementation focuses on TCP communications.
Key features
- Minimal SOCKS5 proxy implementation.
- Low-overhead connection handling.
- Docker and direct Python execution modes.
- Useful as a networking experiment and lightweight local proxy.
- Referenced from the SOCKS Wikipedia page among SOCKS proxy server implementations.
Design decisions
The most relevant design decision is the avoidance of a thread-per-connection model. The implementation favors a more controlled forwarding loop, which makes it interesting as a compact networking and resource-efficiency exercise.