nickbeardedMost 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 💪
cnx-software.com [Unofficial]Boardcon PICOT536 SoM and EMT536 SBC feature Allwinner T536 Edge AI processor
Boardcon PICOT536 SoM and EMT536 SBC feature Allwinner T536 Edge AI processor
Back in April last year, Allwinner released the T536 SoC, and since then, we’ve seen MYiR Tech and Forlinx introduce SoM and SBC based on it. The latest to join the lineup is Boardcon, which has recently launched the PICOT536 SoM and EMT536 SBC for industrial HMI, machine vision, robotics, and other edge computing applications. As a reminder, the Allwinner T536 SoC features a quad-core Arm Cortex-A55 CPU, XuanTie E907 and E902 RISC-V coprocessors, and a 2 TOPS NPU for edge AI. The module comes with up to 8GB LPDDR4/LPDDR4X memory, up to 64GB eMMC flash, an optional WiFi 6 and Bluetooth 5.4 module, and a 314-pin MXM edge connector exposing I/Os such as MIPI DSI and LVDS, camera inputs, audio inputs and outputs, Gigabit Ethernet, PCIe, USB 3.0, and more. PICOT536 System-on-Module PICOT536 specifications: SoC – Allwinner T536 CPU – Quad-core Arm Cortex-A55 at up to 1.6GHz, RISC-V XuanTie
Resilience TheatreStories 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: https://codeberg.org/resiliencetheatre/rpi-extree/src/branch/main/link.md
#opsec #comsec #outofband #opensource #buildroot #embedded #lvgl #prepping #preparedness #nitrokey #fido2 #satcom
#opsec #comsec #outofband #opensource #buildroot #embedded #lvgl #prepping #preparedness #nitrokey #fido2 #satcom
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
Fiona@adulau @gcve 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 @Bubu 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.
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 @Bubu 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.
GitHub - fkie-cad/nvd-json-data-feeds: Community reconstruction of the legacy JSON NVD Data Feeds. This project uses and redistributes data from the NVD API but is neither endorsed nor certified by the NVD.
Community reconstruction of the legacy JSON NVD Data Feeds. This project uses and redistributes data from the NVD API but is neither endorsed nor certified by the NVD. - fkie-cad/nvd-json-data-feeds
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 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…LeafKVM open-source hardware IP KVM offers WiFi 5, PoE, USB-C serial console, and 2.4-inch touchscreen display (Crowdfunding)
LeafKVM open-source hardware IP KVM offers WiFi 5, PoE, USB-C serial console, and 2.4-inch touchscreen display (Crowdfunding)
LeafKVM is a wireless and PoE open-source hardware IP KVM based on Rockchip RV1126B SoC with 512MB RAM and a microSD card slot for storage. Like other IP KVMs, it enables remote access to computers and servers, even at the BIOS level or when the machine is unresponsive, by emulating keyboard, mouse, and video through HDMI/VGA and USB ports. Other features include a 2.4-inch touchscreen display for configuration and guest video mirroring, a USB-C port for serial debug, a USB Type-A port for expansion (e.g., power control), and an ultra-low latency of less than 100ms. LeafKVM specifications: SoC - Rockchip RV1126B CPU – Quad-core Arm Cortex-A53 up to 1.6 GHz GPU – 2D Graphics Engine VPU Video Decoder – H.265/H.264 up to 3840×2160 @ 30fps Video Encoder – H.265, H.264, JPEG up to 12Mbps @ 30fps JPEG Decoder AI accelerator – Rockchip NPU engine up to 3 TOPS (INT8); likely not
Ezurio Tungsten 510/700 SMARC SoM features MediaTek Genio 510/700 AIoT SoC, dual GbE, WiFi 6
Ezurio Tungsten 510/700 SMARC SoM features MediaTek Genio 510/700 AIoT SoC, dual GbE, WiFi 6
Ezurio Tungsten 510 and Tungsten 700 SMARC 2.1 compliant system-on-module powered by MediaTek Genio 510 hexa-core and Genio 700 octa-core Cortex-A78/A55 AIoT SoCs with an up to 4 TOPS NPU. The SMARC modules feature 4GB or 8GB LPDDR4 memory and 16GB flash by default (upgradeable up to 128GB), offer dual Gigabit Ethernet, WiFi 6 and Bluetooth 5.2 connectivity, and various interfaces exposed through a standard 314-pin MXM connector, including HDMI, DisplayPort, eDP, and MIPI DSI display interfaces, two MIPI CSI camera interfaces, two I2S audio interface, PCIe Gen2 x1, and more. Ezurio Tungsten 510/700 specifications: SoC (one or the other) MediaTek Genio 510 (MT8370) CPU - Hexa-core processor with 2x Arm Cortex-A78 core up to 2.2 GHz, 4x Cortex-A55 cores up to 2 GHz GPU - Arm Mali-G57 MC2 GPU VPU - 4Kp60 H.265, AV1, VP9, H.264 video decoding, 4Kp30 H.265 and H.264 video encoding Accelerators - Up to 3.2
LinuxGizmos.com [Unofficial]Comet Q KVM supports browser-based control of laptops and iPhones over Wi-Fi 6
