Skip to content

Commit b499a38

Browse files
authored
Merge pull request #1034 from chocolatey/fix/security-mdx-link-syntax
(fix) Correct link syntax in security.mdx
2 parents 76f6598 + b37d010 commit b499a38

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

src/content/docs/en-us/information/security.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -236,7 +236,7 @@ For using Chocolatey, if you are using the community repository, you will need t
236236

237237
For specific IP addresses to whitelist, please see the following: [https://www.cloudflare.com/ips/](https://www.cloudflare.com/ips/)
238238

239-
If you are using the community package repository, you would also need to whitelist the official distribution location for **EVERY** package that you intend to manage (unless you had a licensed edition **and** the downloads have been cached on the Chocolatey customer CDN). This is due to distribution rights and the community repo being publicly available (discussed above at <Xref title="community.chocolatey.org Packages](#chocolateyorg-packages)), so those community packages are not able to embed binaries directly into the package and must download those resources at runtime. Licensed editions of Chocolatey take advantage of a [CDN cache" value="private-cdn" /> of those downloaded resources, which is used instead of reaching out to those remote locations to ensure availability.
239+
If you are using the community package repository, you would also need to whitelist the official distribution location for **EVERY** package that you intend to manage (unless you had a licensed edition **and** the downloads have been cached on the Chocolatey customer CDN). This is due to distribution rights and the community repo being publicly available (discussed above at [community.chocolatey.org Packages](#communitychocolateyorg-packages)), so those community packages are not able to embed binaries directly into the package and must download those resources at runtime. Licensed editions of Chocolatey take advantage of a <Xref title="CDN cache" value="private-cdn" /> of those downloaded resources, which is used instead of reaching out to those remote locations to ensure availability.
240240

241241
Keep in mind that the Chocolatey CDN can only download resources for packages that it has been able to cache. While it is currently able to cache 70% of the existing packages ([https://chocolatey.org/stats](https://chocolatey.org/stats)) for actuals - use PackagesCached divided by UniquePackages), we always recommend running `choco search pkgid` (or `choco info pkgid`) to determine if it has the "Downloads cached for licensed users" aspect, or look on the package page for the indicator that the packages are cached. If it does not, you would either need to go through the process of internalization for that package, or look to whitelisting whatever resources that package needed to download.
242242

@@ -296,4 +296,4 @@ A non-administrative user should choose to install Chocolatey in a directory som
296296
## Report Issue
297297

298298
- Report general security issue - please email security [at] chocolatey dot io.
299-
- Report package malware/security/other package issue - please use the Report Abuse link directly on the package page on [https://community.chocolatey.org/packages](https://community.chocolatey.org/packages).
299+
- Report package malware/security/other package issue - please use the Report Abuse link directly on the package page on [https://community.chocolatey.org/packages](https://community.chocolatey.org/packages).

0 commit comments

Comments
 (0)