The OpenWrt community is proud to announce the eighth service release of OpenWrt 19.07. It fixes security issues, improves device support, and brings a few bug fixes.
The main changes from OpenWrt 19.07.7 are:
Security fixes
Fix FragAttacks (fragmentation and aggregation attacks) vulnerabilities in cfg80211, mac80211, ath10k and ath10k-ct
We are not sure if some closed source firmware files are still affected by these problems.
The builds for ar71xx/nand and lantiq/falcon failed because of some network problems in the initial build, I retriggered builds for these two targets yesterday and the new images are available now.
In the past on 19.x I used ath10k because of the better stability for my Android LOS devices but it seems that with this release ath10k-ct is as good (or better) as the aforementioned. Perhaps coincidence or some neural misconception ;- ) Anyway...a big thank you to the involved developers!
For the 21.02 release preparation we did bigger changes to the build bot infrastructure like upgrading build bot and this also affected the 19.07 build bots. Probably something went wrong and the sha256sums.asc files were not generated or coped any more.
Normally I have to announce an update to my family and am "forced" to reinstall the non-CT drivers mainly because of Xbox connection and some other issues.
A few days ago I did a "silent" update (R7800 router and R7800 AP) and keeping the standard CT drivers on both devices. No complaints for a few days now.
Just to be clear, are you saying that an upgrade like this normally necessities re-doing a non-CT configuration, if that's what someone had and wants? If so, I guess I should have known, since they're packages like anything else you might have installed that would need re-installing, but I thought of these more as drivers, I guess.
After an update (sysupgrade or factory) it is necessary to reinstall any package but the standard ones. This also applies to the non-CT drivers (CT drivers are the standard; since 19.07?).
I don't know if there are any exceptions on this.
There are probably more ways to manage an upgrade of a non standard configuration but that question is better answered by an expert.
I have done my own shell-script and added it to the files that are backed, so after an upgrade that keeps the configuration I just need to execute that script and it installs me all packages again, another reboot, and the system is (hopefully) back withe the upgraded openwrt and the according packages.
The 19.07.8 release is now signed with GPG and the signature was uploaded. @jow added the missing signatures and uploaded them.
The signing key for OpenWrt 19.07 had expired and then gpg just did not created a signature.