[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: https://gitlab.com/gnutls/gnutls/merge_requests/985#note_165188848

> but gnutls does default to 2^14+1, so a server that replies with a lower value, will force that asymmetricity; also as we discussed

This is already covered by the new unit tests, where server and client sends different limits.

> also as we discussed, if the server does reply with 64, the client has only two options: comply or abort connection, it can't retroactively un-negotiate the extension

This still sounds out-of-scope.  Regardless of this MR, the client aborts when it receives smaller limits than 512.

-- 
Reply to this email directly or view it on GitLab: https://gitlab.com/gnutls/gnutls/merge_requests/985#note_165188848
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/20190429/832433bc/attachment.html>