Werner

The official supported way to build Armbian is using the build script as it is. We cannot provide support for any 3rd party modifications. Also user customization while building is...

any issues that might pop up when upgrading for example?

Hard to find any useful information around. Some threads popped up at Pihole and raspberry pi forums but nothing really yet. https://nvd.nist.gov/vuln/detail/CVE-2019-15126 Seem to sit mainly in the bcm firmware...

...and probably never will. I tried to find something even though I am not very deep into this topic. What I could find was The firmware-brcm80211 Debian package but this...

Sometimes you are on your own to make the world a bit better. This makes it not less valuable. In my eyes at least.

The Broadcom blobs in either the Xulong repo and the Debian package seem to be quite outdated. `strings` from each binary revealed dates from 2011 to 2018, nothing newer.

This would not fix the security flaw since those blobs seem to be quite old as well. The commit log confirms my results from `strings`: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/log/brcm

> 'Wi-Fi vulnerable to [BroadPwn](https://nvd.nist.gov/vuln/detail/CVE-2017-9417) and [Kr00k](https://nvd.nist.gov/vuln/detail/CVE-2019-15126)'... ...and there is no way for Armbian to fix this without the help of the chipset manufacturer, so please blame them. 😄

There is some communication with Cypress going on I think: https://github.com/linux-mailinglist-archives/linux-kernel.vger.kernel.org.0/blob/15e842ac08ee319a3e941a0b67f8acb8d77fee6e/m

Now there is...