Ignore:
Timestamp:
2010-04-11T18:12:25Z (15 years ago)
Author:
Wilmer van der Gaast <wilmer@…>
Branches:
master
Children:
a87e6ba, b308cf9
Parents:
ba7d16f
Message:

Fixing a bug in s5bytestream code to deal with incomplete SOCKS5 messages
and my rewrite of the bs_peek function.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • protocols/jabber/s5bytestream.c

    rba7d16f r3ab1d31  
    482482                        else if( ret < sizeof( struct socks5_message ) )
    483483                        {
    484                                 /* Either a buggy proxy or just one that doesnt regard the SHOULD in XEP-0065
    485                                  * saying the reply SHOULD contain the address */
    486 
    487                                 ASSERTSOCKOP( ret = recv( fd, &socks5_reply, ret, 0 ), "Dequeuing after MSG_PEEK" );
     484                                /* Either a buggy proxy or just one that doesnt regard
     485                                 * the SHOULD in XEP-0065 saying the reply SHOULD
     486                                 * contain the address. We'll take it, so make sure the
     487                                 * next jabber_bs_peek starts with an empty buffer. */
     488                                bt->peek_buf_len = 0;
    488489                        }
    489490
Note: See TracChangeset for help on using the changeset viewer.