diff options
author | Jacob Hoffman-Andrews <github@hoffman-andrews.com> | 2021-11-12 18:18:41 -0800 |
---|---|---|
committer | Daniel Stenberg <daniel@haxx.se> | 2021-11-13 22:57:20 +0100 |
commit | be8d77b14634081a6031cf1acdc0887797840f2a (patch) | |
tree | 58405952e92d6e3489ff63547af6a99015c50fe2 /acinclude.m4 | |
parent | 26247a0d7e24c06d5b250f044a951441674a4484 (diff) | |
download | curl-be8d77b14634081a6031cf1acdc0887797840f2a.tar.gz |
rustls: remove incorrect EOF check
The update to rustls-ffi 0.8.0 changed handling of EOF and close_notify.
From the CHANGELOG:
> Handling of unclean close and the close_notify TLS alert. Mirroring
> upstream changes, a rustls_connection now tracks TCP closed state like
> so: rustls_connection_read_tls considers a 0-length read from its
> callback to mean "TCP stream was closed by peer." If that happens
> before the peer sent close_notify, rustls_connection_read will return
> RUSTLS_RESULT_UNEXPECTED_EOF once the available plaintext bytes are
> exhausted. This is useful to protect against truncation attacks. Note:
> some TLS implementations don't send close_notify. If you are already
> getting length information from your protocol (e.g. Content-Length in
> HTTP) you may choose to ignore UNEXPECTED_EOF so long as the number of
> plaintext bytes was as expected.
That means we don't need to check for unclean EOF in `cr_recv()`,
because `process_new_packets()` will give us an error if appropriate.
Closes #8003
Diffstat (limited to 'acinclude.m4')
0 files changed, 0 insertions, 0 deletions