[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#25061: consider adding %COMPAT to default gnutls priority string
From: |
Lars Ingebrigtsen |
Subject: |
bug#25061: consider adding %COMPAT to default gnutls priority string |
Date: |
Tue, 24 Jan 2017 23:48:31 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/26.0.50 (gnu/linux) |
Ted Zlatanov <tzz@lifelogs.com> writes:
> On Thu, 01 Dec 2016 21:25:29 +0100 ludo@gnu.org (Ludovic Courtès) wrote:
>
> LC> Ted Zlatanov <tzz@lifelogs.com> skribis:
>
>>> We could break down %COMPAT to all its components and find which ones
>>> are causing the issue.
>
> LC> %DUMBFW may be that option (info "(gnutls) Priority Strings"):
>
> LC> will add a private extension with bogus data that make the
> LC> client hello exceed 512 bytes. This avoids a black hole
> LC> behavior in some firewalls. This is the [_rfc7685_] client
> LC> hello padding extension, also enabled with %COMPAT.
>
> Nice. Could you or Andy verify if it resolves the originally reported
> problem? I think it's very reasonable to add it to the default, if it does.
Yes, I think so, too. Did anyone of you check whether it fixed the problems?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
- bug#25061: consider adding %COMPAT to default gnutls priority string,
Lars Ingebrigtsen <=