go-connections
go-connections copied to clipboard
docker
Utility package to work with network connections
Currently, tlsconfig only works by loading PEM data from files. In some scenarios, we might not want to let tlsconfig load PEM data itself (e.g.: because it is not stored...
This error is reproducible with 0.3.0: ``` === RUN TestConfigServerTLSClientCASet --- FAIL: TestConfigServerTLSClientCASet (0.00s) panic: runtime error: invalid memory address or nil pointer dereference [recovered] panic: runtime error: invalid memory...
Go 1.7 added [x509.SystemCertPool()](https://golang.org/pkg/crypto/x509/#SystemCertPool). It'd be nice to support this in the TLS configs instead of the empty cert pool (perhaps optionally?) on go 1.7 builds using a build tag....
See moby/moby#36442 ---- This is a rebase of #98.
It currently returns error "protocol not supported" https://github.com/docker/go-connections/blob/5df8d2b30ca886f2d94740ce3c54abd58a5bb2c9/sockets/sockets_windows.go#L13 But modern Windows version support AF_UNIX https://devblogs.microsoft.com/commandline/af_unix-comes-to-windows/ and it can possibly be used as a transport for Docker or Docker compatible APIs...
