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
There are no such plans, but I am happy to accept a PR, that allows users to specify a padding scheme. I am open to suggestions on API, but a good one would probably be to allow to set a functor that accepts original size of the record and returns size of padding to be used.
Would it be possible to add support for TLS 1.3 record padding to thwart traffic analysis?
The text was updated successfully, but these errors were encountered: