Re: ath10k-ct all hash values are different?

It is the firmware that is broken and just contains 0s. On 11/7/20 6:54 PM, Nick wrote: > I fixed the hash values: https://github.com/openwrt/openwrt/pull/3573 > Not sure why the hash is suddenly different for all firmware files? > > ___ > openwrt-devel

ath10k-ct all hash values are different?

I fixed the hash values: https://github.com/openwrt/openwrt/pull/3573 Not sure why the hash is suddenly different for all firmware files? ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org

[PATCH 1/2] target: select procd-ujail if !SMALL_FLASH

Add procd-ujail to DEFAULT_PACKAGES if not building for space-constraint (FEATURES:=small_flash) targets. Signed-off-by: Daniel Golle --- include/target.mk | 5 + 1 file changed, 5 insertions(+) diff --git a/include/target.mk b/include/target.mk index a2e76f8149..7a74aceb59 100644 ---

[PATCH 0/2] enable procd security features by default

Hi all! A while ago we have added some useful kernel features to !SMALL_FLASH devices[1]. To make more use of that by default in a way which will make exploiting potential vulnerabilities in OpenWrt's services much harder, it'd be great to also have procd-ujail as well as procd-seccomp installed

[PATCH 2/2] target: select procd-seccomp if kernel support is present

Install ld-preload hooks allowing to add seccomp filters for arbitrary services if kernel support for seccomp is present. Signed-off-by: Daniel Golle --- include/target.mk | 5 + 1 file changed, 5 insertions(+) diff --git a/include/target.mk b/include/target.mk index 7a74aceb59..d8cb0e6e58