public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: ummeegge <ummeegge@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [Fwd: Re: request for info: unbound via https / tls]
Date: Sun, 02 Dec 2018 20:10:31 +0100	[thread overview]
Message-ID: <2a8665dc77d64d42818cc8a1b3ec92a3090a9403.camel@ipfire.org> (raw)
In-Reply-To: <45075a10-3447-480e-dcc5-4878242e6a82@link38.eu>

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

Hi all,
have build knot but needed also

  # Begin knot deps
  lfsmake2 libmaxminddb
  lfsmake2 libedit
  lfsmake2 userspace
  lfsmake2 knot
  # End knot

to build kdig properly. By the usage of e.g.

kdig -d @145.100.185.18 +tls-host=dnsovertls3.sinodun.com ipfire.org

i get an

;; DEBUG: Querying for owner(ipfire.org.), class(1), type(1),
server(145.100.185.18), port(853), protocol(TCP)
;; WARNING: TLS, failed to import system certificates
(GNUTLS_E_UNIMPLEMENTED_FEATURE)
;; WARNING: failed to query server 145.100.185.18(a)853(TCP)

. So it seems that 'gnutls_x509_trust_list_add_trust_file{dir}()' is
not able to find the system certificates. May a

--with-default-trust-store-dir=/etc/ssl/certs

in configure of GnuTLS might help there...

As a beside one, some tests causing DoT happens in here -->
https://forum.ipfire.org/viewtopic.php?f=50&t=21954

whereby Dot runs currently without problems but the focus is in there relies
on the initscript of unbound to make DoT usable over on IPFire.

Have compiled meanwhile also ldns whereby drill is also a possibility 
for other views and there is also a DoT patch for ldns -->

https://portal.sinodun.com/stash/projects/TDNS/repos/dns-over-tls_patches/browse/ldns-1.6.17_dns-over-tls.patch

https://tools.ietf.org/html/draft-ietf-dprive-dns-over-tls-09#section-8.2

but the versions are outdated even unbound needs also to be patched.
May NLnet Labs did there already something to support that but i haven´t found it yet.

Some infos from here.

Best,

Erik
 

Am Dienstag, den 01.05.2018, 16:40 +0200 schrieb Peter Müller:
> Hello,
> 
> > 
> > The unbound init and the cgi scripts use dig 9.11.3, which has no
> > native support for TLS.  I'm trying to configure stunnel to act as
> > MITM
> > so that dig can succeed.  I hope to restrict unbound to port 853
> > for
> > listen and send, and use stunnel to listen on port 53 and forward
> > to
> > 853.
> 
> as far as I am aware, the knot-utils from CZ.NIC are capable of
> DNS over TLS. Maybe we should think about moving to them, or wait
> until bind-utils/dig are updated (not sure if we are running the
> latest
> version anyway).
> 
> Best regards,
> Peter Müller
> 


  parent reply	other threads:[~2018-12-02 19:10 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 [this message]
2018-12-02 20:23       ` Paul Simmons
2018-12-04 14:01         ` ummeegge
2018-12-04 16:19           ` Peter Müller
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=2a8665dc77d64d42818cc8a1b3ec92a3090a9403.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