diff options
| author | Daiki Ueno <dueno@redhat.com> | 2019-04-25 17:08:43 +0200 |
|---|---|---|
| committer | Daiki Ueno <dueno@redhat.com> | 2019-05-14 06:44:38 +0200 |
| commit | 2dc96e3b8d0e043bebf0815edaaa945f66ac0531 (patch) | |
| tree | df3932ecaf592291b53cb8936d23ba19f9226f50 /devel/fuzz/gnutls_client.in/fe9abe3ee8ab25893f43f213496ba1c01f9d8579 | |
| parent | 9509af0e791b74538de8ffa8dd0d47c05cb08eed (diff) | |
| download | gnutls-tmp-record-sizes.tar.gz | |
ext/record_size_limit: distinguish sending and receiving limitstmp-record-sizes
The previous behavior was that both sending and receiving limits are
negotiated to be the same value. It was problematic when:
- client sends a record_size_limit with a large value in CH
- server sends a record_size_limit with a smaller value in EE
- client updates the limit for both sending and receiving, upon
receiving EE
- server sends a Certificate message larger than the limit
With this patch, each peer maintains the sending / receiving limits
separately so not to confuse with the contradicting settings.
Signed-off-by: Daiki Ueno <dueno@redhat.com>
Diffstat (limited to 'devel/fuzz/gnutls_client.in/fe9abe3ee8ab25893f43f213496ba1c01f9d8579')
0 files changed, 0 insertions, 0 deletions