The OpenWrt community is proud to announce the newest stable release of the OpenWrt 21.02 stable version series. It fixes security issues, improves device support, and brings a few bug fixes.
Download firmware images using the OpenWrt Firmware Selector:
The OpenWrt 21.02 stable series is in security maintenance only mode. It is projected to go end of life on 6. April 2023 following the OpenWrt Security support guidelines. We encourage all users of the OpenWrt 21.02 stable series to upgrade to OpenWrt 22.03. https://openwrt.org/docs/guide-developer/security#support_status
Main changes between OpenWrt 21.02.3 and OpenWrt 21.02.4:
Security fixes
wolfssl: Fix security problem (CVE-2022-34293, CVE-2022-38152, CVE-2022-38153 and CVE-2022-39173)
There was no reason to think that it was fixed, but just a note here to mention that the cool "reboot and get a new WAN IP most of the time" problem (certain network interface commands can also do it) is still around for those susceptible to the problem (some aren't, for whatever reason).
This problem began in v21. Unsure if it's around in v22 but I would expect so.
I'd have to delve back into early v21 threads to recall now if certain routers were exempt, but I don't recall that being the case and it's difficult to know that one way or another without a lot more data. It doesn't help clarifying it when there are numerous ISPs, which are wrapped up in this
I think it's more likely that the given ISP creates a condition (relative to DHCP) which encourages the problem (starting with v21 and perhaps continuing in v22) regardless of router model.
Hello.. I would like to inform that the package for curl and libcurl4 is still using the broken version 7.83.1-2.1 (due to the security update for wolfssl) on majority of architecture builds. See links below for mipsel_24kc.
With those versions, curl won't work for HTTPS/SSL URLs. So in short, updating via AUC or downloading the update firmware breaks curl capability to open HTTPS links.
To put this into context: curl is not part of the default OpenWrt installation image. The mentioned broken curl package should only affect setups where curl is installed from opkg packages or as a dependency from other packages.
Thanks for the info, but who should we raise this to? Because a lot of known/popular packages like https-dns-proxy uses this and adblock uses it as the default downloader. So upon setup this will cause confusion as it will not work initially as intended.
If this would be my router I would dive into the source code of the program that throws the error message and find out, what the message is about in detail.
It’s up to you if you worry about this and what you do about it.
If you don’t like to care about such details at all: that’s what the OEM firmware is for. If it breaks you ask manufacturer’s support. With OpenWrt you can do a lot more but you need to support things by yourself.