Can you show some exemple?

Hi,

I love this library, but it looks like you did not have the time to maintain it the last couple of years... there are a few open pull requests and a lot of forks where people fix smaller issues.

Do you need help? I'd be willing to clean this up and consolidate everything, please let me know!

Thanks for your work!

Hi
I need get all request headers. Please write example code. Thanks

2|socket5 | 2020/08/18 21:23:00 [ERR] socks: Failed to handle request: readfrom tcp 16.24.177.51:59642->172.67.80.44:80: splice: connection reset by peer
2|socket5 | 2020/08/18 21:23:01 [ERR] socks: Failed to handle request: readfrom tcp 16.24.177.51:39608->172.67.80.44:443: splice: connection reset by peer

with readme demo

It crashes when using custom net.conn implementation that does not return net.TCPAddr when con.LocalAddr()

Crash example

panic: interface conversion: net.Addr is net.pipeAddr, not *net.TCPAddr

goroutine 7 [running]:
github.com/armon/go-socks5.(*Server).handleConnect(0xc00019a320, {0xfe4fd0, 0xc00009e0d0}, {0x1aae30650d8, 0xc000006020}, 0xc0002d2040)
	C:/Users/aymerici/go/pkg/mod/github.com/armon/[email protected]/request.go:194 +0x950

The problem is in this Line

	local := target.LocalAddr().(*net.TCPAddr)

Would you like to add support for intercepting proxied traffic, for example, for getting statistics, creating limits and so one.

I can create pull request with this changes or I should to create my own fork?

Thanks.

This library has socket leaks. When running it for a long time with real human traffic, it will end-up like this:

2020/09/21 08:40:19 [ERR] socks: Failed to handle request: Connect to xxx.xxx.xxx.xxx:443 failed: dial tcp xxx.xxx.xxx.xxx:443: socket: too many open files
panic: accept tcp [::]:4080: accept4: too many open files

Udp support it ? How?

I want to parse by remote
Local can not be resolved

see https://github.com/armon/go-socks5/blob/master/request.go#L124-L134

Hi , have you begin with the future features?

Thanks

does this support UDP ? or tcp only

I am not as familar with go as I would like to be. I was wondering if there was anyway to handle closing of the socks5 server?

I have seen examples like:

http://www.hydrogen18.com/blog/stop-listening-http-server-go.html

and

https://rcrowley.org/articles/golang-graceful-stop.html

Was wondering if it would be possible to do the same with the socks5 server?

It seems this project attracts a lot of attention since this is the 1st hit if you search "go socks5", but be warned this is not what you're looking for, for example:

https://github.com/armon/go-socks5/blob/master/socks5.go#L127

I don't want go to details, but TCP is a stream protocol, there is no guarantee the first Read will only read the 1st byte magically, this is just plain wrong.

I am currently testing your libary in a project and it works great so far, thanks for your work!

I noticed that it writes to stdout (via log in request.go/proxy(), see here), breaking the output of programs using it.

Is it possible to remove that or to make it configurable?

// proxy is used to suffle data from src to destination, and sends errors
// down a dedicated channel
func proxy(dst io.Writer, src io.Reader, errCh chan error) {
_, err := io.Copy(dst, src)
if tcpConn, ok := dst.(closeWriter); ok {
tcpConn.CloseWrite()
}
errCh <- err
}

when i try use it as socks4 server it gives me that error: Unsupported SOCKS version: [4]
Will that be added in the future updates?

Is there a way to have a client connecting to a public ip on the server browse the internet using the same ip?

For example I have a server with a public /24 attached to it. and I want client1 to only have access to 23.8.22.3 and also browse the internet using that ip.

client1 connects to the socks using host 23.8.22.3 and checks his ip on a website which also shows 23.8.22.3.

When trying to use the socks5 proxy (with Chrome on a Mac), it fails with this error message:

[ERR] socks: Failed to authenticate: No supported authentication mechanism

I had set the System Preferences on the Mac to use the SOCKS Proxy, and I provided the user and password. The proxy was clearly being contacted, but the authentication step was failing.

Here is the code that attempts to configure socks5 to use the UserPassAuthenticator.

package main

import socks5 "github.com/armon/go-socks5"

func main() {
	cred := socks5.StaticCredentials{"user": "pass"}
	conf := &socks5.Config{Credentials: cred}
	server, err := socks5.New(conf)
	if err != nil {
		panic(err)
	}
	err = server.ListenAndServe("tcp", "127.0.0.1:8000")
	if err != nil {
		panic(err)
	}
}

Can anyone give a simple example showing how UserPassAuthenticator can be used with Chrome/Safari browsers on a Mac?

there is mention of Custom DNS resolution in the readme but there is no documentation on using this.

In short, I want to make it possible for the proxy to hand off the connection to some go code to handle, rather than always proxy it out.

I know server.Dial exists, but I think thats a little messy + lots of wrapping+unwrapping layers of abstraction (for this use case).

1. The client connects to the proxy and issues a connect for a specific endpoint.
2. The connect request matches some internal state indicating it should be hijacked.
3. The server proceeds as normal, except instead of opening the remote connection and proxying the data, it passes off the net.Conn to a callback.

In my use case, I pass the net.Conn to a http.Server and serve proxy status pages.

I am happy to code this and send a PR, just wanted to make sure this is okay with you.

It would be nice if there was a channel to send a message to stop the server.

e.g. I want to run it as part of a larger app that occasionally and intermittently needs to offer a socks server. When the need is gone, I would like to shit it down.

I suppose I can pull and modify it...

It would be great to have an ability to log every request server processing.

I've been looking at how to create a replacement of ocproxy which sets up a socks5 proxy in front of openconnect. Openconnect talks to ocproxy via a unix socket. Are there any plans to support a unix socket for the local address?