mirror of
https://github.com/openssl/openssl.git
synced 2025-01-06 13:26:43 +08:00
41b3c9ce2a
In SCTP the code was only allowing a send of a close_notify alert if the socket is dry. If the socket isn't dry then it was attempting to save away the close_notify alert to resend later when it is dry and then it returned success. However because the application then thinks that the close_notify alert has been successfully sent it never re-enters the DTLS code to actually resend the alert. A much simpler solution is to just fail with a retryable error in the event that the socket isn't dry. That way the application knows to retry sending the close_notify alert. Reviewed-by: Richard Levitte <levitte@openssl.org> (Merged from https://github.com/openssl/openssl/pull/3286) |
||
|---|---|---|
| .. | ||
| b_addr.c | ||
| b_dump.c | ||
| b_print.c | ||
| b_sock2.c | ||
| b_sock.c | ||
| bf_buff.c | ||
| bf_lbuf.c | ||
| bf_nbio.c | ||
| bf_null.c | ||
| bio_cb.c | ||
| bio_err.c | ||
| bio_lcl.h | ||
| bio_lib.c | ||
| bio_meth.c | ||
| bss_acpt.c | ||
| bss_bio.c | ||
| bss_conn.c | ||
| bss_dgram.c | ||
| bss_fd.c | ||
| bss_file.c | ||
| bss_log.c | ||
| bss_mem.c | ||
| bss_null.c | ||
| bss_sock.c | ||
| build.info | ||