TLS 1.3 Causes TCP Issue with Flask #2

Open
opened 2020-12-07 21:57:37 -05:00 by gashapwn · 0 comments
Owner

When TLS 1.3 is enabled, requesting an image (such as lainsign.png) causes part of the image to load and then the connection becomes stuck. The TCP connection stays alive but sends no more packets with data in them.

This only happens for some clients.

This seems to be related to MTU / SSL / the OpenBSD TCP implementation.

TLS 1.3 is currently disabled and TLS 1.2 is used, but this bug should be fixed and TLS 1.3 re-enabled.

When TLS 1.3 is enabled, requesting an image (such as lainsign.png) causes part of the image to load and then the connection becomes stuck. The TCP connection stays alive but sends no more packets with data in them. This only happens for some clients. This seems to be related to MTU / SSL / the OpenBSD TCP implementation. TLS 1.3 is currently disabled and TLS 1.2 is used, but this bug should be fixed and TLS 1.3 re-enabled.
gashapwn added the
Problem
label 2020-12-07 22:50:48 -05:00
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: gashapwn/lyadmin#2
No description provided.