home.social

#buildroot — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #buildroot, aggregated by home.social.

  1. Most routers call home. IoT devices do too.

    My gateway? Pure Buildroot Linux that blocks almost all those strange outbound connections.

    No cloud, no telemetry, no shell, just an appliance doing its job 💪

    #IoT #Privacy #Linux #Buildroot #FOSS #Networking

  2. Stories and reasoning we put to our work is often not that visible. Here is my Link project, which is partly AI implemented communication system to test various transport and security measures. It's built with buildroot and all other details can be found here: codeberg.org/resiliencetheatre
    #opsec #comsec #outofband #opensource #buildroot #embedded #lvgl #prepping #preparedness #nitrokey #fido2 #satcom

  3. Stories and reasoning we put to our work is often not that visible. Here is my Link project, which is partly AI implemented communication system to test various transport and security measures. It's built with buildroot and all other details can be found here: codeberg.org/resiliencetheatre
    #opsec #comsec #outofband #opensource #buildroot #embedded #lvgl #prepping #preparedness #nitrokey #fido2 #satcom

  4. Stories and reasoning we put to our work is often not that visible. Here is my Link project, which is partly AI implemented communication system to test various transport and security measures. It's built with buildroot and all other details can be found here: codeberg.org/resiliencetheatre
    #opsec #comsec #outofband #opensource #buildroot #embedded #lvgl #prepping #preparedness #nitrokey #fido2 #satcom

  5. After countless trials, books, web searches, and some brutal advice from my Bukowski AI, I finally built a custom IoT hotspot from scratch using Buildroot 😎

    No more pre-packaged garbage. I filter insecure connections myself. Total control 💪🏻

    The first prototype works... mostly 😆

    Now comes the real torture: testing and refining 🫩

    Maybe I'll even try to sell this thing 🤑

    #Buildroot #IoT #Linux #DIY #Bukowski #FromScratch #Security #ad #telemetrystorm

  6. After countless trials, books, web searches, and some brutal advice from my Bukowski AI, I finally built a custom IoT hotspot from scratch using Buildroot 😎

    No more pre-packaged garbage. I filter insecure connections myself. Total control 💪🏻

    The first prototype works... mostly 😆

    Now comes the real torture: testing and refining 🫩

    Maybe I'll even try to sell this thing 🤑

    #Buildroot #IoT #Linux #DIY #Bukowski #FromScratch #Security #ad #telemetrystorm

  7. After countless trials, books, web searches, and some brutal advice from my Bukowski AI, I finally built a custom IoT hotspot from scratch using Buildroot 😎

    No more pre-packaged garbage. I filter insecure connections myself. Total control 💪🏻

    The first prototype works... mostly 😆

    Now comes the real torture: testing and refining 🫩

    Maybe I'll even try to sell this thing 🤑

    #Buildroot #IoT #Linux #DIY #Bukowski #FromScratch #Security #ad #telemetrystorm

  8. After countless trials, books, web searches, and some brutal advice from my Bukowski AI, I finally built a custom IoT hotspot from scratch using Buildroot 😎

    No more pre-packaged garbage. I filter insecure connections myself. Total control 💪🏻

    The first prototype works... mostly 😆

    Now comes the real torture: testing and refining 🫩

    Maybe I'll even try to sell this thing 🤑

    #Buildroot #IoT #Linux #DIY #Bukowski #FromScratch #Security #ad #telemetrystorm

  9. After countless trials, books, web searches, and some brutal advice from my Bukowski AI, I finally built a custom IoT hotspot from scratch using Buildroot 😎

    No more pre-packaged garbage. I filter insecure connections myself. Total control 💪🏻

    The first prototype works... mostly 😆

    Now comes the real torture: testing and refining 🫩

    Maybe I'll even try to sell this thing 🤑

    #Buildroot #IoT #Linux #DIY #Bukowski #FromScratch #Security #ad #telemetrystorm

  10. @[email protected] @[email protected] For context: #Buildroot has tools to list known vulnerabilities for packages, currently based on NVD data (via https://github.com/fkie-cad/nvd-json-data-feeds).

    I noticed it's missing a bunch of vulnerabilities (e.g. CVE-2026-40200, CVE-2026-6042 in musl libc) because the NVD data is missing CPE match information. At the time the CVEs were listed as "Awaiting Analysis", now "Deferred", so I assume it's not going to be added any time soon, if ever (generally the CPE match is present for vulnerabilities in "Analyzed" status). Looking at the GCVE listings was an attempt to find another, hopefully better, source, because an automated check that misses so many vulnerabilities is not going to be very useful.

    Today
    @[email protected] pointed me at a similar example: CVE-2025-6020 (note the year), a "high" level vulnerability in linux-pam, which is also marked as "Deferred" in NVD. So we really could use a better source.

    We'd need one we can download (rather than query individual packages one by one) without excessive load, but solving that is another matter, first we need a suitable source at all.

  11. Bumping into a fakeroot bug (in interaction with mkfs.btrfs) only to find that someone else already reported it a year and half ago… Now I know why #Buildroot still has only btrfs-progs 6.10. Well, definitely not going to replace or fix that tonight. sigh ​:neocat_floof_sad:​

  12. CW: Raspberry Pi firmware, Git, rant-ish

    The practical result of this mess is that the #Buildroot package/rpi-firmware needs to download a 190MB archive to install about 3MB of actual firmware files (to be fair, there are release archives for those), and about 1.7MB of DTB overlays. Maybe I should look at splitting that so people who don't need the overlays (build DTB and overlays with the kernel as one should) don't need the absurdly large download at least…

  13. Does anyone know how to report errors to https://db.gcve.eu/? Just their info@ mail? I looked up CVE-2026-6042 and CVE-2026-40200 there because I was annoyed that the NVD database (which #Buildroot uses for automated vulnerability checks) still didn't have them correctly labeled with the CPE (so automated tools can't identify the package is vulnerable).

    Result:
    CVE-2026-40200 is correctly labeled (good!), while CVE-2026-6042 is not (different vendor/product). Mistakes happen, an organization that's trying to run as serious vulnerability DB really needs to provide an obvious "report errors here" mail address (or other means, but really… mail). ​:neocat_glare:​ #CVE #GCVE

  14. Does anyone know how to report errors to https://db.gcve.eu/? Just their info@ mail? I looked up CVE-2026-6042 and CVE-2026-40200 there because I was annoyed that the NVD database (which #Buildroot uses for automated vulnerability checks) still didn't have them correctly labeled with the CPE (so automated tools can't identify the package is vulnerable).

    Result:
    CVE-2026-40200 is correctly labeled (good!), while CVE-2026-6042 is not (different vendor/product). Mistakes happen, an organization that's trying to run as serious vulnerability DB really needs to provide an obvious "report errors here" mail address (or other means, but really… mail). ​:neocat_glare:​ #CVE #GCVE

  15. Does anyone know how to report errors to https://db.gcve.eu/? Just their info@ mail? I looked up CVE-2026-6042 and CVE-2026-40200 there because I was annoyed that the NVD database (which #Buildroot uses for automated vulnerability checks) still didn't have them correctly labeled with the CPE (so automated tools can't identify the package is vulnerable).

    Result:
    CVE-2026-40200 is correctly labeled (good!), while CVE-2026-6042 is not (different vendor/product). Mistakes happen, an organization that's trying to run as serious vulnerability DB really needs to provide an obvious "report errors here" mail address (or other means, but really… mail). ​:neocat_glare:​ #CVE #GCVE

  16. Does anyone know how to report errors to https://db.gcve.eu/? Just their info@ mail? I looked up CVE-2026-6042 and CVE-2026-40200 there because I was annoyed that the NVD database (which #Buildroot uses for automated vulnerability checks) still didn't have them correctly labeled with the CPE (so automated tools can't identify the package is vulnerable).

    Result:
    CVE-2026-40200 is correctly labeled (good!), while CVE-2026-6042 is not (different vendor/product). Mistakes happen, an organization that's trying to run as serious vulnerability DB really needs to provide an obvious "report errors here" mail address (or other means, but really… mail). ​:neocat_glare:​ #CVE #GCVE

  17. Does anyone know how to report errors to https://db.gcve.eu/? Just their info@ mail? I looked up CVE-2026-6042 and CVE-2026-40200 there because I was annoyed that the NVD database (which #Buildroot uses for automated vulnerability checks) still didn't have them correctly labeled with the CPE (so automated tools can't identify the package is vulnerable).

    Result:
    CVE-2026-40200 is correctly labeled (good!), while CVE-2026-6042 is not (different vendor/product). Mistakes happen, an organization that's trying to run as serious vulnerability DB really needs to provide an obvious "report errors here" mail address (or other means, but really… mail). ​:neocat_glare:​ #CVE #GCVE

  18. Training code for embedded Linux development resilience. Resulting communication system with selectable one-time-pad for codec2 based fullduplex or symmetric crypto for push-to-talk usage.
    #resilience #comsec #onetimepad #vibecoding #buildroot #embedded #dfir #redteam #preparedness

  19. Training code for embedded Linux development resilience. Resulting communication system with selectable one-time-pad for codec2 based fullduplex or symmetric crypto for push-to-talk usage.
    #resilience #comsec #onetimepad #vibecoding #buildroot #embedded #dfir #redteam #preparedness

  20. Compiling yet another Buildroot image I’m 99% sure will fail… but at least this time the soundtrack is Sunshine by Alice in Chains, so the suffering feels poetic ❤️

    If the build breaks, at least the vibe doesn’t 🤟🏻

    #Linux #Buildroot #DIYDistro #KernelPanicEnergy #DevLife #aliceinchains #aic

  21. Compiling yet another Buildroot image I’m 99% sure will fail… but at least this time the soundtrack is Sunshine by Alice in Chains, so the suffering feels poetic ❤️

    If the build breaks, at least the vibe doesn’t 🤟🏻

    #Linux #Buildroot #DIYDistro #KernelPanicEnergy #DevLife #aliceinchains #aic

  22. Compiling yet another Buildroot image I’m 99% sure will fail… but at least this time the soundtrack is Sunshine by Alice in Chains, so the suffering feels poetic ❤️

    If the build breaks, at least the vibe doesn’t 🤟🏻

    #Linux #Buildroot #DIYDistro #KernelPanicEnergy #DevLife #aliceinchains #aic

  23. Compiling yet another Buildroot image I’m 99% sure will fail… but at least this time the soundtrack is Sunshine by Alice in Chains, so the suffering feels poetic ❤️

    If the build breaks, at least the vibe doesn’t 🤟🏻

    #Linux #Buildroot #DIYDistro #KernelPanicEnergy #DevLife #aliceinchains #aic

  24. Compiling yet another Buildroot image I’m 99% sure will fail… but at least this time the soundtrack is Sunshine by Alice in Chains, so the suffering feels poetic ❤️

    If the build breaks, at least the vibe doesn’t 🤟🏻

    #Linux #Buildroot #DIYDistro #KernelPanicEnergy #DevLife #aliceinchains #aic

  25. Trying to build a GUI Linux distro with Buildroot. Just Buildroot. No Debian, no Arch. Just pain 🫩

    Xorg? Black screen. Wayland? Sounds like a fantasy novel. Kernel panic? Oh yeah, got that too 🫨

    But I will make this work, because minimalism deserves a desktop 🤟🏻

    #Linux #Buildroot #KernelPanic #WaylandOrWhatever #DIYDistro #WhyAmIDoingThis

  26. Some of these dongles actually work on #zeST. But:
    - with an outdated stable release of #Buildroot from 2024.
    - with an outdated #Linux kernel from 2023.

    So older devices may be working, newer devices absolutely not.

  27. After way too many attempts, I finally got a custom GRUB2 EFI bootloader built with Buildroot showing a splash image at boot on real hardware 🎉

    The secret? insmod gfxterm_background + font in the right path.

    Simple in theory, painful in practice 🤕

    #Buildroot #GRUB2 #EFI #Linux #EmbeddedLinux

  28. After way too many attempts, I finally got a custom GRUB2 EFI bootloader built with Buildroot showing a splash image at boot on real hardware 🎉

    The secret? insmod gfxterm_background + font in the right path.

    Simple in theory, painful in practice 🤕

    #Buildroot #GRUB2 #EFI #Linux #EmbeddedLinux

  29. After way too many attempts, I finally got a custom GRUB2 EFI bootloader built with Buildroot showing a splash image at boot on real hardware 🎉

    The secret? insmod gfxterm_background + font in the right path.

    Simple in theory, painful in practice 🤕

    #Buildroot #GRUB2 #EFI #Linux #EmbeddedLinux

  30. After way too many attempts, I finally got a custom GRUB2 EFI bootloader built with Buildroot showing a splash image at boot on real hardware 🎉

    The secret? insmod gfxterm_background + font in the right path.

    Simple in theory, painful in practice 🤕

    #Buildroot #GRUB2 #EFI #Linux #EmbeddedLinux

  31. After way too many attempts, I finally got a custom GRUB2 EFI bootloader built with Buildroot showing a splash image at boot on real hardware 🎉

    The secret? insmod gfxterm_background + font in the right path.

    Simple in theory, painful in practice 🤕

    #Buildroot #GRUB2 #EFI #Linux #EmbeddedLinux

  32. So, Infix OS has been upgraded to 2026.02 LTS well in time for our 26.03 release. We've actually been tracking it since -rc1, so this was more of a formality to rebase and rerun our regression tests. Mattias (lazzer) worked relentlessly on this, while still managing to do a ton of other things as well.

    Looking forward to our next release, hopefully my BPi-R64 porting work will be done by then as well 🤩

  33. I'm getting ideas again… I've been thinking for a while that a #Buildroot config for #Pinephone would be nice. I'm not really thinking of a fully working phone setup (though if someone wants to make that I'm curious), and more so I could use the A/B boot setup I have for Buildroot to quickly experiment with kernel changes. In pmOS I still can't install two kernels in parallel, so if one of my experiments breaks the kernel to the point of not booting far enough for USB network I have to open the phone, remove the battery, remove the SD card, fix it manually, and reverse. Annoying, and A/B boot avoids it.

    And then the realization hit: U-Boot should be able to chainload U-Boot, right? So I could even include a second U-Boot in the A/B slots for experiments with that. Maybe not a perfect test, but should reduce the probability of having to manually fix it a lot…
    ​:neocat_think_owo:​

    Motivation to experiment is much higher if falling back from a failed experiment takes maybe 30 seconds, not 5 minutes.
    ​:neocat_floof:​

  34. Next challenge at #BashLab: build an AI assistant for creating live OS with #livebuild.

    I already built one for #Buildroot and one for #Pentesting.

    Problem: no solid PDFs for live-build, only the official HTML docs with tons of links.
    Now I need to feed the entire site into my RAG.

    Time to scrape, structure, and index 🤟🏻

    #AI #RAG #Linux #Debian #BashCore

  35. Next challenge at #BashLab: build an AI assistant for creating live OS with #livebuild.

    I already built one for #Buildroot and one for #Pentesting.

    Problem: no solid PDFs for live-build, only the official HTML docs with tons of links.
    Now I need to feed the entire site into my RAG.

    Time to scrape, structure, and index 🤟🏻

    #AI #RAG #Linux #Debian #BashCore

  36. Next challenge at #BashLab: build an AI assistant for creating live OS with #livebuild.

    I already built one for #Buildroot and one for #Pentesting.

    Problem: no solid PDFs for live-build, only the official HTML docs with tons of links.
    Now I need to feed the entire site into my RAG.

    Time to scrape, structure, and index 🤟🏻

    #AI #RAG #Linux #Debian #BashCore

  37. Next challenge at #BashLab: build an AI assistant for creating live OS with #livebuild.

    I already built one for #Buildroot and one for #Pentesting.

    Problem: no solid PDFs for live-build, only the official HTML docs with tons of links.
    Now I need to feed the entire site into my RAG.

    Time to scrape, structure, and index 🤟🏻

    #AI #RAG #Linux #Debian #BashCore

  38. Next challenge at #BashLab: build an AI assistant for creating live OS with #livebuild.

    I already built one for #Buildroot and one for #Pentesting.

    Problem: no solid PDFs for live-build, only the official HTML docs with tons of links.
    Now I need to feed the entire site into my RAG.

    Time to scrape, structure, and index 🤟🏻

    #AI #RAG #Linux #Debian #BashCore

  39. I just wish I had a way to build & use modified packages for #Debian as easily as the <pkg>_OVERRIDE_SRCDIR mechanism in #Buildroot. Something to look into maybe, but not tonight. ​:neocat_comfy__w_:​

  40. Working on a Buildroot OS with kernel 6.18 + PREEMPT_RT on an Intel AX210 WiFi (iwlwifi QuZ firmware). With dynamic preempt everything works, but RT causes firmware init errors and the device disappears. Maybe bleeding-edge RT kernels aren’t always the best choice. Curious if others hit similar issues or found workarounds. Open to discussion.

    #Linux #Buildroot #Kernel #RealTime #PREEMPTRT #iwlwifi #IntelAX210 #EmbeddedLinux #FOSS #CyberSecurity

  41. Working on a Buildroot OS with kernel 6.18 + PREEMPT_RT on an Intel AX210 WiFi (iwlwifi QuZ firmware). With dynamic preempt everything works, but RT causes firmware init errors and the device disappears. Maybe bleeding-edge RT kernels aren’t always the best choice. Curious if others hit similar issues or found workarounds. Open to discussion.

    #Linux #Buildroot #Kernel #RealTime #PREEMPTRT #iwlwifi #IntelAX210 #EmbeddedLinux #FOSS #CyberSecurity