[gnutls-devel] GnuTLS | ext/record_size_limit: distinguish sending and receiving limits (!985)

[Development of GNU's TLS library]

Daiki Ueno commented on a discussion on lib/ext/max_record.c: https://gitlab.com/gnutls/gnutls/merge_requests/985#note_164709605

>  
>  	/* this function sends the client extension data (dnsname) */
>  	if (session->security_parameters.entity == GNUTLS_CLIENT) {
> -		if (session->security_parameters.max_record_send_size !=
> +		/* this extension requires that both sending and
> +		 * receiving limits are the same */

@tomato42 maybe I don't understand what you mean, but my understanding is that if max_fragment_length is negotiated, the limit applies to both sending and receiving.

The below condition is basically to check a programmer error, where the programmer sets the limit with the new asymmetric API `gnutls_record_set_max_recv_size()` instead of the old API `gnutls_record_set_max_size()`.

-- 
Reply to this email directly or view it on GitLab: https://gitlab.com/gnutls/gnutls/merge_requests/985#note_164709605
You're receiving this email because of your account on gitlab.com.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.gnupg.org/pipermail/gnutls-devel/attachments/20190426/fbad1e60/attachment.html>