docs: add security clarification for enterprise users (#41)#48
Merged
Conversation
- Clarify that no Base64-encoded PowerShell is used - Explain why security software may still alert - Provide solutions for enterprise users - Emphasize all scripts are plaintext and auditable Related #41
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
📝 Documentation Update
Fixes #41
Problem
企业用户担心 start.bat 中的 Base64 编码 PowerShell 会被 EDR/杀毒软件拦截。
Solution
经检查,当前版本已不使用 Base64 编码的 PowerShell 命令。所有下载逻辑使用:
curl.exeExpand-ArchiveChanges
在 README_CN.md 的「安全提示」部分添加:
Security Audit
Impact
Priority
🟠 P1 High - Security concerns block enterprise adoption
This PR was created automatically by AI assistant