I guess that the missing hostapd-common package for mipsel_24kc is a separate issue. I wonder where to report it. For mipsel_24kc_24kf this package exists. Can't build an image for my TP-Link RE205 V3.
Update: hostapd-common is built again
Most of these issues are a result of https://github.com/openwrt/docker/commit/342193af4537f549095f2df04bfee29b99aae725#commitcomment-149974606, i.e., mis-configured docker images for some of the -RC2 targets. Some will work, some won't, as @aparcar merged that fix after the rc2 builds had partially completed.
Trying to build 24.10.0-rc2 I received the following error. The image built and flashed OK. Just an FYI.
Trying to build 24.10.0-rc2.
Got:
Unsupported profile: xiaomi_redmi-router-ax6000-ubootmod
Does this mean we should expect a rebiuld of RC2 or will it simply be called RC3?
It's not the imagebuilders or RC2 builds themselves that are at fault, those are fine. It's the docker container images that are used by the ASU server that have the issue (if you go to downloads and grab any of the rc2 images or imagebuilders, they'll work as-is). The docker containers are built on a per-target basis, as the builds complete and the imagebuilder becomes available, so if there's a way to manually fire off re-generation of them, it shouldn't take very long at all (https://github.com/openwrt/docker/commit/342193af4537f549095f2df04bfee29b99aae725#commitcomment-149974606)
Thank you for clarifying. I had another go at using the OpenWRT Firmware Selector with custom package selection and it seems to be generating images and packages as expected for both aforementioned devices.
Snapshot 28262 is out, but the Firmware Selector is now completely broken. Doesn't do anything when requesting a new custom build. It just stays there, no response.
Can anybody fix it?
The sysupgrade.openwrt.org site is down for a while, undergoing some testing. Expect it back in a day or two.
For those who want to know more, this is what happened: https://github.com/openwrt/asu/security/advisories/GHSA-r3gq-96h6-3v7q
What was the hack trying to accomplish had it succeeded and a user installed the altered firmware? Did it come from China?
They don't mention being hacked, only that the possibility existed for an attacker to do so and that a security researcher reported it to them.
How to know if I was (possibly) affected by this vulnerability?
Has anyone managed to get a custom snapshot build with Firmware Selector yet? It hasn't been working for several days, but @aparcar says the sysupgrade.openwrt.org server (which is being queried by FS to actually build a custom image) works for him.
Very strange, to say the least. The lack of transparency is concerning, especially considering the security issue from last week.
@KrypteX I'm not sure if it's lost in translation but I find your choice of word very strange, to say the least. Please find my response under one of your other "bug reports" Can't reach attended sysupgrade server from luci, diadnostic ping, or browser - #5 by aparcar
We can't properly, that's why it's recommended to install a fresh installation.
@aparcar I'm not sure what choice of my words made you misunderstand. If it's not working, it's not working. Hence I'm reporting a bug. This shouldn't be some hard-to-get philosophy for anyone, whether we are native English speakers or not.
Anyway, thanks for the heads up.
Dumb question but when you say fresh installation, do you mean reflashing the firmware, performing a factory reset or something else?
It's not a dumb question.
Re flashing the firmware and to be extra safe without keeping settings.
What I would do is before flashing make a backup of your settings and peruse said backup with a text editor to make sure there is nothing funky in them. Afterwards restore your settings.