diff options
| author | Nick Mathewson <nickm@torproject.org> | 2012-05-24 16:57:36 -0400 |
|---|---|---|
| committer | Nick Mathewson <nickm@torproject.org> | 2012-05-24 16:57:36 -0400 |
| commit | 9d41629aa072b389332273a21926260c302b49e1 (patch) | |
| tree | 9f68fd91ea568ccf2ab685b28d46bf550e4a08d7 /changes/bug5374 | |
| parent | 75fc4dbbcabaedc715f0f9e883ccab1c9634e787 (diff) | |
| download | tor-9d41629aa072b389332273a21926260c302b49e1.tar tor-9d41629aa072b389332273a21926260c302b49e1.tar.gz | |
Delay getsockname() call until after connect() is done
On Windows, getsockname() on a nonblocking apparently won't work
until the connection is done connecting. On XP, it seems to fail by
reporting success and declaring that your address is INADDR_ANY. On the
Win8 preview, though, it fails more loudly and says WSAEINVAL.
Fix for bug 5374; bugfix on 0.1.1.14-alpha.
Diffstat (limited to 'changes/bug5374')
| -rw-r--r-- | changes/bug5374 | 7 |
1 files changed, 7 insertions, 0 deletions
diff --git a/changes/bug5374 b/changes/bug5374 new file mode 100644 index 000000000..926a07490 --- /dev/null +++ b/changes/bug5374 @@ -0,0 +1,7 @@ + o Minor bugfixes: + + - Don't check for whether the address we're using for outbound + connections has changed until after the outbound connection has + completed. On Windows, getsockname() doesn't succeed until the + connection is finished. Fix for bug 5374; bugfix on + 0.1.1.14-alpha. |