[jdev] Re: s2s - invalid subsequent db:result

[Gaston Dombiak]

Hey Stephen,

Thanks for your answer. I finally made the same assumption.

Regards,

  -- Gato

"Stephen Marquard" <scm at marquard.net> wrote in message 
news:d6jrgv$d0k$1 at sea.gmane.org...
> Gaston Dombiak wrote:
>> The RFC3920 says:
>> "After successful dialback negotiation, the Receiving Server SHOULD 
>> accept subsequent <db:result/> packets (e.g., validation requests sent to 
>> a subdomain or other hostname serviced by the Receiving Server) from the 
>> Originating Server over the existing validated connection; this enables 
>> "piggybacking" of the original validated connection in one direction."
>>
>> Which is the expected behavior when the subsequent <db:result/> packet is 
>> invalid or there was some kind of error during the validation process? 
>> Should the Receiving Server close the stream and the underlying TCP 
>> connection as described in Protocol 8.3 step 10?
>
> That was my interpretation for jabberd2 - any validation error on the 
> stream at any stage causes the stream & TCP connection to be closed.
>
> It should only happen if something is misconfigured on either side or 
> someone is trying to spoof a connection.
>
> Regards
> Stephen