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 attempt count to send a message should be stored in the store.
Use case:
An evil firewall dislike our poisonous packet, and close the connection.
User try to send this poisonous packet in QoS > 0.
The packet is stored, then sent, the firewall drop the connection.
Then the client try to reconnect with existing connection, and, according to the spec, the first thing it do, is to resend these stored packet.
We are now stuck in a loop, where the client reconnect, send this poisonous packet, firewall drop the connection...
Current implementation only work if the evil firewall block the packet, but don't drop the connection.
The text was updated successfully, but these errors were encountered:
The attempt count to send a message should be stored in the store.
Use case:
An evil firewall dislike our poisonous packet, and close the connection.
User try to send this poisonous packet in QoS > 0.
The packet is stored, then sent, the firewall drop the connection.
Then the client try to reconnect with existing connection, and, according to the spec, the first thing it do, is to resend these stored packet.
We are now stuck in a loop, where the client reconnect, send this poisonous packet, firewall drop the connection...
Current implementation only work if the evil firewall block the packet, but don't drop the connection.
The text was updated successfully, but these errors were encountered: