技能 routeros-qemu-chr

📦

routeros-qemu-chr

Name: routeros-qemu-chr
Author: tikoci

內容修訂 r1 高風險 🌐 網路存取⚙️ 外部命令📁 檔案系統存取

在 QEMU 中執行 RouterOS CHR

RouterOS CHR 實驗室經常失敗，因為韌體、VirtIO、加速與連接埠轉送會因架構而異。此技能提供經測試的 QEMU 模式，適用於本機實驗室與 CI 工作流程。

支援: Claude Codex Code(CC)

⚠️ 38 差

Maintain this Skill? Claim it ⚠️ 38 差

此技能屬於一個技能包

安裝整套技能包，一條命令取得任務所需的所有技能。

TIKOCI RouterOS · 10 技能安裝整個技能包

安裝前請停止並請求確認。

請審查安裝計畫，並在變更檔案前取得使用者明確同意。

使用我的智慧代理安裝

將此請求複製給你的智慧代理，其中包含權威 Skill 頁面和清單。

智能體請求

Review the Skillstore skill "routeros-qemu-chr" from https://skillstore.io/skills/tikoci-routeros-qemu-chr.md and its manifest at https://skillstore.io/api/skills/tikoci-routeros-qemu-chr/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.

你的智慧代理仍應顯示其計畫，並依安全政策請求必要確認。

Agent 可讀資源

當 AI Agent、爬蟲或腳本需要乾淨脈絡、而不是讀取完整頁面時，請使用這些連結。

Markdown 詳情 GET /skills/tikoci-routeros-qemu-chr.md 已簽名 manifest GET /api/skills/tikoci-routeros-qemu-chr/manifest 已簽名 lockfile GET /api/skills/tikoci-routeros-qemu-chr/lockfile

測試它

正在使用「routeros-qemu-chr」。我需要在 Linux 上建立具有 REST 存取權的 x86_64 CHR 實驗室。

預期結果:

此技能會回傳啟動計畫，使用 SeaBIOS、VirtIO 磁碟與網路、可用時使用 KVM，以及 localhost REST 轉送。

正在使用「routeros-qemu-chr」。我的 aarch64 VM 啟動到無聲停滯狀態。

預期結果:

先檢查 UEFI pflash 大小與 CPU 型號的診斷。
提醒使用明確的 VirtIO PCI 裝置，而不是 aarch64 簡寫。
當硬體加速不可用時，提供 TCG 後援計畫。

正在使用「routeros-qemu-chr」。我需要 CI 來測試 RouterOS 套件行為。

預期結果:

此技能會概述映像檔下載、磁碟轉換、QEMU 啟動、就緒檢查、套件上傳、重新啟動處理與清理。

安全審計

高風險

v6 • 2026/7/7 開啟版本化報告

No prompt injection, hidden exfiltration, or malicious intent was found. The skill is legitimate RouterOS CHR and QEMU guidance, but it includes privileged host changes, external downloads, VM process launch, local service exposure, and predictable temp paths. These risks should be documented and gated by user confirmation before execution.

已掃描檔案

799

分析行數

複核項目

已忽略的誤報

已確認的安全問題 (4)

高

references/github-actions-ci.md:46

World-Writable KVM Device Permission

The CI pattern writes a udev rule that sets the KVM device mode to 0666. This broadens virtualization access to every local user on shared or self-hosted runners.

The exact rule sets MODE="0666" for the KVM device. The impact is clear in shared runner or multi-user host contexts.

中

references/github-actions-ci.md:162

Network reconnaissance

sshpass -p '' scp -P 9122 -o StrictHostKeyChecking=no "$pkg" admin@127.0.0.1:/

The package upload uses sshpass with an empty admin password and disables host key checking against localhost. This is acceptable only for disposable local CHR instances.

中

references/chr-licensing.md:70 references/github-actions-ci.md:162-166

Default Empty RouterOS Administrator Credentials

Several examples use the default admin account with an empty password over SSH or HTTP. This is suitable only for disposable local CHR instances.

The examples show admin: or sshpass with an empty password. The context is local CI, but copying the pattern to persistent labs would be unsafe.

中

references/github-actions-ci.md:204-205

Destructive Git Cleanup Commands in CI Example

The retry pattern resets tracked files and removes untracked files before rebasing. This can delete local work if reused outside a disposable CI worktree.

The commands are explicitly present in the CI retry pattern. The documented context is CI, but the destructive behavior is real if copied elsewhere.

能力複核項目 (33)

這些是真實的本機能力，對此技能而言可能是預期行為，因此需要複核，但不會按已確認的惡意行為計分。

高

references/github-actions-ci.md:34

sudo privilege escalation

sudo apt-get update

The CI example runs apt with sudo, which modifies the host runner package state. This is legitimate setup work but requires elevated privileges.

高

references/github-actions-ci.md:35

sudo privilege escalation

sudo apt-get install -y qemu-system-x86 qemu-utils

The CI example runs apt with sudo, which modifies the host runner package state. This is legitimate setup work but requires elevated privileges.

高

references/github-actions-ci.md:46

sudo privilege escalation

echo 'KERNEL=="kvm", GROUP="kvm", MODE="0666", OPTIONS+="static_node=kvm"' | sudo tee /etc/udev/rule

The CI example uses sudo to alter udev/KVM handling on the host. This broadens virtualization device access and is security-sensitive.

高

references/github-actions-ci.md:47

sudo privilege escalation

sudo udevadm control --reload-rules

The CI example uses sudo to alter udev/KVM handling on the host. This broadens virtualization device access and is security-sensitive.

高

references/github-actions-ci.md:48

sudo privilege escalation

sudo udevadm trigger --name-match=kvm

The CI example uses sudo to alter udev/KVM handling on the host. This broadens virtualization device access and is security-sensitive.

高

SKILL.md:97

Process spawn

const proc = Bun.spawn([

The skill shows Bun.spawn launching qemu-system-x86_64 with VM devices and forwarded ports. This is intended functionality, but it executes a host binary and starts a VM process.

中

references/chr-licensing.md:70

Hardcoded URL

curl -u admin: http://<router-ip>/rest/system/license

The example uses cleartext HTTP Basic auth to query a RouterOS license endpoint. This can expose credentials if copied outside a trusted local lab.

中

references/github-actions-ci.md:224

Shell command substitution

kill $(cat /tmp/qemu.pid) 2>/dev/null || true

The cleanup command reads a PID from a predictable temp file and passes it to kill. A tampered PID file could terminate an unintended process on less isolated hosts.

中

references/github-actions-ci.md:103

nohup (background persistent process)

nohup qemu-system-x86_64 \

The workflow backgrounds QEMU with nohup, creating a long-lived VM process. If cleanup fails, the process can persist and keep forwarded ports open.

中

references/github-actions-ci.md:166

Hardcoded URL

curl -sf -u admin: -X POST http://127.0.0.1:9180/rest/system/reboot || true

The workflow sends an authenticated reboot request using the default admin account with no password. This is safe only when the forwarded REST service is local and ephemeral.

中

references/github-actions-ci.md:162

Hardcoded IP address

sshpass -p '' scp -P 9122 -o StrictHostKeyChecking=no "$pkg" admin@127.0.0.1:/

The package upload uses sshpass with an empty admin password and disables host key checking against localhost. This is acceptable only for disposable local CHR instances.

中

references/github-actions-ci.md:166

Hardcoded IP address

curl -sf -u admin: -X POST http://127.0.0.1:9180/rest/system/reboot || true

The workflow sends an authenticated reboot request using the default admin account with no password. This is safe only when the forwarded REST service is local and ephemeral.

中

references/github-actions-ci.md:110

Temp directory access

> /tmp/qemu.log 2>&1 &

The workflow stores QEMU logs and PID data in predictable /tmp paths. On shared hosts, predictable temp paths can enable clobbering or process-control mistakes.

中

references/github-actions-ci.md:111

Temp directory access

echo $! > /tmp/qemu.pid

The workflow stores QEMU logs and PID data in predictable /tmp paths. On shared hosts, predictable temp paths can enable clobbering or process-control mistakes.

中

references/github-actions-ci.md:223

Temp directory access

if [ -f /tmp/qemu.pid ]; then

The workflow stores QEMU logs and PID data in predictable /tmp paths. On shared hosts, predictable temp paths can enable clobbering or process-control mistakes.

中

references/github-actions-ci.md:224

Temp directory access

kill $(cat /tmp/qemu.pid) 2>/dev/null || true

The workflow stores QEMU logs and PID data in predictable /tmp paths. On shared hosts, predictable temp paths can enable clobbering or process-control mistakes.

中

references/known-issues.md:55

nohup (background persistent process)

When backgrounding QEMU (e.g., `nohup qemu-system-x86_64 ... &`), use `exec` in the shell wrapper to

The reference discusses backgrounding QEMU with nohup. The surrounding text explains safe PID handling, but the pattern can still leave orphaned VMs if copied incorrectly.

中

references/known-issues.md:59

nohup (background persistent process)

nohup sh -c "qemu-system-x86_64 ..." &

The reference discusses backgrounding QEMU with nohup. The surrounding text explains safe PID handling, but the pattern can still leave orphaned VMs if copied incorrectly.

中

references/known-issues.md:62

nohup (background persistent process)

nohup sh -c "exec qemu-system-x86_64 ..." &

The reference discusses backgrounding QEMU with nohup. The surrounding text explains safe PID handling, but the pattern can still leave orphaned VMs if copied incorrectly.

中

references/known-issues.md:72

Temp directory access

socat -,rawer UNIX-CONNECT:/tmp/serial.sock,retry=10,interval=1

The example uses predictable /tmp paths for sockets or firmware variable files. This is operationally useful but can collide across users or VM instances.

中

references/known-issues.md:81

Temp directory access

VARS_COPY="/tmp/qemu-${VM_NAME}-vars.fd"

The example uses predictable /tmp paths for sockets or firmware variable files. This is operationally useful but can collide across users or VM instances.

中

SKILL.md:104

Temp directory access

"-chardev", `socket,id=serial0,path=/tmp/chr-serial.sock,server=on,wait=off`,

The programmatic QEMU example creates monitor or serial sockets under predictable /tmp paths. Shared hosts should use private per-instance directories and permissions.

中

SKILL.md:106

Temp directory access

"-monitor", `unix:/tmp/chr-monitor.sock,server,nowait`,

The programmatic QEMU example creates monitor or serial sockets under predictable /tmp paths. Shared hosts should use private per-instance directories and permissions.

中

SKILL.md:146

Temp directory access

cp /path/to/edk2-arm-vars.fd /tmp/my-vars.fd

The UEFI example copies writable firmware variables into /tmp. Predictable firmware-variable paths can collide or be clobbered on shared systems.

中

SKILL.md:150

Temp directory access

-drive if=pflash,format=raw,unit=1,file=/tmp/my-vars.fd \

The UEFI example copies writable firmware variables into /tmp. Predictable firmware-variable paths can collide or be clobbered on shared systems.

低

references/github-actions-ci.md:71

Hardcoded URL

wget -q "https://download.mikrotik.com/routeros/${ROSVER}/chr-${ROSVER}.vdi.zip" \

The workflow downloads VM images or package bundles from external MikroTik endpoints. The domains are expected, but this remains a remote supply-chain dependency.

低

references/github-actions-ci.md:72

Hardcoded URL

|| wget -q "https://cdn.mikrotik.com/routeros/${ROSVER}/chr-${ROSVER}.vdi.zip"

The workflow downloads VM images or package bundles from external MikroTik endpoints. The domains are expected, but this remains a remote supply-chain dependency.

低

references/github-actions-ci.md:156

Hardcoded URL

wget -q "https://download.mikrotik.com/routeros/${ROSVER}/all_packages-x86-${ROSVER}.zip" \

The workflow downloads VM images or package bundles from external MikroTik endpoints. The domains are expected, but this remains a remote supply-chain dependency.

低

references/github-actions-ci.md:157

Hardcoded URL

|| wget -q "https://cdn.mikrotik.com/routeros/${ROSVER}/all_packages-x86-${ROSVER}.zip"

The workflow downloads VM images or package bundles from external MikroTik endpoints. The domains are expected, but this remains a remote supply-chain dependency.

低

SKILL.md:31

Fetch API call

const version = await fetch(

The download guidance contacts MikroTik services to resolve or fetch CHR images. The endpoints are expected, but the skill depends on external network content.

低

SKILL.md:32

Hardcoded URL

`https://upgrade.mikrotik.com/routeros/NEWESTa7.${channel}`

The download guidance contacts MikroTik services to resolve or fetch CHR images. The endpoints are expected, but the skill depends on external network content.

低

SKILL.md:36

Hardcoded URL

const url = `https://download.mikrotik.com/routeros/${version}/chr-${version}.img.zip`;

The download guidance contacts MikroTik services to resolve or fetch CHR images. The endpoints are expected, but the skill depends on external network content.

低

SKILL.md:38

Hardcoded URL

const armUrl = `https://download.mikrotik.com/routeros/${version}/chr-${version}-arm64.img.zip`;

The download guidance contacts MikroTik services to resolve or fetch CHR images. The endpoints are expected, but the skill depends on external network content.

風險因素

🌐 網路存取 (20)

⚙️ 外部命令 (92)

📁 檔案系統存取 (30)

偵測到的模式

Network reconnaissance

審計單位: codex 檢視審計紀錄 →

分享與引用此報告

分享版本化評估報告、中性徽章、嵌入卡片與引用。Skillstore 只報告證據，不判斷該 Skill 是否安全。

開啟版本化報告

複製報告連結

https://skillstore.io/skills/tikoci-routeros-qemu-chr/audits/6?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown 徽章

[![Skillstore security assessment](https://skillstore.io/badges/skills/tikoci-routeros-qemu-chr/security.svg)](https://skillstore.io/skills/tikoci-routeros-qemu-chr?utm_source=security_passport_badge)

HTML 徽章

<a href="https://skillstore.io/skills/tikoci-routeros-qemu-chr?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/tikoci-routeros-qemu-chr/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

嵌入卡片

<iframe src="https://skillstore.io/embed/skills/tikoci-routeros-qemu-chr.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

學術引用 (APA · BibTeX · CFF)

APA 引用

tikoci. (2026). routeros-qemu-chr security audit report (audit version 6) [Author version unspecified]. Skillstore. https://skillstore.io/skills/tikoci-routeros-qemu-chr/audits/6

BibTeX 引用

@techreport{tikoci-tikoci-routeros-qemu-chr-2026,
  author = {tikoci},
  title = {routeros-qemu-chr security audit report (audit version 6)},
  institution = {Skillstore},
  year = {2026},
  number = {6},
  url = {https://skillstore.io/skills/tikoci-routeros-qemu-chr/audits/6},
  note = {Author version unspecified}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "routeros-qemu-chr security audit report (audit version 6)"
version: "unspecified"
type: report
authors:
  - name: "tikoci"
date-released: "2026-07-07"
url: "https://skillstore.io/skills/tikoci-routeros-qemu-chr/audits/6"
identifiers:
  - type: other
    value: "skillstore:tikoci-routeros-qemu-chr:audit:6"
    description: "Skillstore immutable audit report identifier"

Skillstore 評分

評分依據證據置信度: 中

架構

可維護性

內容

社群

規範符合度

你可以打造什麼

建立可拋棄式 RouterOS 實驗室

建立本機 CHR VM，用於 API 測試、封包除錯或訓練，無需硬體。

新增 RouterOS 整合測試

在 GitHub Actions 中執行 CHR，以驗證 REST、套件與產生的結構描述。

診斷 CHR 啟動問題

當 VM 停滯或逾時時，比較韌體、CPU、加速與 VirtIO 選擇。

試試這些提示

規劃 CHR 實驗室

在我的主機上規劃 RouterOS CHR QEMU 實驗室。如有需要，請詢問我的主機 OS 與 CPU 架構，然後建議映像檔、啟動方法、加速方式、RAM、磁碟與連接埠轉送。

除錯啟動失敗

診斷此 CHR 啟動失敗：[symptoms]。比較韌體、機器類型、磁碟介面、CPU 型號與 VirtIO 傳輸。提供依優先順序排列的修復清單。

建立 CI 工作流程

為選定的 RouterOS CHR 版本設計 GitHub Actions 工作流程。包含映像檔下載、磁碟轉換、QEMU 啟動、REST 就緒檢查、選用套件上傳、重新啟動處理與安全清理。

設計多架構矩陣

為 x86_64 與 aarch64 主機建立多架構 CHR 測試策略。包含加速後援規則、不支援的組合、啟動時間預期與略過邏輯。

最佳實務

除非需要遠端存取，否則將轉送服務繫結到 localhost。
為每個執行個體使用獨立的暫存路徑，用於 QEMU socket、日誌與韌體變數。
在測試輸送量或套件下載前，確認 CHR 授權限制。

避免

不要對 RouterOS 磁碟使用 aarch64 if=virtio 簡寫。
不要假設 KVM 或 HVF 可跨主機與客體架構運作。
不要在可拋棄式本機 CHR 執行個體之外重複使用空白 admin 密碼。

常見問題

此技能會安裝 RouterOS 嗎？

不會。它會說明如何取得 CHR 映像檔並使用 QEMU 執行。

它可以在 macOS 上執行嗎？

可以。它涵蓋 HVF、Homebrew 韌體路徑與 CPU 型號限制。

為什麼 aarch64 需要 UEFI？

arm64 CHR 映像檔會透過 EDK2 pflash 韌體啟動，而不是 SeaBIOS。

免費 CHR 授權足以用於 CI 嗎？

對 API 測試而言足夠。輸送量限制為 1 Mbps。

它會在啟動後設定 RouterOS 嗎？

不會。請在 CHR 可連線後，使用 RouterOS 設定技能或 CLI 工作流程。

CI 範例在共用 runner 上安全嗎？

需要審查。部分步驟會使用 sudo、KVM 權限、本機連接埠轉送與可預測的暫存路徑。

開發者詳細資訊

作者

tikoci

授權

MIT

Skillstore 修訂

版本提示

作者未聲明版本。

儲存庫

https://github.com/tikoci/routeros-skills/tree/main/routeros-qemu-chr

引用

36e07d5e13068e5be64447e8f20b427cf2cbd21a

維護新鮮度

2026/7/18

使用量

4 次下載 · 112 次瀏覽

檔案結構

📁 references/

📄 chr-licensing.md

📄 github-actions-ci.md

📄 known-issues.md

📄 virtio-drivers.md

📄 SKILL.md