lkml.org 
[lkml]   [1999]   [Sep]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    From
    Date
    SubjectRe: tcp/ip bug (2.2.12) or telnet client bug


    Craig Milo Rogers wrote:


    >Statement of Problem
    >========= == =======
    > When the application opens a TCP connection without specifying
    > a local port number, the system will sometimes assign the same
    > local port number as the foreign port number in the connection,
    > creating an open, looped connection if the local and foreign IP
    > adresses are the same. The application programmer expected the
    > connection to fail, as the specified "foreign" port did not
    > exist prior to the attempt to open the "local" port and connection.
    >
    >Note that the question isn't, "Should explicitly requested TCP
    >self-connections be allowed?". Rather, it is, "Should unintentional
    >TCP self-connects be prevented?"

    It happened after:

    fd= socket( AF_INET, SOCK_STREAM, 0);
    .....
    /* NO BIND HERE */
    .....
    (void ) connect( fd, address, size);

    Question is: why that socket accepted connection from itself if that socket
    was not in LISTEN state ???? If that happened then that is the bug.

    Sergey Tsybanov







    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.rutgers.edu
    Please read the FAQ at http://www.tux.org/lkml/

    \
     
     \ /
      Last update: 2005-03-22 13:54    [W:0.020 / U:63.216 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site