[ 
https://issues.apache.org/jira/browse/THRIFT-1692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13682245#comment-13682245
 ] 

Ben Craig commented on THRIFT-1692:
-----------------------------------

This has been fixed in the recent porting mega-patch
                
> SO_REUSEADDR allows for socket hijacking on Windows
> ---------------------------------------------------
>
>                 Key: THRIFT-1692
>                 URL: https://issues.apache.org/jira/browse/THRIFT-1692
>             Project: Thrift
>          Issue Type: Bug
>          Components: C++ - Library
>    Affects Versions: 0.8, 0.9
>         Environment: Worst on WinXP, slightly less bad on Win Server 2003+
>            Reporter: Ben Craig
>             Fix For: 1.0
>
>
> SO_REUSEADDR is a fine idea for sockets on POSIX operating systems. 
> SO_REUSEADDR on Windows operates differently though.  This MSDN article 
> explains the behavior:
> http://msdn.microsoft.com/en-us/library/windows/desktop/ms740621.aspx
> Long story short, with SO_REUSEADDR, a hostile process owned by another user 
> can steal your port.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to