From mboxrd@z Thu Jan 1 00:00:00 1970 From: ummeegge To: development@lists.ipfire.org Subject: Re: [Fwd: Re: request for info: unbound via https / tls] Date: Wed, 05 Dec 2018 08:35:33 +0100 Message-ID: <1a6da97b7616f5d73650ad6ed6f89a2cc8d2775c.camel@ipfire.org> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============5281111774036170489==" List-Id: --===============5281111774036170489== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hello Peter, and thanks for your response. Am Dienstag, den 04.12.2018, 17:19 +0100 schrieb Peter M=C3=BCller: > I am pretty sure there is still huge interest in adding DoT support > to > IPFire - in my point of view, yesterdays telephone conference showed > this again. >=20 Good to here. Wanted to be part of the last conference but my jobsite have had other plans. > Our problem seems to be a lack of coordination: You are developing > pretty much (OpenSSL 1.1.1 comes to my mind), which is simply great. I do not really see a lack of coordination here or are somebody else working on DoT currently ?=20 OpenSSL-1.1.1 might be a good/important addition to DoT -->=20 https://tools.ietf.org/html/draft-ietf-tls-sni-encryption-02 --> https://blog.cloudflare.com/encrypted-sni/ which brings also some=20 other interesting side affects -->=20 https://www.dnsthingy.com/2018/10/encrypted-sni-death-blow-to-transparent-fil= tering/=20 ... > I can only speak for myself here, but do not have any overview about > what these are in detail. :-) >=20 Not 100% sure what you mean, are you mean an overview of other projects which i am currently working one ? > Maybe joining a telco might help (nudge, nudge). :-) >=20 I hear you :D . Looking forward for more_action/more_people or in general for more response/help in this topic. Best, Erik --===============5281111774036170489==--