Skip to content
New issue

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

Encrypted payloads should not exceed 16384 bytes to match TLS record standard #8

Open
mrapitis opened this issue Apr 27, 2017 · 0 comments

Comments

@mrapitis
Copy link

To ensure compatibility with transport layer security, we should make note when using encrypted protocol messages, the payload should not exceed 16384 bytes to match the maximum available in a standard TLS record. Please see link below for details as well as a pertinent copy / pasted snippet.

https://hpbn.co/transport-layer-security-tls/

Maximum TLS record size is 16 KB Each record contains a 5-byte header, a MAC (up to 20 bytes for SSLv3, TLS 1.0, TLS 1.1, and up to 32 bytes for TLS 1.2), and padding if a block cipher is used. To decrypt and verify the record, the entire record must be available.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant