Unbound 1.6.1 has a few bug fixes for resource leaks,
configuration robustness, compile environment interaction,
and maintaining the trust anchor. The 2017 trust anchor
(DS) is built into unbound and unbound-anchor.
File /etc/unbound/root.key holds 2010/2017 DS record until 2018
https://www.icann.org/resources/pages/ksk-rolloverhttps://www.iana.org/domains/root
Signed-off-by: Eric Luehrsen <ericluehrsen@hotmail.com>
Update:
- Python 3.6 support fixed. It is now correctly compiled and available.
Fixes:
- disabled context and fiber for unsupported targets
There are several architectures which are not supported by context nor
fiber. Because of this, Boost build was failing targets. This created the
situation where the other boost libs were not being built and consequently,
becoming unavailable at the OpenWRT/LEDE repositories.
To solve this issue, it was necessary to disabled fiber and context for
the incompatible targets.
Boost.Fiber is disabled for:
-> ar7, rb532, brcm63xx.smp, brcm63xx, brcm47xx, brcm47xx.legacy, brcm2708,
au1000, ath25, adm8668 and adm5120.
Boost.Context is disabled for:
-> avr32, octeon and netlogic.
Signed-off-by: Carlos Miguel Ferreira <carlosmf.pt@gmail.com>
To have service working nicely with procd it should be running in the
foreground. Otherwise it's not possible to e.g. stop it with the init.d
script. Luckily for us pptpd has a simple switch that allows it.
Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
Fixes: 15e7f611af ("pptpd: convert init script to procd")
This fixes upstream regression introduced in 1.4.40. It was reported &
debugged in https://redmine.lighttpd.net/issues/2793
This fix is queued for 1.4.46 in the personal/gstrauss/master upstream
branch.
Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* optimize memory consumption &
enable overall sort only on devices with > 64MB RAM,
this prevents sort related kernel dumps
Signed-off-by: Dirk Brenken <dev@brenken.org>
This commit fixes an existent regression in boost 1.63 [1].
The regression appears when libc is used for the toolchain.
[1] - https://svn.boost.org/trac/boost/ticket/11756
Signed-off-by: Carlos Miguel Ferreira <carlosmf.pt@gmail.com>
Update to 1.4.42 introduced a problem with starting lighttpd as
OpenWrt/LEDE service. It was stopping whole init process at sth like:
783 root 1124 S {S50lighttpd} /bin/sh /etc/rc.common /etc/rc.d/S50lighttpd boot
799 root 1164 S /usr/sbin/lighttpd -f /etc/lighttpd/lighttpd.conf
It was hanging until getting random pool:
[ 176.340007] random: nonblocking pool is initialized
and then immediately the rest of init process followed:
[ 176.423475] jffs2_scan_eraseblock(): End of filesystem marker found at 0x0
[ 176.430754] jffs2_build_filesystem(): unlocking the mtd device... done.
[ 176.437615] jffs2_build_filesystem(): erasing all blocks after the end marker... done.
This was fixed in 1.4.44, but bump directly to 1.4.45 while at it.
Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* add 'enabled' check in init script
* support multiple radios (see online doc)
* fix race condition in ap check
Signed-off-by: Dirk Brenken <dev@brenken.org>