-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
finished translation #128
finished translation #128
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
注意格式问题
Many kernel mailing lists reject HTML formatted messages, so use the plain text mode when sending the report. | ||
请将发现的错误报告给 Linux 内核维护人员。 | ||
要找出负责特定内核子系统的维护者列表,请使用 [get_maintainer.pl](https://github.com/torvalds/linux/blob/master/scripts/get_maintainer.pl) 脚本:`./scripts/get_maintainer.pl -f guilty_file.c`。 请将 `[email protected]` 添加到抄送列表。 | ||
确保在报告中明确指出发生错误的确切内核分支和版本号。 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
这里明确和确切是不是重复了
Note that people are more likely to care about kernel crashes (e.g. use-after-frees or panics) than of INFO: messages and such, unless it is clearly visible from the report what exactly is wrong. | ||
If there are stalls or hangs, only report them if they are frequent enough or have a reliable reproducer. | ||
在提交报告前需要字斟句酌。 | ||
如今,Linux 维护者被日益增加的bug报告淹没了,因此仅仅增加报告的提交量无助于解决bug本身。 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
英文和中文用空格隔开
The more actionable your report is, the higher the chance that it will be addressed. | ||
Note that people are more likely to care about kernel crashes (e.g. use-after-frees or panics) than of INFO: messages and such, unless it is clearly visible from the report what exactly is wrong. | ||
If there are stalls or hangs, only report them if they are frequent enough or have a reliable reproducer. | ||
在提交报告前需要字斟句酌。 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
原文没有换行,尽量和原文格式保持一致。
在提交报告前需要字斟句酌。 | ||
如今,Linux 维护者被日益增加的bug报告淹没了,因此仅仅增加报告的提交量无助于解决bug本身。 | ||
您的报告越详细越具有可操作性,解决它的可能性就越大。 | ||
请注意,人们更关心内核崩溃 (例如 use-after-frees 或者 panics) 而非仅仅是 INFO:错误信息或者类似的信息,除非从报告中清楚地指出了到底在哪里出现了什么具体问题。 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
英文括号也和中文用空格隔开
Check that the reproducer works if you run it manually. | ||
Syzkaller tries to simplify the reproducer, but the result might not be ideal. | ||
You can try to simplify or annotate the reproducer manually, that greatly helps kernel developers to figure out why the bug occurs. | ||
总体而言,没有复制器(reproducers)的错误不太可能被分类和修复。 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
同上
If you want to deal with the disclosure yourself, read below. | ||
1. 私下将错误报告给 `[email protected]`. 在这种情况下,它应该在上游内核中修复,但不能保证修复程序会传播到稳定版或发行版内核。此清单上的最长禁止公开披露期限为7天。 | ||
2. 私下向例如 Red Hat (`[email protected]`) 或者 SUSE (`[email protected]`) 等供应商报告错误. 他们应该修复错误,分配 CVE,并通知其他供应商。 | ||
3. 这些名单上的最长禁运期限 embargo 为5周。 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
和原文格式保持一致
2. 通过 [Web 表单](https://cveform.mitre.org/)向 MITRE 请求 CVE。. 描述 bug 详细信息,并在请求中添加指向修复的链接 (`patchwork.kernel.org`, `git.kernel.org` 或者 `github.com`). | ||
3. 分配 CVE 后,将 bug 详细信息、CVE 编号和修复链接发送到 `[email protected]`. | ||
|
||
### 报告主要安全漏洞 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
这段格式也有问题,注意和原文保持一致
把两个commit合并一下,保持commit历史干净 |
完成翻译