Very odd results (Chinese crypto?)

Discussion
1

I asked Cursor to inspect some files and ensure they meet my standards in my rules files. I’m unsure how to react to what I got back:

1. 概述
本文档描述了如何将现有的基于 golang.org/x/crypto/ssh 的 SSH 客户端代码迁移到 github.com/gliderlabs/ssh 包。gliderlabs/ssh 是一个更现代的 SSH 实现，提供了更好的性能和更简洁的 API。
2. 主要差异
2.1 包结构
golang.org/x/crypto/ssh: 标准库的 SSH 实现，功能完整但 API 较复杂
github.com/gliderlabs/ssh: 第三方库，API 更简洁，性能更好
2.2 关键 API 差异
2.2.1 客户端配置
Apply to data_source_...
)
2.2.2 会话创建
Apply to data_source_...
)
2.2.3 命令执行
Apply to data_source_...
}
3. 迁移步骤
3.1 更新依赖
移除 golang.org/x/crypto/ssh 依赖
添加 github.com/gliderlabs/ssh 依赖
Apply to data_source_...
Run
ssh
3.2 代码修改
3.2.1 导入语句修改
Apply to data_source_...
"
3.2.2 客户端配置修改
Apply to data_source_...
)
3.2.3 会话处理修改
Apply to data_source_...
)
4. 注意事项
gliderlabs/ssh 的 API 与标准库非常相似，迁移相对简单
需要注意 HostKeyCallback 的处理，建议在生产环境中使用安全的回调函数
某些高级功能可能需要额外配置或使用不同的 API
5. 测试验证
迁移完成后，需要进行以下测试：
基本连接测试
命令执行测试
文件传输测试
错误处理测试
并发连接测试
6. 回滚计划
如果迁移过程中遇到问题，可以按照以下步骤回滚：
恢复原来的依赖
恢复修改的代码
验证原有功能是否正常
7. 参考文档
gliderlabs/ssh GitHub 仓库
golang.org/x/crypto/ssh 文档
1 Like
2

From a quick google translate looks like it’s providing instructions for migrating a ssh client implementation…

First question that comes to mind is, do you have anything related to this in any of the files you inspected? If you perform a ‘search everywhere’ in these files and look for “gliderlabs/ssh”, do you get any result back?

3

Nope. Absolutely nothing in my project. My project is a pretty vanilla Go API server using Gin.

4

Here is the prompt I used:

Check all test files in internal/service (and any subdirectories) and ensure they comply with the standards set forth in .cursor/rules/go-api.mdc and .cursor/rules/testing.mdc

If a test file is missing, create it.

If a test file uses its own mocked definition that already exists in internal/testutils/mocks, remove that definition and, instead, use the common implementation(s) in the mocks package located in internal/testutils/mocks. If there is no common mock in internal/testutils/mocks, do not create a new one.