You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/zh-cn/docs/reference/issues-security/security.md
+28-12Lines changed: 28 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -31,37 +31,45 @@ This page describes Kubernetes security and disclosure information.
31
31
## 安全公告 {#security-announcements}
32
32
33
33
<!--
34
-
Join the [kubernetes-security-announce](https://groups.google.com/forum/#!forum/kubernetes-security-announce) group for emails about security and major API announcements.
34
+
Join the [kubernetes-security-announce](https://groups.google.com/forum/#!forum/kubernetes-security-announce)
35
+
group for emails about security and major API announcements.
35
36
-->
36
-
加入 [kubernetes-security-announce](https://groups.google.com/forum/#!forum/kubernetes-security-announce) 组，以获取关于安全性和主要 API 公告的电子邮件。
We're extremely grateful for security researchers and users that report vulnerabilities to the Kubernetes Open Source Community. All reports are thoroughly investigated by a set of community volunteers.
46
+
We're extremely grateful for security researchers and users that report vulnerabilities to
47
+
the Kubernetes Open Source Community. All reports are thoroughly investigated by a set of community volunteers.
45
48
-->
46
49
我们非常感谢向 Kubernetes 开源社区报告漏洞的安全研究人员和用户。
47
50
所有的报告都由社区志愿者进行彻底调查。
48
51
49
52
<!--
50
-
To make a report, submit your vulnerability to the [Kubernetes bug bounty program](https://hackerone.com/kubernetes). This allows triage and handling of the vulnerability with standardized response times.
53
+
To make a report, submit your vulnerability to the [Kubernetes bug bounty program](https://hackerone.com/kubernetes).
54
+
This allows triage and handling of the vulnerability with standardized response times.
You can also email the private [[email protected]](mailto:[email protected]) list with the security details and the details expected for [all Kubernetes bug reports](https://github.com/kubernetes/kubernetes/blob/master/.github/ISSUE_TEMPLATE/bug-report.yaml).
You may encrypt your email to this list using the GPG keys of the [Security Response Committee members](https://git.k8s.io/security/README.md#product-security-committee-psc). Encryption using GPG is NOT required to make a disclosure.
70
+
You may encrypt your email to this list using the GPG keys of the
Each report is acknowledged and analyzed by Security Response Committee members within 3 working days. This will set off the [Security Release Process](https://git.k8s.io/security/security-release-process.md#disclosures).
113
+
Each report is acknowledged and analyzed by Security Response Committee members within 3 working days.
114
+
This will set off the [Security Release Process](https://git.k8s.io/security/security-release-process.md#disclosures).
Any vulnerability information shared with Security Response Committee stays within Kubernetes project and will not be disseminated to other projects unless it is necessary to get the issue fixed.
120
+
Any vulnerability information shared with Security Response Committee stays within Kubernetes project
121
+
and will not be disseminated to other projects unless it is necessary to get the issue fixed.
@@ -122,18 +133,23 @@ As the security issue moves from triage, to identified fix, to release planning
122
133
## 公开披露时间 {#public-disclosure-timing}
123
134
124
135
<!--
125
-
A public disclosure date is negotiated by the Kubernetes Security Response Committee and the bug submitter. We prefer to fully disclose the bug as soon as possible once a user mitigation is available.
136
+
A public disclosure date is negotiated by the Kubernetes Security Response Committee and the bug submitter.
137
+
We prefer to fully disclose the bug as soon as possible once a user mitigation is available.
126
138
-->
127
139
公开披露日期由 Kubernetes 安全响应委员会和 bug 提交者协商。
128
140
我们倾向于在能够为用户提供缓解措施之后尽快完全披露该 bug。
129
141
130
142
<!--
131
-
It is reasonable to delay disclosure when the bug or the fix is not yet fully understood, the solution is not well-tested, or for vendor coordination.
143
+
It is reasonable to delay disclosure when the bug or the fix is not yet fully understood,
144
+
the solution is not well-tested, or for vendor coordination.
The timeframe for disclosure is from immediate (especially if it's already publicly known) to a few weeks. For a vulnerability with a straightforward mitigation, we expect report date to disclosure date to be on the order of 7 days. The Kubernetes Security Response Committee holds the final say when setting a disclosure date.
149
+
The timeframe for disclosure is from immediate (especially if it's already publicly known)
150
+
to a few weeks. For a vulnerability with a straightforward mitigation, we expect report date
151
+
to disclosure date to be on the order of 7 days. The Kubernetes Security Response Committee
152
+
holds the final say when setting a disclosure date.
Examples using `kubectl` and JSONPath expressions:
121
128
-->
122
-
使用 `kubectl` 和 JSONPath 表达式的示例:
129
+
使用 `kubectl` 和 JSONPath 表达式的示例：
123
130
124
131
```shell
125
132
kubectl get pods -o json
@@ -128,22 +135,21 @@ kubectl get pods -o=jsonpath='{.items[0]}'
128
135
kubectl get pods -o=jsonpath='{.items[0].metadata.name}'
129
136
kubectl get pods -o=jsonpath="{.items[*]['metadata.name', 'status.capacity']}"
130
137
kubectl get pods -o=jsonpath='{range .items[*]}{.metadata.name}{"\t"}{.status.startTime}{"\n"}{end}'
138
+
kubectl get pods -o=jsonpath='{.items[0].metadata.labels.kubernetes\.io/hostname}'
131
139
```
132
140
133
-
<!--
134
141
{{< note >}}
135
-
On Windows, you must _double_ quote any JSONPath template that contains spaces (not single quote as shown above for bash). This in turn means that you must use a single quote or escaped double quote around any literals in the template. For example:
142
+
<!--
143
+
On Windows, you must _double_ quote any JSONPath template that contains spaces (not single quote as shown above for bash).
144
+
This in turn means that you must use a single quote or escaped double quote around any literals in the template. For example:
136
145
137
146
```cmd
138
147
kubectl get pods -o=jsonpath="{range .items[*]}{.metadata.name}{'\t'}{.status.startTime}{'\n'}{end}"
139
148
kubectl get pods -o=jsonpath="{range .items[*]}{.metadata.name}{\"\t\"}{.status.startTime}{\"\n\"}{end}"
140
149
```
141
-
{{< /note >}}
142
150
-->
143
-
{{< note >}}
144
151
在 Windows 上，对于任何包含空格的 JSONPath 模板，你必须使用双引号（不是上面 bash 所示的单引号）。
145
-
反过来，这意味着你必须在模板中的所有文字周围使用单引号或转义的双引号。
146
-
例如:
152
+
反过来，这意味着你必须在模板中的所有文字周围使用单引号或转义的双引号。例如：
147
153
148
154
```cmd
149
155
C:\> kubectl get pods -o=jsonpath="{range .items[*]}{.metadata.name}{'\t'}{.status.startTime}{'\n'}{end}"
0 commit comments