public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: ummeegge <ummeegge@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] unbound: Update to 1.9.0
Date: Fri, 15 Feb 2019 14:12:42 +0100	[thread overview]
Message-ID: <14c5d428a3bf996d499779fb903415b7635132c6.camel@ipfire.org> (raw)
In-Reply-To: <158112F4-0931-45C2-9BD6-2D577CBBA1D2@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 1699 bytes --]

Hi Michael,
another point was TFO for DoT whereby Matthis found an interessting
mailinglist entry -->
https://www.mail-archive.com/unbound-users(a)nlnetlabs.nl/msg00523.html .
So it appears that DoT currently do not benefits from TFO which
reflects also my testings. There has been longer time ago also some
requests on OpenSSL causing this topic -->
https://github.com/openssl/openssl/issues/4783 (there ist more).

In general, after some faster tests with curl, TFO seems to work --> 
https://forum.ipfire.org/viewtopic.php?f=50&t=21954&start=15#p122372 .


Best,

Erik


On Do, 2019-02-14 at 11:01 +0000, Michael Tremer wrote:
> Hi,
> 
> > On 14 Feb 2019, at 07:05, Matthias Fischer <
> > matthias.fischer(a)ipfire.org> wrote:
> > 
> > Hi Michael,
> > 
> > On 13.02.2019 18:32, Michael Tremer wrote:
> > > Hi,
> > > 
> > > I did *not* merge this one, yet.
> > 
> > No problem - I'm in touch with Erik trying to help testing TFO and
> > DoT.
> 
> Please don’t forget to share what you are doing on this list :)
> 
> > 
> > Its a bit weird...
> > 
> > > The change log that you linked wasn’t very helpful, but there was
> > > an announcement email with some more details:
> > > 
> > >  
> > > https://nlnetlabs.nl/pipermail/unbound-users/2019-February/011353.html
> > > 
> > > This release contains all the EDNS Flag Day changes and that
> > > might cause some trouble. I would prefer to merge this with the
> > > next Core Update because Core 128 should already have been closed
> > > and I do not want to risk re-opening it.
> > > 
> > > So, please remind me to merge this next week in case I forgot.
> > 
> > No hurry - I'll do. ;-)
> > 
> > Best,
> > Matthias
> > 
> > > ...
> 
> -Michael


      parent reply	other threads:[~2019-02-15 13:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-09  9:40 Matthias Fischer
2019-02-13 17:32 ` Michael Tremer
2019-02-14  7:05   ` Matthias Fischer
2019-02-14 11:01     ` Michael Tremer
2019-02-14 17:26       ` Matthias Fischer
2019-02-15 11:34         ` Michael Tremer
2019-02-15 16:48           ` Matthias Fischer
2019-02-26  9:54             ` Michael Tremer
2019-02-15 13:12       ` ummeegge [this message]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=14c5d428a3bf996d499779fb903415b7635132c6.camel@ipfire.org \
    --to=ummeegge@ipfire.org \
    --cc=development@lists.ipfire.org \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox