go-connections
go-connections copied to clipboard
docker
Utility package to work with network connections
This introduce `PortMapping.String()` for (some) symmetry with `ParsePortSpec`
A minor inconsistency in error handling between two functions in the ``Port`` type. In the ``Int`` function, there is a comment suggesting that the error should be ignored: https://github.com/docker/go-connections/blob/fa09c952e3eadbffaf8afc5b8a1667158ba38ace/nat/nat.go#L80-L87 However,...
```go broker := func(to, from *net.TCPConn) { written, err := io.Copy(to, from) if err != nil { // If the socket we are writing to is shutdown with // SHUT_WR,...
```go read, err := proxyConn.Read(readBuf) // .... for i := 0; i != read; { written, err := proxy.listener.WriteToUDP(readBuf[i:read], clientAddr) if err != nil { return } i += written...
Alternative for https://github.com/docker/go-connections/pull/72. Relates to https://github.com/moby/moby/issues/41392 Due to race-conditions between containers starting and the Docker remote API being up, containers bind-mounting the docker-socket may cause the socket-path to be created...
- Related to https://github.com/docker/go-connections/pull/104 - `TestConfigServerExclusiveRootPools`: see https://github.com/docker/go-connections/blob/5cc4da5c08cd0df3e0a45da21ebd07e131109bd2/tlsconfig/config_test.go#L202-L205 - `TestConfigClientExclusiveRootPools`: see https://github.com/docker/go-connections/blob/5cc4da5c08cd0df3e0a45da21ebd07e131109bd2/tlsconfig/config_test.go#L566-L569 Both tests break with the following error: > Unable to verify certificate 1: x509: certificate signed by unknown...
In this https://github.com/docker/go-connections/blob/master/tlsconfig/config.go#L43, is said 'CBC cipher suites - will phase out in the future'. I want to know can the CBC cipher suites be phase out now. Or if...
We have this comment: https://github.com/docker/go-connections/blob/58542c764a1173ea3dac965d89146c931a2946f7/tlsconfig/config.go#L43 Perhaps it is time to go ahead and make good on that comment?
