Also, since radsecproxy will fail to start if it can't resolve the host
it is configured to contact, it really should be moved up to START=70
rather than the current START=50. Did not include this in the patch
because it's a separate issue; can resubmit if needed, or submit a
separate patch for the
This patch converts the radsecproxy init script to use procd. Works for
me, but not sure if the stop_service part is entirely idiomatic
(omitting it breaks things, though)...
-Toke
diff --git a/net/radsecproxy/files/radsecproxy.init
b/net/radsecproxy/files/radsecproxy.init
index b1b4f8e..b551f0
On 2014-02-27 12:32, Thomas Wouters wrote:
> This change creates a new ip-full variant for the ip package.
> It disables IP_CONFIG_TINY to make some iproute2 features available like
> xfrm, gretap, ...
>
> Signed-off-by: Thomas Wouters
Applied with minor modifications in r39854
Thanks,
- Felix
On 2014-02-28 10:38, Helmut Schaa wrote:
> On some build hosts openssl fails to install since openssl installs itself
> into
> lib64 while the openwrt Makefile expects the libs to end up in lib.
>
> install -m0644
> .../openwrt/build_dir/target-x86_64_uClibc-0.9.33.2/openssl-1.0.1e/ipkg-install/
On 2014-03-05 21:03, Peter Wagner wrote:
> Update openssl to 1.0.1f
>
> This version includes this changes:
>
> Don't include gmt_unix_time in TLS server and client random values
> Fix for TLS record tampering bug CVE-2013-4353
> Fix for TLS version checking bug CVE-2013-6449
> Fi
On 2014-03-08 05:09, Ben West wrote:
> Thanks for the clarification. The basic rates vs. supported rates were
> a bit ambiguous to me. My underlying motivation was to disable lower
> 2.4GHz bitrates, i.e. 1 through 5.5Mbit/s, to conserve airtime. Is such
> a hotplug script nevertheless the best
