feat: bump restls to v0.1.5 (utls v1.4.3) #692
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi,
Sorry for the delay. We were working on this update throughout the entire week.
Off topic:
It turns out we were among the few projects leveraging session resumption (we don't rebuild the TLS Config per connection). This led us down many rarely traversed paths, which hadn't been tested for years. Pinpointing and resolving these issues was time-consuming.
Our efforts culminated in the introduction of a long-awaited feature in uTLS: PSK-based session resumption for TLS 1.3. We're in the final stages of our work, anticipating its integration into uTLS. Implementing the PSK feature will enhance parroting, aligning utls clients more closely with browsers, especially given that recent Chrome versions utilize PSK-based sessions for TLS 1.3.