<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>linux on toorun.dev</title><link>https://toorun.dev/tags/linux/</link><description>Recent content in linux on toorun.dev</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Wed, 20 May 2026 10:00:00 +0000</lastBuildDate><atom:link href="https://toorun.dev/tags/linux/index.xml" rel="self" type="application/rss+xml"/><item><title>Command Injection in C/C++: Why system() with User Input is Dangerous (with Practical Examples)</title><link>https://toorun.dev/posts/command-injection-in-c/c-why-system-with-user-input-is-dangerous-with-practical-examples/</link><pubDate>Wed, 20 May 2026 10:00:00 +0000</pubDate><guid>https://toorun.dev/posts/command-injection-in-c/c-why-system-with-user-input-is-dangerous-with-practical-examples/</guid><description>Command Injection in C/C++: Why system() with User Input is Dangerous Command injection is one of the most common and dangerous security vulnerabilities in C/C++ applications—especially in Linux utilities, embedded systems, and IoT devices. This post explains what command injection is, why it happens, and how to avoid it, with practical examples and secure coding tips.
What is Command Injection? Command injection occurs when an application constructs a shell command using user input and executes it.</description></item><item><title>License Plate Reader – Edge Detection Based Recognition for ARM64</title><link>https://toorun.dev/posts/license-plate-reader-edge-detection-based-recognition-for-arm64/</link><pubDate>Wed, 06 May 2026 12:30:00 +0000</pubDate><guid>https://toorun.dev/posts/license-plate-reader-edge-detection-based-recognition-for-arm64/</guid><description>Project Overview The License Plate Reader is a two-stage license plate detection pipeline designed for real-time operation on resource-constrained devices like the Raspberry Pi. It prioritizes lightweight computation over accuracy, using edge detection and contour analysis instead of machine learning frameworks.
The system is structured as:
Stage 1: Edge detection using Canny edge detection to identify plate-like regions Stage 2: Contour analysis with aspect ratio filtering to isolate license plates Stage 3: Tesseract OCR for text extraction and recognition This approach eliminates dependency on heavy ML frameworks, making it suitable for deployment on embedded ARM64 systems where memory and CPU are limited.</description></item><item><title>About This Technical Blog: Electronics, Embedded Linux, and Real-World Troubleshooting</title><link>https://toorun.dev/posts/tech-notebook-diary/</link><pubDate>Sun, 29 Mar 2026 12:30:00 +0000</pubDate><guid>https://toorun.dev/posts/tech-notebook-diary/</guid><description>This blog is not a polished magazine. It is my personal tech notebook — a place to capture what I learn, remember why I built things, and keep a clear trail of my experiences.
Who I am I am an electronic engineer with more than 15 years of software development experience across the full stack of embedded and systems work. My background starts at bare metal and microcontrollers, extends through embedded Linux and embedded systems, and also includes desktop application development and practical infrastructure work.</description></item><item><title>Linux WiFi TX Power Configuration and Regulatory Constraints</title><link>https://toorun.dev/posts/linux-wifi-tx-power-regulatory-configuration/</link><pubDate>Sat, 29 Nov 2025 12:30:00 +0000</pubDate><guid>https://toorun.dev/posts/linux-wifi-tx-power-regulatory-configuration/</guid><description>WiFi TX Power Configuration Overview WiFi configuration typically allows runtime control of parameters such as channel selection.
However, TX power is not always dynamically configurable and may require configuration during driver initialization.
This is done by providing a TX power configuration binary to the driver.
TX Power Configuration Flow The general workflow:
Generate TX power configuration binary\ Place it in firmware path\ Load driver with configuration\ Verify applied limits Generating TX Power Configuration A configuration file is used to generate a binary representation of TX power limits.</description></item></channel></rss>