Skip to content

docs: 微信二维码+搜索关键词 / security: 移除硬编码WiFi凭据 - #1

Merged
DrDavidDa merged 2 commits into
mainfrom
agents/wechat-qr-upload-m5stack-integration
Sep 2, 2026
Merged

DrDavidDa merged 2 commits into
mainfrom
agents/wechat-qr-upload-m5stack-integration

Conversation

@DrDavidDa

@DrDavidDa DrDavidDa commented Sep 2, 2026 •

Copy link
Copy Markdown
Owner

变更

  • 💬 交流板块上传微信二维码(docs/images/wechat-qr.jpg)
  • 🔎 README 底部新增关键词块;仓库 topics/description 已加 m5stack/papercolor 等 20 个标签
  • 🔒 write_hotspot.py 硬编码 WiFi 凭据改参数化;教程真实 SSID 改通用示例

安全审查结论(M5Burner 发布前置检查)

  • 固件镜像(app分区/NVS/TTS模型)无敏感数据:代码仅占位符,NVS 只存 Anki 状态,WiFi/token 均在 SD 卡 config.ini
  • zhipu_token.txt / sf_api_key.txt / wifi_extra.txt 确认从未入库
  • ⚠️ 历史提交仍含旧凭据 → 已建议改路由器/热点密码根治

🤖 Generated with Claude Code


Note

Low Risk
Documentation and a dev helper script only; no firmware or runtime auth logic changes. Remaining risk is historical commits that may still contain old WiFi secrets (not fixed by this diff).

Overview
Community & discoverability: The README 交流 section now shows a WeChat QR image (docs/images/wechat-qr.jpg) with scan-to-add copy instead of text-only contact. A collapsible 关键词 / Keywords block was added near the bottom for search/discovery (hardware, firmware, features).

Security & docs hygiene: write_hotspot.py no longer ships default hotspot/home WiFi passwords in source—credentials must be passed on the command line, with optional second-network args; usage is printed and the script exits if args are missing. docs/coding-plan-guide.md config.ini examples were switched from real SSIDs to generic placeholders (我的手机热点, 家里WiFi).

Reviewed by Cursor Bugbot for commit 48a89ef. Bugbot is set up for automated code reviews on this repo. Configure here.

DrDavidDa and others added 2 commits September 2, 2026 14:08
- write_hotspot.py: 热点/家里WiFi全部走命令行参数,不再默认硬编码
- coding-plan-guide.md: 真实SSID改为通用示例
- 历史提交中仍含旧凭据,需同步修改路由器/热点密码根治

Co-Authored-By: Claude <noreply@anthropic.com>
@cursor

cursor Bot commented Sep 2, 2026

Copy link
Copy Markdown

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_997bde74-56a4-4166-880e-b3e8fb8d0773)

@DrDavidDa
DrDavidDa merged commit fde601b into main Sep 2, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant