From: Lars Ingebrigtsen <larsi@gnus.org>
To: ludo@gnu.org (Ludovic Courtès)
Cc: Andy Wingo <wingo@igalia.com>, 25061@debbugs.gnu.org
Subject: bug#25061: consider adding %COMPAT to default gnutls priority string
Date: Tue, 24 Jan 2017 23:48:31 +0100 [thread overview]
Message-ID: <878tq0dqgw.fsf@gnus.org> (raw)
In-Reply-To: <87zikfmiiy.fsf@lifelogs.com> (Ted Zlatanov's message of "Thu, 01 Dec 2016 16:44:21 -0500")
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
next prev parent reply other threads:[~2017-01-24 22:48 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-29 10:24 bug#25061: consider adding %COMPAT to default gnutls priority string Andy Wingo
2016-12-01 18:32 ` Ted Zlatanov
2016-12-01 20:25 ` Ludovic Courtès
2016-12-01 21:44 ` Ted Zlatanov
2017-01-24 22:48 ` Lars Ingebrigtsen [this message]
2017-01-30 8:01 ` Ludovic Courtès
2017-02-10 15:51 ` Andy Wingo
2017-02-13 16:04 ` Ted Zlatanov
2017-09-02 13:49 ` Eli Zaretskii
2017-09-06 19:32 ` Ted Zlatanov
2017-09-07 7:18 ` Michael Albinus
2017-09-14 21:11 ` Ted Zlatanov
2017-09-15 6:05 ` Eli Zaretskii
2017-12-02 17:36 ` Eli Zaretskii
2017-12-09 23:50 ` Ted Zlatanov
2017-12-10 7:04 ` Eli Zaretskii
2017-12-10 13:29 ` Ted Zlatanov
2017-12-10 14:12 ` Eli Zaretskii
2017-12-11 15:03 ` Ted Zlatanov
2017-12-11 15:40 ` Eli Zaretskii
2017-12-15 4:18 ` Ted Zlatanov
2017-12-16 23:25 ` Philipp Stephani
2017-12-16 23:34 ` Ted Zlatanov
2017-12-17 3:39 ` Eli Zaretskii
2017-12-17 15:17 ` Eli Zaretskii
2017-12-19 17:46 ` Ted Zlatanov
2017-12-17 17:52 ` Philipp Stephani
2017-12-10 9:31 ` Michael Albinus
2017-12-18 17:16 ` Kaushal Modi
2017-12-18 19:52 ` Philipp Stephani
2017-12-19 17:47 ` Ted Zlatanov
2017-12-19 22:00 ` Kaushal Modi
2017-12-20 1:08 ` Ted Zlatanov
2017-12-20 11:41 ` Robert Pluim
2017-12-20 16:09 ` Eli Zaretskii
2017-12-21 13:20 ` Kaushal Modi
2017-12-21 13:26 ` Ted Zlatanov
2017-12-20 11:48 ` Kaushal Modi
2017-12-20 12:54 ` Andy Moreton
2017-12-20 13:16 ` Andy Moreton
2017-12-20 16:19 ` Eli Zaretskii
2017-12-20 16:38 ` Andy Moreton
2017-12-21 1:15 ` Ted Zlatanov
2017-12-21 1:39 ` Ted Zlatanov
2017-12-21 8:30 ` Robert Pluim
2017-12-21 13:12 ` Ted Zlatanov
2017-12-21 16:20 ` Eli Zaretskii
2017-12-21 10:54 ` Andy Moreton
2017-12-21 16:26 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878tq0dqgw.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=25061@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=wingo@igalia.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).