Mirror of packages feed https://git.openwrt.org/feed/packages/atom?h=master 2024-10-26T11:49:06Z 2024-10-26T11:49:06Z Jianhui Zhao 2024-10-26T03:18:27Z urn:sha1:da42d2f1ba1e2a28b4058d24434468590b83e62c Signed-off-by: Jianhui Zhao <zhaojh329@gmail.com> 2023-02-16T13:28:52Z Eneas U de Queiroz 2023-02-09T14:25:47Z urn: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> 2022-11-06T19:44:00Z Rosen Penev 2022-11-05T04:32:42Z urn:sha1:a9f03ff5b0bea317f1673c298e123c7865d694cd Signed-off-by: Rosen Penev <rosenp@gmail.com> 2022-10-04T07:58:29Z Petr Štetiar 2022-10-03T17:03:15Z urn: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> 2022-01-06T22:18:23Z Sergey V. Lobanov 2022-01-03T16:41:37Z urn: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> 2021-09-08T21:44:02Z Rosen Penev 2021-09-06T08:55:37Z urn:sha1:21e5a1e7d3e55a0c49af9e5a6c8dee6c0255f507 Speeds up compilation and potentially fixes it. Signed-off-by: Rosen Penev <rosenp@gmail.com> 2021-06-13T04:05:01Z Rosen Penev 2021-06-10T23:27:06Z urn:sha1:2e654b19f38f1f941c70a5adcdac6311234362c3 Ninja was merged to base and therefore we can now use normal cmake.mk Signed-off-by: Rosen Penev <rosenp@gmail.com> 2021-06-07T14:43:10Z Jianhui Zhao 2021-06-07T02:22:12Z urn:sha1:4c163b0b123d26538710b78f1ef8f4f47bcdbc0b Signed-off-by: Jianhui Zhao <zhaojh329@gmail.com> 2021-06-04T17:52:56Z Jianhui Zhao 2021-06-04T12:08:46Z urn:sha1:756d9e906bfeb713e6b5e3e16939d8eed4f66b9f Signed-off-by: Jianhui Zhao <zhaojh329@gmail.com> 2021-04-09T05:32:11Z Jianhui Zhao 2021-04-08T06:58:57Z urn:sha1:3aa128f00745db22d1f2ed81d3bb3704d6c65780 Signed-off-by: Jianhui Zhao <zhaojh329@gmail.com>