public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: "Peter Müller" <peter.mueller@link38.eu>
To: development@lists.ipfire.org
Subject: Re: [Fwd: Re: request for info: unbound via https / tls]
Date: Tue, 04 Dec 2018 17:19:45 +0100	[thread overview]
Message-ID: <fa272e61-5de8-5d3d-27ce-105b05e9fe22@link38.eu> (raw)
In-Reply-To: <bfa9531d3ab365105ee98c55a317e9e7c79c9d45.camel@ipfire.org>

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

Hello Erik,

> Hi Paul,
> and thanks for your positive feedback.
> Wrote now all togehter for better overview but also for better overview
> of open questions.
> 
> You can find in here --> https://gitlab.com/ummeegge/dot-for-ipfire 
> the actual state + a simple in- uninstaller helper, i hoped it is 
> then may also a little easier for people without "developer|admin-foo" to go 
> for some testing rounds ;-).
> 
> ldns (which includes drill) can be found in here -->
> https://people.ipfire.org/~ummeegge/ldns/ .
> 
> Since this topic here is also an older one, i´ am not sure if there is interest anymore in DoT or DoH.
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.

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 can only speak for myself here, but do not have any overview about
what these are in detail. :-)

Maybe joining a telco might help (nudge, nudge). :-)

Thanks, and best regards,
Peter Müller
> 
> Let´s see.
> 
> Best,
> 
> Erik
> -- 
Microsoft DNS service terminates abnormally when it recieves a response
to a DNS query that was never made.  Fix Information: Run your DNS
service on a different platform.
		-- bugtraq

  reply	other threads:[~2018-12-04 16:19 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1525184928.3530.13.camel@gmail.com>
2018-05-01 14:33 ` Paul Simmons
2018-05-01 14:40   ` Peter Müller
2018-05-01 17:16     ` Paul Simmons
2018-05-03 16:03       ` Michael Tremer
2018-12-02 19:10     ` ummeegge
2018-12-02 20:23       ` Paul Simmons
2018-12-04 14:01         ` ummeegge
2018-12-04 16:19           ` Peter Müller [this message]
2018-12-05  7:35             ` ummeegge
2018-12-09 20:08               ` ummeegge
2018-12-10  0:21                 ` Michael Tremer
2018-12-10 11:30                   ` ummeegge
2018-12-10  0:21               ` Michael Tremer
2018-12-10 12:14                 ` ummeegge
2018-12-10 12:32                   ` ummeegge
2018-12-10 13:26                     ` Michael Tremer
2018-12-10 14:37                       ` ummeegge
2018-12-11 19:22                         ` Michael Tremer
2018-12-11 19:43                           ` ummeegge
2018-12-11 19:54                             ` Michael Tremer
2018-12-12 13:42                               ` ummeegge
2018-12-12 15:25                                 ` Michael Tremer
2018-12-12 17:44                                   ` ummeegge
2018-12-13  6:52                                     ` ummeegge
2018-12-13 16:26                                       ` Michael Tremer
2018-12-10 13:37                   ` Michael Tremer
2018-12-11  2:01                   ` Paul Simmons
2018-12-11 20:09                     ` ummeegge

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=fa272e61-5de8-5d3d-27ce-105b05e9fe22@link38.eu \
    --to=peter.mueller@link38.eu \
    --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