Skip to content

Commit 5866a6f

Browse files
Tim Bannistersaschagrunert
andcommitted
Revise download page SBoM advice
Quote a command to avoid any risk of side-effects from a malicious BoM Avoid a use of grep where awk can achieve the same outcome Co-authored-by: Sascha Grunert <[email protected]>
1 parent b7834e3 commit 5866a6f

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

content/en/releases/download.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -73,13 +73,13 @@ in SBoM (Software Bill of Materials) format.
7373
You can fetch that list using:
7474

7575
```shell
76-
curl -Ls https://sbom.k8s.io/$(curl -Ls https://dl.k8s.io/release/latest.txt)/release | grep 'PackageName: k8s.gcr.io/' | awk '{print $2}'
76+
curl -Ls "https://sbom.k8s.io/$(curl -Ls https://dl.k8s.io/release/latest.txt)/release" | awk '/PackageName: k8s.gcr.io\// {print $2}'
7777
```
7878
For Kubernetes v{{< skew currentVersion >}}, the only kind of code artifact that
7979
you can verify integrity for is a container image, using the experimental
8080
signing support.
8181

82-
To manually verify signed container images of Kubernetes core components, please refer to
82+
To manually verify signed container images of Kubernetes core components, refer to
8383
[Verify Signed Container Images](/docs/tasks/administer-cluster/verify-signed-images).
8484

8585

0 commit comments

Comments
 (0)