unbound: new package

Unbound: validating, recursive & caching DNS resolver with DNSSEC, QNAME minimisation, DNSCrypt and DNS-over-TLS support.

---

Changes v1 -> v2:

- Fixed license to BSD-3-Clause (by Bernd Kuhls)
- Fixed DNSCrypt handling (by Bernd Kuhls)
- Use "select BR2_PACKAGE_OPENSSL" (by Bernd Kuhls)
- Added "--with-ssl=$(STAGING_DIR)/usr" (by Bernd Kuhls)
- Use "BR2_TOOLCHAIN_USES_UCLIBC" (by Bernd Kuhls)

 DEVELOPERS                   |  1 +
 package/Config.in            |  1 +
 package/unbound/Config.in    | 37 ++++++++++++++++++++++++++++++++
 package/unbound/unbound.hash |  3 +++
 package/unbound/unbound.mk   | 51 ++++++++++++++++++++++++++++++++++++++++++++
 5 files changed, 93 insertions(+)
 create mode 100644 package/unbound/Config.in
 create mode 100644 package/unbound/unbound.hash
 create mode 100644 package/unbound/unbound.mk

index 2f7d051e8a..184ce82cec 100644
@@ -1642,6 +1642,7 @@ N:	Stefan Fr?berg <[email protected]>
 F:	package/elfutils/
 F:	package/libtasn1/
 F:	package/proxychains-ng/
+F:	package/unbound/
 F:	package/yasm/
 F:	package/zlib-ng/
 

index 01f4095be5..f810445e27 100644
@@ -1827,6 +1827,7 @@ endif
 	source "package/udpcast/Config.in"
 	source "package/uhttpd/Config.in"
 	source "package/ulogd/Config.in"
+	source "package/unbound/Config.in"
 	source "package/ushare/Config.in"
 	source "package/ussp-push/Config.in"
 	source "package/vde2/Config.in"

new file mode 100644
index 0000000000..a53cd2537c
@@ -0,0 +1,37 @@
+config BR2_PACKAGE_UNBOUND
+	bool "unbound"
+	select BR2_PACKAGE_EXPAT
+	select BR2_PACKAGE_LIBEVENT
+	select BR2_PACKAGE_OPENSSL
+	help
+	  Unbound is a validating, recursive, and caching DNS resolver.
+	  It supports DNSSEC, QNAME minimisation, DNS-over-TLS and
+	  DNSCrypt.
+
+	  https://www.unbound.net
+
+if BR2_PACKAGE_UNBOUND
+
+config BR2_PACKAGE_UNBOUND_DNSCRYPT
+	bool "Enable DNSCrypt"
+	select BR2_PACKAGE_LIBSODIUM
+	help
+	  DNSCrypt wraps unmodified DNS queries between a client and
+	  a DNS resolver. Default port used is 443 and like with
+	  normal unencrypted DNS, it uses UDP first and falling back
+	  to TCP if response too large.
+
+	  There is also DNS-over-TLS, a TCP only version
+	  of proposed standard for DNS encryption (RFC 7858).
+	  Default port for DNS-over-TLS is 853 and Unbound has
+	  built-in support for it.
+
+	  https://tools.ietf.org/html/rfc7858
+
+	  Note: Neither DNSCrypt or DNS-over-TLS encrypt the SNI.
+	  Here is some suggestions how to handle SNI encryption:
+
+	  https://tools.ietf.org/html/draft-ietf-tls-sni-encryption-00
+
+endif
+

new file mode 100644
index 0000000000..5f2183897e
@@ -0,0 +1,3 @@
+# Locally calculated
+sha256	4e7bd43d827004c6d51bef73adf941798e4588bdb40de5e79d89034d69751c9f  unbound-1.6.7.tar.gz
+sha256	8eb9a16cbfb8703090bbfa3a2028fd46bb351509a2f90dc1001e51fbe6fd45db  LICENSE

2.13.6

Am Sun, 14 Jan 2018 00:26:51 +0200 schrieb Stefan Fr?berg:

Hi,

when testing your package with this defconfig stored in ./test-unbound

$ cat ./test-unbound 
BR2_PACKAGE_UNBOUND=y
BR2_PACKAGE_UNBOUND_DNSCRYPT=y

$ utils/test-pkg -c test-unbound $HOME/test-unbound

it fails on some platforms:

                   br-arm-cortex-m4-full [ 8/47]: FAILED
                      br-arm-full-static [11/47]: FAILED
                            br-bfin-full [12/47]: FAILED
                       br-m68k-5208-full [15/47]: FAILED

I stopped the test at this point, maybe you can have a look at the failures? I did not do that at this time (CET) of day ;)

Regards, Bernd

Hi Bernd

Bernd Kuhls kirjoitti 14.01.2018 klo 01:11:

Uh...47 compiler/platform combinations? Jeeez...that will take ages with my poor comp ...

Where does that test-pkg script output the build failures?

Regards
Stefan
?

Hi Stefan,

Am Sun, 14 Jan 2018 19:56:00 +0200 schrieb Stefan Fr?berg:

Maybe not, test-pkg uses pre-built toolchains, just like the autobuilders.

$HOME/test-unbound/{name of compiler/platform combo}/logfile

Some errors are thread-related, maybe you need to check for BR2_TOOLCHAIN_HAS_THREADS_NPTL instead of BR2_TOOLCHAIN_HAS_THREADS.

Regards, Bernd

Hello Bernd

I have a little problem. I have ran all the tests now but my $HOME/tests-unbound is totally empty.
What I am doing wrong?

Regards
Stefan

Bernd Kuhls kirjoitti 14.01.2018 klo 20:42:

Am Tue, 16 Jan 2018 23:28:58 +0200 schrieb Stefan Fr?berg:

Hi Stefan,

I wrote

$ utils/test-pkg -c test-unbound $HOME/test-unbound

and forgot to add "-d" before $HOME/test-unbound, sorry.

The correct syntax would have been

$ utils/test-pkg -c test-unbound -d $HOME/test-unbound

Therefore $HOME/test-unbound was not used but you should find the builds in $HOME/br-test-pkg/ instead, this is the default value.

Regards, Bernd

Hi Bernd

Bernd Kuhls kirjoitti 16.01.2018 klo 23:48:

No problem at all :-)

You are right. Thank god and Thank You!

Best Regards
Stefan

Hi,

Will you send an updated patch once you have looked at those build failures? I have so far marked the patch as changes requested in patchwork.

Bye, Peter Korsgaard

Hi Peter

Yes, I try to go throught them all tomorro.
Already checked some of them and they give me error because I don't have 32-bit libs on my pure, non-multilib 64-bit system.
So those ones I can't check out.

Best Regards
Stefan

Peter Korsgaard kirjoitti 28.01.2018 klo 18:24:

Does your distribution not provide 32bit libraries? The toolchains are 32bit on purpose for compatibility reasons.

Bye, Peter Korsgaard

Results:

armv5-ctng-linux-gnueabi [ 1/47]: FAILED (cannot execute cross-compiler) armv7-ctng-linux-gnueabihf [ 2/47]: FAILED (cannot execute cross-compiler)

br-arm-cortex-m4-full [ 8/47]: FAILED (need openssl 0.9.7 or higher) br-arm-full-static [11/47]: FAILED (need openssl 0.9.7 or higher)

br-bfin-full [12/47]: FAILED (undefined pthread_spin_init, pthread_spin_lock etc..)
br-m68k-5208-full [15/47]: FAILED (undefined pthread_spin_init, pthread_spin_lock etc..)
br-m68k-68040-full [16/47]: FAILED (undefined pthread_spin_init, pthread_spin_lock etc..)
br-microblazeel-full [17/47]: FAILED (undefined pthread_spin_init, pthread_spin_lock etc..)
br-openrisc-uclibc [23/47]: FAILED (undefined pthread_spin_init, pthread_spin_lock etc..)

i686-ctng-linux-gnu [34/47]: FAILED (cannot execute cross-compiler) mips64el-ctng_n32-linux-gnu [37/47]: FAILED (cannot execute cross-compiler) mips64el-ctng_n64-linux-gnu [38/47]: FAILED (cannot execute cross-compiler) powerpc-ctng_e500v2-linux-gnuspe [39/47]: FAILED (cannot execute cross-compiler)
sourcery-arm-armv4t [40/47]: FAILED (need 32-bit support library) sourcery-arm [41/47]: FAILED (need 32-bit support library) sourcery-arm-thumb2 [42/47]: FAILED (need 32-bit support library) sourcery-mips64 [43/47]: FAILED (need 32-bit support library) sourcery-mips [44/47]: FAILED (need 32-bit support library) sourcery-nios2 [45/47]: FAILED (need 32-bit support library) sourcery-x86-64 [46/47]: FAILED (need 32-bit support library) x86_64-ctng_locales-linux-gnu [47/47]: FAILED (cannot execute cross-compiler)

So only br-bfin-full, br-m68k-5208-full, br-m68k-68040-full, br-microblazeel-full, br-openrisc-uclibc
I could only try to patch.

So what is the proper way of checking if external toolchain has thread support ?
BR2_TOOLCHAIN_HAS_THREADS checks only internal toolchain right?

Best Regards
Stefan

Huh? Are you missing some 32bit libraries?

Presumably needs do depend on openssl?

Needs threads support.

Again 32bit libraries?

No, BR2_TOOLCHAIN_HAS_THREADS applies to all toolchain types.

Bye, Peter Korsgaard