randombit/botan

Limit data sent over TLS by ciphersuite

Open

#2,283 opened on Feb 26, 2020

View on GitHub
 (1 comment) (0 reactions) (0 assignees)C++ (654 forks)auto 404
enhancementhelp wanted

Repository metrics

Stars
 (3,283 stars)
PR merge metrics
 (PR metrics pending)

Description

Then renegotiate or fail when too much data is sent. There is already a limit of 2^48 for DTLS or 2^64 for TLS due to sequence number wraparound, but specific ciphers have smaller limits. This is most important for 3DES due to collisions, but even AES-GCM has relatively small limits

NSS change https://bugzilla.mozilla.org/show_bug.cgi?id=1268745 Paper http://www.isg.rhul.ac.uk/~kp/TLS-AEbounds.pdf

Contributor guide

Research direction
Study the existing TLS implementation in Botan, locate where data transfer limits are currently enforced, and implement ciphersuite specific limits based on the referenced NSS change and paper.
Tech stack
cpp
Domain
security
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
C++Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40