We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HttpServer responses to HTTP queries are encrypted into separate RecordLayer messages on a line-by-line basis, thus creating side-channel leak.
In other words, the following reply:
[Thread 21] [12/4/2015 6:41:24 PM] --> HTTP/1.0 200 OK [Thread 21] [12/4/2015 6:41:24 PM] --> Content-Type: text/plain [Thread 21] [12/4/2015 6:41:24 PM] --> Connection: close [Thread 21] [12/4/2015 6:41:24 PM] --> Content-Length: 0 [Thread 21] [12/4/2015 6:41:24 PM] -->
will be encrypted in 5 Application Data records:
ApplicationData('HTTP/1.0 200 OK\r\n') ApplicationData('Content-Type: text/plain\r\n') ApplicationData('Connection: close\r\n') ApplicationData('Content-Length: 0\r\n') ApplicationData('\r\n')
The text was updated successfully, but these errors were encountered:
No branches or pull requests
HttpServer responses to HTTP queries are encrypted into separate RecordLayer messages on a line-by-line basis, thus creating side-channel leak.
In other words, the following reply:
will be encrypted in 5 Application Data records:
The text was updated successfully, but these errors were encountered: