Re: [LEDE-DEV] [PATCH v2] openvpn: update to 2.4.3

2017-06-22 Thread e9hack
Am 22.06.2017 um 23:01 schrieb Magnus Kroken: > v2: Correct PKG_HASH and add another mirror. OpenVPN had various issues with > their > CDN caching wrong files, these are the correct values according to > http://community.openvpn.net/openvpn/wiki/release-packages-2.4.3-2.3.17. See > mailing list

[LEDE-DEV] [PATCH v2] openvpn: update to 2.4.3

2017-06-22 Thread Magnus Kroken
Fixes for security and other issues. See security announcement for more details: https://community.openvpn.net/openvpn/wiki/VulnerabilitiesFixedInOpenVPN243 * Remotely-triggerable ASSERT() on malformed IPv6 packet (CVE-2017-7508) * Pre-authentication remote crash/information disclosure for

Re: [LEDE-DEV] [PATCH procd] watchdog: add support for starting/stopping kernel watchdog

2017-06-22 Thread John Crispin
On 19/06/17 11:14, Hans Dedecker wrote: Extend the ubus watchdog cmd with the parameter magicclose; when set and in case the stopped parameter is enabled the kernel watchdog will be stopped by first sending the magic character 'V' followed by a close of the watchdog fd. In case stopped is set

Re: [LEDE-DEV] [PATCH] uhttpd: fix PKG_BUILD_DEPENDS

2017-06-22 Thread Jo-Philipp Wich
Hi, that fix seems wrong to me as build depends must specify source packages. This should be solved in buildroot instead. ~ Jo > Am 22.06.2017 um 02:07 schrieb Daniel Golle : > > uhttpd refered to ustream-ssl as PKG_BUILD_DEPENDS. While this > intuitively seems like the

[LEDE-DEV] [PATCH] shadowsocks-libev: fix tproxy issue for udp traffic

2017-06-22 Thread Zhizhang
ss-rules script in shadowsocks-libev currently is using TPROXY without mark packet first this patch will fix it. Signed-off-by: Zhizhang Deng --- ss-rules2017-05-17 12:40:01.020106879 -0400 +++ ss-rules-new2017-05-17 12:45:19.740116941 -0400 @@ -120,6 +120,9 @@

[LEDE-DEV] [PATCH] scripts: getver.sh: include branch name in a revision string

2017-06-22 Thread Rafał Miłecki
From: Rafał Miłecki The purpose of revision (r* number) is to provide a rough info about build next to the (very) specific SHA-1. Unfortunately without a branch name specified it's a bit misleading and what's more two commits may get the same revision, e.g.: For master branch: