You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The dTLS server (1.2) is not handling properly the re-transmissions in case of delay in flight at server side (we see clientKeyExchange before serverKeyExchange and serverHelloDone)
#4036
Open
shreyaaapatil opened this issue
Apr 30, 2024
· 0 comments
We tried to test a scenario that the server has a delay before sending message, so we expect the client to do retransmission, but it seems like the client sends the next flight before getting all the flight for the server (We can see clientKeyExchange before serverKeyExchange and serverHelloDone).
void
CallbacksPSK::tls_emit_data(uint8_t const buf[], size_t const length)
{
if (nullptr == mEngine) {
throw std::runtime_error("Null engine pointer!");
}
if(mEngine->mIsServer){
sleep(5); //delay of 5 sec at server side
}
}
This is not the right behavior according to the RFC, because in case of partial read, we shouldn't move to Sending state.
The same delay when we add it for client side the handshake is getting completed-
if(!mEngine->mIsServer){
sleep(5); //delay of 5 sec at client side
}
Is adding delay at server side affecting retransmission behaviour?
The text was updated successfully, but these errors were encountered:
shreyaaapatil
changed the title
The dTLS server (1.2) is not handling properly the re-transmissions in case of delay in flight we see clientKeyExchange before serverKeyExchange and serverHelloDone
The dTLS server (1.2) is not handling properly the re-transmissions in case of delay in flight at server side we see clientKeyExchange before serverKeyExchange and serverHelloDone
Apr 30, 2024
shreyaaapatil
changed the title
The dTLS server (1.2) is not handling properly the re-transmissions in case of delay in flight at server side we see clientKeyExchange before serverKeyExchange and serverHelloDone
The dTLS server (1.2) is not handling properly the re-transmissions in case of delay in flight at server side (we see clientKeyExchange before serverKeyExchange and serverHelloDone)
Apr 30, 2024
We tried to test a scenario that the server has a delay before sending message, so we expect the client to do retransmission, but it seems like the client sends the next flight before getting all the flight for the server (We can see clientKeyExchange before serverKeyExchange and serverHelloDone).
This is not the right behavior according to the RFC, because in case of partial read, we shouldn't move to Sending state.
The same delay when we add it for client side the handshake is getting completed-
Is adding delay at server side affecting retransmission behaviour?
The text was updated successfully, but these errors were encountered: