New Version #30
Comments
|
yes, but i was hoping to get some feedback on it first since i didn't test it extensively. |
|
Will UDP support be added in the next update? @rofl0r |
no, that's not really in my TODO list. the number of applications that can only be used via UDP and support a socks server can be counted on one hand. if someone else does the work and the quality is sufficient it may at some point be added though. |
parke
added a commit
to parke/microsocks
that referenced
this issue
Dec 12, 2021
If `-b bindaddr` is used, then created sockets must be of the same address family as `bindaddr` (otherwise, calls to `bind()` will fail). This patch harmonizes the address family across the calls to `socket()`, `bind()`, and `connect()`. Prior to this patch, `microsocks` would use the first `addrinfo` record returned by `getaddrinfo()`. On systems with both IPv4 and IPv6, sometimes the address family of the first record would be a mismatch with `bindaddr`, resulting in an error. This patch may fix issue rofl0r#30. (And issue rofl0r#40?)
parke
added a commit
to parke/microsocks
that referenced
this issue
Dec 12, 2021
If `-b bindaddr` is used, then created sockets must be of the same address family as `bindaddr` (otherwise, calls to `bind()` will fail). This patch harmonizes the address family across the calls to `socket()`, `bind()`, and `connect()`. Prior to this patch, `microsocks` would use the first `addrinfo` record returned by `getaddrinfo()`. On systems with both IPv4 and IPv6, sometimes the address family of the first record would be a mismatch with `bindaddr`, resulting in an error. This patch may fix issue rofl0r#30. (And issue rofl0r#40?)
rofl0r
pushed a commit
that referenced
this issue
Dec 13, 2021
If `-b bindaddr` is used, then created sockets must be of the same address family as `bindaddr`, otherwise, calls to `bind()` will fail. This patch harmonizes the address family across the calls to `socket()`, `bind()`, and `connect()`. Prior to this patch, `microsocks` would use the first `addrinfo` record returned by `getaddrinfo()`. On systems with both IPv4 and IPv6, sometimes the address family of the first record would be a mismatch with `bindaddr`, resulting in an error. Fixes #30. (And possibly #40)
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
@rofl0r - will you be tagging the new changes to
pollwith a new version?The text was updated successfully, but these errors were encountered: