GITBOOK-8658: vc-Risk factor: Public facing - Add reference to k8 con…

…nector page
snyk · Jan 8, 2025 · 8e32ae8 · 8e32ae8
1 parent 70e9230
commit 8e32ae8
Show file tree

Hide file tree

Showing 2 changed files with 6 additions and 6 deletions.
diff --git a/...or-fixing/assets-and-risk-factors-for-snyk-apprisk/risk-factor-public-facing.md b/...or-fixing/assets-and-risk-factors-for-snyk-apprisk/risk-factor-public-facing.md
@@ -22,7 +22,7 @@ Kubernetes Connector checks the images for ingress configuration. If not detecte
 
 ## Kubernetes Connector integration
 
-The Public facing risk factor can be applied to your Kubernetes Connector integrations.&#x20;
+The Public facing risk factor can be applied to your [Kubernetes Connector](../set-up-insights-for-snyk-apprisk/set-up-insights-kubernetes-connector.md) integrations.&#x20;
 
 The Public facing risk factor has significant implications for Kubernetes Connector integration. It affects how vulnerabilities and potential attack vectors are prioritized and managed within the Kubernetes environment. The continuous monitoring of Kubernetes events by the Kubernetes Connector ensures that any changes or potential risks are instantly evaluated and relayed to the Snyk platform. This real-time data allows for the dynamic adjustment of security policies and proactive risk mitigation, ensuring the integrity and security of the cloud-native infrastructure.
 

diff --git a/docs/snyk-cli/install-or-update-the-snyk-cli/verifying-cli-standalone-binaries.md b/docs/snyk-cli/install-or-update-the-snyk-cli/verifying-cli-standalone-binaries.md
@@ -10,10 +10,10 @@ To check that a downloaded file matches the checksum, use a `sha256sum` command,
 grep snyk-macos sha256sums.txt.asc | sha256sum -c -
 ```
 
-If you want to verify Snyk CLI standalone binaries against [Snyk CLI GPG key](https://github.com/snyk/cli/blob/master/help/\_about-this-project/snyk-code-signing-public.pgp), first import the CPG key:
+If you want to verify Snyk CLI standalone binaries against the [Snyk CLI GPG key](https://github.com/snyk/cli/blob/master/help/_about-this-project/snyk-code-signing-public.pgp), first import the GPG key:
 
 ```
-# A22665FB96CAB0E0973604C83676C4B8289C296E is the key belonging to [email protected]
+# 467717A30B2B4658415975629691DA64D0025194 is the key belonging to [email protected]
 # Copy of this public key is also in this repository /help/_about-this-project/snyk-code-signing-public.pgp
 gpg --keyserver hkps://keys.openpgp.org --recv-keys A22665FB96CAB0E0973604C83676C4B8289C296E
 ```
@@ -27,10 +27,10 @@ gpg --verify sha256sums.txt.asc
 The command output should look like the following:
 
 ```
-gpg: Signature made So  8 Jan 14:11:44 2023 CET
-gpg:                using EDDSA key A22665FB96CAB0E0973604C83676C4B8289C296E
+gpg: Signature made So  8 Jan 14:11:44 2025 CET
+gpg:                using EDDSA key 467717A30B2B4658415975629691DA64D0025194
 gpg: Good signature from "Snyk Limited <[email protected]>" [unknown]
 gpg: WARNING: This key is not certified with a trusted signature!
 gpg:          There is no indication that the signature belongs to the owner.
-Primary key fingerprint: A226 65FB 96CA B0E0 9736  04C8 3676 C4B8 289C 296E
+Primary key fingerprint: 4677 17A3 0B2B 4658 4159  7562 9691 DA64 D002 5194
 ```