packages/libs/libuhttpd, branch masterCommunity maintained packages for OpenWrthttp://x-nagi.com/cgit/packages/atom?h=master2023-02-16T13:28:52Zlibuhttpd: allow building with OpenSSL 3.02023-02-16T13:28:52ZEneas U de Queirozcotequeiroz@gmail.com2023-02-09T14:25:47Zurn:sha1:d0d2f1862bbb4e0780bd73cbe1ae3ba8844521ca
Add -Wno-error=deprecated-declarations to CFLAGS to allow usage of
deprecated API.
Signed-off-by: Eneas U de Queiroz <cotequeiroz@gmail.com>
libuhttpd: update to 3.14.12022-11-06T19:44:00ZRosen Penevrosenp@gmail.com2022-11-05T04:32:42Zurn:sha1:a9f03ff5b0bea317f1673c298e123c7865d694cd
Signed-off-by: Rosen Penev <rosenp@gmail.com>
treewide: fix security issues by bumping all packages using libwolfssl2022-10-04T07:58:29ZPetr Štetiarynezz@true.cz2022-10-03T17:03:15Zurn:sha1:845d81ca0976c82829addc23e9e8b95885c910ee
As wolfSSL is having hard time maintaining ABI compatibility between
releases, we need to manually force rebuild of packages depending on
libwolfssl and thus force their upgrade. Otherwise due to the ABI
handling we would endup with possibly two libwolfssl libraries in the
system, including the patched libwolfssl-5.5.1, but still have
vulnerable services running using the vulnerable libwolfssl-5.4.0.
So in order to propagate update of libwolfssl to latest stable release
done in commit ec8fb542ec3e4 ("wolfssl: fix TLSv1.3 RCE in uhttpd by
using 5.5.1-stable (CVE-2022-39173)") which fixes several remotely
exploitable vulnerabilities, we need to bump PKG_RELEASE of all packages
using wolfSSL library.
Same bump has been done in buildroot in commit f1b7e1434f66 ("treewide:
fix security issues by bumping all packages using libwolfssl").
Signed-off-by: Petr Štetiar <ynezz@true.cz>
libuhttpd: add compatibility for wolfssl >= 5.02022-01-06T22:18:23ZSergey V. Lobanovsergey@lobanov.in2022-01-03T16:41:37Zurn:sha1:9a9f26796bdf4bd6ebe5a9aee9dcb2feee54780f
NTRU support has been removed in wolfssl 5.0 so it is required to
mask NTRU specific code if wolfssl >= 5.0
Signed-off-by: Sergey V. Lobanov <sergey@lobanov.in>
libuhttp: don't build examples2021-09-08T21:44:02ZRosen Penevrosenp@gmail.com2021-09-06T08:55:37Zurn:sha1:21e5a1e7d3e55a0c49af9e5a6c8dee6c0255f507
Speeds up compilation and potentially fixes it.
Signed-off-by: Rosen Penev <rosenp@gmail.com>
treewide: back to cmake.mk2021-06-13T04:05:01ZRosen Penevrosenp@gmail.com2021-06-10T23:27:06Zurn:sha1:2e654b19f38f1f941c70a5adcdac6311234362c3
Ninja was merged to base and therefore we can now use normal cmake.mk
Signed-off-by: Rosen Penev <rosenp@gmail.com>
libuhttpd: Update to 3.12.12021-06-07T14:43:10ZJianhui Zhaozhaojh329@gmail.com2021-06-07T02:22:12Zurn:sha1:4c163b0b123d26538710b78f1ef8f4f47bcdbc0b
Signed-off-by: Jianhui Zhao <zhaojh329@gmail.com>
libuhttpd: Update to 3.12.02021-06-04T17:52:56ZJianhui Zhaozhaojh329@gmail.com2021-06-04T12:08:46Zurn:sha1:756d9e906bfeb713e6b5e3e16939d8eed4f66b9f
Signed-off-by: Jianhui Zhao <zhaojh329@gmail.com>
libuhttpd: Update to 3.11.02021-04-09T05:32:11ZJianhui Zhaozhaojh329@gmail.com2021-04-08T06:58:57Zurn:sha1:3aa128f00745db22d1f2ed81d3bb3704d6c65780
Signed-off-by: Jianhui Zhao <zhaojh329@gmail.com>
treewide: build CMake projects with Ninja2021-03-28T04:51:50ZRosen Penevrosenp@gmail.com2021-03-04T22:45:01Zurn:sha1:a31b7320077c340268d31642ded69cc66fbc230c
faster to compile.
A small selection of packages was tested going from:
Executed in 696.30 secs fish external
usr time 82.98 mins 395.00 micros 82.98 mins
sys time 9.02 mins 0.00 micros 9.02 mins
to:
Executed in 592.20 secs fish external
usr time 84.84 mins 361.00 micros 84.84 mins
sys time 8.85 mins 57.00 micros 8.85 mins
Tested by running make -j 12 and wiping staging/build_dir/target_x
Signed-off-by: Rosen Penev <rosenp@gmail.com>