eric/terminalX
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
5d1abdc7aca6dddf1fe97e61307e6b61f7b8917c
terminalX/vendor/mbedtls/BUGS.md
kid aa92d0e676 初始提交：terminalX 可运行态（M0/M1/M1.5 已真机验证） 
- M0: libghostty SSH 终端（渲染/输入/连接）+ 白屏修复(OutputGate) + 会话状态机/自动重连
- M1: tsnet 用户态组网 + SSH-over-tsnet(fd 桥)，shell 级真机验证；R5(Go+gvisor+C+++Swift 同进程) retire
- M1.5: tmux -CC 原生 tab（MVP）
- 结构: packages/(TXCore·TXTransport), apps/TerminalX, vendor/(libghostty-spm/libssh2/mbedtls/tsnet-bridge), artifacts/
- 文档: CLAUDE.md + docs/HANDOFF.md（新会话入口）
- 环境: 认证代理→依赖 vendor 本地化；Go 在 ~/.local/go；仅模拟器/未签名
- 待续: M2 mosh, tmux 多 pane, M4 安全(host key/SE)

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-07-24 10:20:46 +08:00

926 B
Raw Blame History

Known issues

Known issues in Mbed TLS are tracked on GitHub.

Reporting a bug

If you think you've found a bug in Mbed TLS, please follow these steps:

  1. Make sure you're using the latest version of a maintained branch: main, development, or a long-time support branch.
  2. Check GitHub to see if your issue has already been reported. If not, …
  3. If the issue is a security risk (for example: buffer overflow, data leak), please report it confidentially as described in SECURITY.md. If not, …
  4. Please create an issue on on GitHub.

Please do not use GitHub for support questions. If you want to know how to do something with Mbed TLS, please see SUPPORT.md for available documentation and support channels.