dan
/
jekyll
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Typo

This commit is contained in:
Frank Taillandier 2018-09-27 14:47:22 +02:00 committed by GitHub
parent 3055992712
commit 4a6edf4778
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/_posts/2018-09-19-security-fixes-for-3-6-3-7-3-8.markdown
View File

@ -12,13 +12,13 @@ bring that patch to you. The vulnerability allowed arbitrary file reads with the
config file. config file.
By simply including a symlink in the `include` array allowed the symlinked file to be read into the build when they shouldn't By simply including a symlink in the `include` array allowed the symlinked file to be read into the build when they shouldn't
actually be read in any circumstance. <br/> actually be read in any circumstance.  
Further details regarding the patch can be viewed at the [pull request URL]({{ site.repository }}/pull/7224) Further details regarding the patch can be viewed at the [pull request URL]({{ site.repository }}/pull/7224)
The patch has been released as versions `3.6.3`, `3.7.4` and `3.8.4`.<br/> The patch has been released as versions `3.6.3`, `3.7.4` and `3.8.4`.  
`v3.7.4` was released a couple of weeks prior and has been bundled with `github-pages-v192`. `v3.7.4` was released a couple of weeks prior and has been bundled with `github-pages-v192`.
Please keep in mind that this issue affects _all previously released Jekyll versions_. If you have not had Please keep in mind that this issue affects _all previously released Jekyll versions_. If you have not had
a good reason to upgrade to `3.6`, `3.7` or `3.8` yet, we advise that you do so at your earliest. a good reason to upgrade to `3.6`, `3.7` or `3.8` yet, we advise that you do so at the earliest.
As always, Happy Jekylling! :sparkles: As always, Happy Jekylling! :sparkles: