-time fee. :)
--
Alessandro Di Federico
[1] https://www.startssl.com/?app=37
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
n the future, we'll all use Let's encrypt and be happy [1].
In any case, I'd avoid CACert [2].
--
Alessandro Di Federico
[1] https://letsencrypt.org/
[2] https://bugzilla.mozilla.org/show_bug.cgi?id=215243
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
t; I'd be able to do the CACert.org procedure by myself to get a cert
> with the correct CN even.
I'd suggest to use StatSSL as a CA, which is trusted by major
browser vendors. If someone can forward me an e-mail for
postmas...@openwrt.org I
From: Alessandro Di Federico
Introduce configuration options to build an "hardened" OpenWRT.
Options to enable Stack-Smashing Protection, FORTIFY_SOURCE and RELRO
have been introduced.
uClibc makefile now automatically detects if SSP support is necessary.
hostapd makefile has bee
