[PATCH 2/3] treewide: use wpad-basic-wolfssl as default

Daniel Golle daniel at makrotopia.org
Sat Jul 25 06:02:16 EDT 2020

On Sat, Jul 25, 2020 at 10:24:42AM +0200, Stijn Segers wrote:
> ...
> P.S. Is there a way to use mbedtTLS with wpad? That would be neat since one
> could have
> LuCI SSL and wpad lean on the same crypto library. I am now building images
> with mbedTLS
> for LuCI and wolfssl for wpad; it's still smaller than having both build
> with OpenSSL
> but a bit cumbersome nonetheless.

...or at least have a px5g-wolfssl variant as well (that shouldn't be
too hard to do)

I've followed closely on how wolfSSL support was added to hostap.git
and even though wolfSSL's API is largely identical to OpenSSL's API, it
still took a large number of commits and almost two years (!) until
things are now working with wolfSSL as well as they do with OpenSSL.
Of course it'd be great to have wpad-mbedtls but I'm afraid it's far
from being doable for the 2020 relrease.

My original motivation to port the wolfSSL variants of hostapd was to
get 802.11s with SAE working on 4/32 devices which also run a routing
protocol (batman-adv) at the same time and still be able to generate
firmware for those devices using the released ImageBuilder.
For 19.07.4 this will finally be reality.

Regarding the 2020 release:
While I agree that release sysupgrade/factory images should have a
similar featureset (and hence should all come with wpad-basic-wolfssl,
libustream-wolfssl and tbd px5g-wolfssl installed), it'd be nice to
still offer ImageBuilder functional to generate images for 4/32 devices
without having to build everything from source.
Hence it makes sense exclude device images which are anyway not going
to be offered for download (ie. 4/32 devices) from this change and keep
them with wpad-mini. In the end it doesn't matter too much as anyone
using the IB for those devices is anyway likely to modify the default
package selection in order to make things fit into 4MB.

More information about the openwrt-devel mailing list