Re: [PATCH 1/3] build: add libustream and certs to default pkgs

2020-09-15 Thread Henrique de Moraes Holschuh
On 27/08/2020 18:47, Paul Spooren wrote: To allow HTTPS usage on a router it requires both certificates (ca-bundle) and a fitting libustream library (libustream-wolfssl) By adding both, uclient-fetch and wget can connect to encrypted HTTP. This allows opkg to update package lists in a more

Re: [PATCH 1/3] build: add libustream and certs to default pkgs

2020-08-28 Thread Petr Štetiar
Karl Palsson [2020-08-28 09:12:04]: Hi, > Doesn't the availability of ustream-*ssl also trigger uhttpd to > generate self signed certs? no, the certs are generated via px5g-mbedtls, so this would need px5g-wolfssl which is not available so far and needs to be done if we would like to ship

Re: [PATCH 1/3] build: add libustream and certs to default pkgs

2020-08-28 Thread Karl Palsson
Paul Spooren wrote: > To allow HTTPS usage on a router it requires both certificates > (ca-bundle) and a fitting libustream library > (libustream-wolfssl) > > By adding both, uclient-fetch and wget can connect to encrypted > HTTP. Doesn't the availability of ustream-*ssl also trigger uhttpd

[PATCH 1/3] build: add libustream and certs to default pkgs

2020-08-27 Thread Paul Spooren
To allow HTTPS usage on a router it requires both certificates (ca-bundle) and a fitting libustream library (libustream-wolfssl) By adding both, uclient-fetch and wget can connect to encrypted HTTP. This allows opkg to update package lists in a more secure fashion. Suggested-by: Petr Štetiar