Skip to content

Lemon串口监控 v0.1.1

Latest
Latest

Choose a tag to compare

View all tags
@qingningmneg qingningmneg released this 20 Jul 02:15
v0.1.1
139de53

Lemon串口监控 0.1.1 发布说明 / Lemon Serial Monitor 0.1.1 Release Notes

简体中文 | English

简体中文

0.1.1 是相对 0.1.0 的维护与发布完整性更新，重点是许可证分发、双语公开文档和版本一致性；它不是新增捕获能力、界面功能或 AI 功能的版本。

本版变化

  • 根目录 MIT 许可证 是规范许可证文本。个人和企业都可以免费使用，也允许商业使用和盈利、修改、合并、发布、再分发、再许可和销售副本；复制或分发本软件或其实质部分时，必须保留 Copyright (c) 2026 qingningmneg 版权声明和 MIT 许可声明。
  • 安装目录现在包含 docs\LICENSE.txt。安装包同时保留 Inno Setup 简体中文翻译的第三方来源与许可证说明；第三方译文只帮助理解，不取代对应的规范许可证原文。
  • 公开 Release 增加独立的 LICENSE.txt，成为第六个公开文件；安装前即可阅读完整 MIT 条款。
  • README、安装、构建、安全、发现与下载说明已同步为等价的中英文内容，并继续使用稳定的安装包下载名称。
  • 产品版本、Windows 文件版本、安装器、安装、卸载、构建和发布校验器已对齐到产品版本 0.1.1；Windows 文件版本保持 0.1.1.0。

发布文件

每个 0.1.1 公开发布目录只包含以下六个普通文件：

  1. LemonSerialMonitor-Setup-x64.exe
  2. LemonSerialMonitor-User-Manual-zh-CN.pdf
  3. RELEASE-NOTES.md
  4. BUILD-INFO.json
  5. LICENSE.txt
  6. SHA256SUMS.txt

SHA256SUMS.txt 只列出并校验除清单自身以外的另外五个文件。下载后应先核对同一版本的清单，再运行安装程序。

安装与安全

0.1.1 仍使用本地测试证书，不是微软 WHQL、Attestation 或生产签名。发布文件没有微软生产信任链，也没有 RFC 3161 公共时间戳；本地测试签名不能替代正式发布签名。

安装程序会核对载荷、证书和哈希，在明确征得同意后导入公钥证书，并在需要时启用 TESTSIGNING。系统策略变化和 Ports 类过滤器加载可能要求重启。软件不会关闭安全启动；安全启动开启或组织策略禁止 TESTSIGNING 时，安装会停止。

0.1.1 不在已有新式安装上执行原地覆盖，也不要直接覆盖正在运行的服务、已加载的驱动或受保护安装记录。

功能边界

  • 监控是被动、只读的：桌面程序和 AI 客户端不打开被监控 COM 端口，内核过滤驱动只复制已经发生的读写和受支持控制事件。
  • 软件不提供主动发送、注入、修改、阻断或重放串口数据的能力。
  • CLI 和 MCP 仅通过受保护的本机接口工作，按页读取持久化捕获事件；不监听 HTTP/TCP，也不提供任意文件访问。

验证证据边界

0.1.0 是现有 Windows 11 实机和 Windows Server 自动化/契约验证的历史基线。0.1.1 没有新增物理串口设备验收、Windows Server 内核驱动端到端验收或完整安装验收，也不构成通用兼容性、真实硬件认证或生产签名声明。

Windows Server 2022/2025 的历史证据仅包括 GitHub 托管桌面 runner 的平台识别、托管测试和安装契约检查，没有装载内核驱动；Server Core 只有组件布局契约测试，Server 2019 自托管任务未执行。重要环境仍应先在同版本测试机完成驱动安装、重启、捕获、AI 和卸载全流程验证。

更新与卸载

从旧版本更新时，先停止监控并导出或备份需要保留的数据，再使用旧版本卸载程序执行完整卸载；按提示重启并等待清理完成后，安装 0.1.1。不要原地覆盖旧版本。

完整卸载会永久删除本软件的会话、导出、设置、日志、缓存和 AI 状态，以及软件拥有的服务、驱动、过滤器、证书和程序文件。需要保留的数据必须先复制到软件管理目录之外。

English

Version 0.1.1 is a maintenance and release-integrity update relative to 0.1.0. It focuses on license distribution, equivalent bilingual public documentation, and version consistency; it is not a release of new capture, UI, or AI features.

What Changed

  • The root MIT License is the canonical license text. Individuals and companies may use the software free of charge, including for commercial and for-profit purposes, and may modify, merge, publish, redistribute, sublicense, and sell copies. Any copy or substantial portion of the software must retain the Copyright (c) 2026 qingningmneg copyright notice and the MIT license notice.
  • The installed files now include docs\LICENSE.txt. Setup also retains the third-party source and license notice for the Inno Setup Simplified Chinese translation; a third-party translation helps with understanding but does not replace the corresponding canonical license text.
  • The public Release adds a separate LICENSE.txt as its sixth public file, so the complete MIT terms can be read before installation.
  • The README, installation, build, security, discovery, and download copy is now equivalent in Chinese and English, while retaining the stable installer download name.
  • The product version, Windows file version, installer, installation, uninstall, build, and release verifier are aligned to product version 0.1.1; the Windows file version remains 0.1.1.0.

Release Assets

Each 0.1.1 public release directory contains exactly these six ordinary files:

  1. LemonSerialMonitor-Setup-x64.exe
  2. LemonSerialMonitor-User-Manual-zh-CN.pdf
  3. RELEASE-NOTES.md
  4. BUILD-INFO.json
  5. LICENSE.txt
  6. SHA256SUMS.txt

SHA256SUMS.txt lists and verifies only the other five files, excluding the manifest itself. Verify the same-version manifest before running Setup.

Installation and Security

Version 0.1.1 still uses a local test certificate, not Microsoft WHQL, Attestation, or production signing. The release files have no Microsoft production trust chain and no RFC 3161 public timestamp; local test signing is not a substitute for production release signing.

Setup verifies the payload, certificate, and hashes, imports the public certificate after explicit consent, and enables TESTSIGNING when required. Changes to system policy and loading the Ports class filter may require a restart. The software does not disable Secure Boot; installation stops when Secure Boot is enabled or organizational policy prohibits TESTSIGNING.

Version 0.1.1 does not perform an in-place overwrite of an existing modern installation. Do not directly overwrite a running service, loaded driver, or protected installation record.

Functional Boundaries

  • Monitoring is passive and read-only: the desktop application and AI client do not open the monitored COM port, and the kernel filter driver only copies read, write, and supported control events that have already occurred.
  • The software does not provide active sending, injection, modification, blocking, or replay of serial data.
  • The CLI and MCP work only through protected local interfaces and read persisted capture events through pagination. They do not listen on HTTP/TCP or provide arbitrary file access.

Evidence Boundary

Version 0.1.0 is the historical baseline for the existing physical Windows 11 and automated/contract Windows Server validation. Version 0.1.1 adds no new physical serial-device acceptance, Windows Server kernel-driver end-to-end acceptance, or full installation acceptance, and makes no universal-compatibility, hardware-certification, or production-signing claim.

The historical Windows Server 2022/2025 evidence covers only platform detection, managed tests, and installation-contract checks on GitHub-hosted desktop runners; it did not load the kernel driver. Server Core received component-layout contract tests only, and the Server 2019 self-hosted job was not run. Important environments must still validate driver installation, restart, capture, AI, and uninstall end to end on a test machine running the same version.

Upgrade and Uninstall

To update from an older version, stop monitoring and export or back up the data you need to keep, then perform a full uninstall with the old version's uninstaller. Restart when prompted and wait for cleanup to finish before installing 0.1.1. Do not overwrite the old version in place.

Full uninstall permanently deletes this software's sessions, exports, settings, logs, caches, and AI state, along with the services, driver, filter, certificates, and program files owned by the software. First copy any data that must be retained outside the software-managed directories.

Assets 8
Loading