Skip to content
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

docs: s/ArgoCD/Argo CD #10352

Merged
merged 1 commit into from
Aug 19, 2022
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
8 changes: 4 additions & 4 deletions docs/security_considerations.md
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@ related features in [Security](./operator-manual/security.md) section.
## Overview of past and current issues

The following table gives a general overview about past and present issues known
to the ArgoCD project. See in the [Known Issues](#known-issues-and-workarounds)
to the Argo CD project. See in the [Known Issues](#known-issues-and-workarounds)
section if there is a work-around available if you cannot update or if there is
no fix yet.

Expand Down Expand Up @@ -45,7 +45,7 @@ Most of the issues are related to the built-in user management implementation.
**Details:**

PyYAML library susceptible to arbitrary code execution when it processes untrusted YAML files.
We do not believe ArgoCD is affected by this vulnerability, because the impact of CVE-2020-1747 and CVE-2020-14343 is limited to usage of awscli.
We do not believe Argo CD is affected by this vulnerability, because the impact of CVE-2020-1747 and CVE-2020-14343 is limited to usage of awscli.
The `awscli` only used for AWS IAM authentication, and the endpoint is the AWS API.

### CVE-2020-5260 - Possible Git credential leak
Expand All @@ -58,13 +58,13 @@ The `awscli` only used for AWS IAM authentication, and the endpoint is the AWS A

**Details:**

ArgoCD relies on Git for many of its operations. The Git project released a
Argo CD relies on Git for many of its operations. The Git project released a
[security advisory](https://github.com/git/git/security/advisories/GHSA-qm7j-c969-7j4q)
on 2020-04-14, describing a serious vulnerability in Git which can lead to credential
leakage through credential helpers by feeding malicious URLs to the `git clone`
operation.

We do not believe ArgoCD is affected by this vulnerability, because ArgoCD does neither
We do not believe Argo CD is affected by this vulnerability, because ArgoCD does neither
make use of Git credential helpers nor does it use `git clone` for repository operations.
However, we do not know whether our users might have configured Git credential helpers on
their own and chose to release new images which contain the bug fix for Git.
Expand Down
2 changes: 1 addition & 1 deletion docs/user-guide/commands/argocd_cli.md
Original file line number Diff line number Diff line change
@@ -1,3 +1,3 @@
# ArgoCD Command Reference

ArgoCD command reference can be found [here](./argocd.md).
Argo CD command reference can be found [here](./argocd.md).
2 changes: 1 addition & 1 deletion test/fixture/certs/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -15,4 +15,4 @@ You can use the CA certificate to sign more certificates, if you need additional
certificates for testing.

Needless to say, but should be mentioned anyway: Do not use these certs for
anything else except ArgoCD tests.
anything else except Argo CD tests.