From c6b6e0a6e012485f74ac4f5ccd241be9d1df22e5 Mon Sep 17 00:00:00 2001 From: Joshua Lock Date: Fri, 18 Aug 2023 11:57:35 +0100 Subject: [PATCH] editorial: fix broken links to .md files MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit There are several places in the generated site where links are broken because they still include the .md file extension. It's unclear why jekyll-relative-links is broken _only_ in these instances, but this surgical change resolves broken links on the site until the wider issue can be addressed. Before this patch: ``` % git grep --color --no-index 'href="[^h][^"]*\.md' _site _site/blog.html:the valuable feedback we received on the first release candidate. This is _site/blog.html:

Interested in getting involved? Now’s the chance to provide your feedback on the foundational v1 release of the SLSA framework.

_site/example.html:

SLSA 4 requires two-party source control and hermetic builds. _site/how-to-orgs.html:https://slsa.dev/provenance/.

_site/spec/v1.0-rc2/onepage.html:

SLSA v1.0 does not address this threat, but it may be addressed in a future _site/spec/v1.0-rc2/onepage.html:

SLSA v1.0 does not address this threat, but it may be addressed in a future _site/spec/v1.0-rc2/threats.html:

SLSA v1.0 does not address this threat, but it may be addressed in a future _site/spec/v1.0-rc2/threats.html:

SLSA v1.0 does not address this threat, but it may be addressed in a future _site/spec/v1.0/onepage.html:

SLSA v1.0 does not address this threat, but it may be addressed in a future _site/spec/v1.0/onepage.html:

SLSA v1.0 does not address this threat, but it may be addressed in a future _site/spec/v1.0/threats.html:

SLSA v1.0 does not address this threat, but it may be addressed in a future _site/spec/v1.0/threats.html:

SLSA v1.0 does not address this threat, but it may be addressed in a future ``` - the two blog.html instances are resolved by editing the individual blog posts to remove the .md file extension - the example.html instance will be resolved by #945 - how-to-orgs.html is fixed by removing the .md extension line 20 of how-to-orgs.md - the v1.0-rc2 threats and onepage are fixed by removing the .md extension in lines 40 and 49 of spec/v1.0-rc2/threats.md - the v1.0 threats and onepage are fixed by removing the .md extension in lines 40 and 49 spec/v1.0/threats.md Following these changes: ``` % git grep --color --no-index 'href="[^h][^"]*\.md' _site _site/example.html:

SLSA 4 requires two-party source control and hermetic builds. ``` which is resolved by the removal of example.md in PR#945 Signed-off-by: Joshua Lock --- docs/_posts/2023-04-03-the-breadth-and-depth-of-slsa.md | 2 +- docs/_posts/2023-04-04-slsa-v1-rc2.md | 2 +- docs/how-to-orgs.md | 2 +- docs/spec/v1.0-rc2/threats.md | 4 ++-- docs/spec/v1.0/threats.md | 4 ++-- 5 files changed, 7 insertions(+), 7 deletions(-) diff --git a/docs/_posts/2023-04-03-the-breadth-and-depth-of-slsa.md b/docs/_posts/2023-04-03-the-breadth-and-depth-of-slsa.md index 9f21915a4..e5593bdeb 100644 --- a/docs/_posts/2023-04-03-the-breadth-and-depth-of-slsa.md +++ b/docs/_posts/2023-04-03-the-breadth-and-depth-of-slsa.md @@ -4,7 +4,7 @@ author: "Mike Lieberman" is_guest_post: false --- -Interested in getting involved? Now’s the chance to [provide your feedback on the foundational v1 release of the SLSA framework.](2023-02-24-slsa-v1-rc.md) +Interested in getting involved? Now’s the chance to [provide your feedback on the foundational v1 release of the SLSA framework.](2023-02-24-slsa-v1-rc) “Software Supply chain security is more than just the build” is a common response when folks learn about SLSA. This is true. SLSA 1.0 is entirely focused on generating [build provenance](/spec/v1.0/provenance) and assurance around that provenance due to the security capabilities of the build system and security properties of a particular running build. Software Supply Chain Security is the cybersecurity practice of extending left into System Delivery Lifecycle or Software Delivery Lifecycle and the SDLC is more than just the build. diff --git a/docs/_posts/2023-04-04-slsa-v1-rc2.md b/docs/_posts/2023-04-04-slsa-v1-rc2.md index 4ab2d104a..fb0f7ca8f 100644 --- a/docs/_posts/2023-04-04-slsa-v1-rc2.md +++ b/docs/_posts/2023-04-04-slsa-v1-rc2.md @@ -26,7 +26,7 @@ all early adopters who have provided valuable feedback on the previous release candidate. Thank you for your contributions to the project! [GitHub issue]: https://github.com/slsa-framework/slsa/issues -[RC1]: 2023-02-24-slsa-v1-rc.md +[RC1]: 2023-02-24-slsa-v1-rc [RC2]: /spec/v1.0-rc2/ [backlog]: https://github.com/orgs/slsa-framework/projects/1/views/1 [Approved Specification]: /spec-stages#approved diff --git a/docs/how-to-orgs.md b/docs/how-to-orgs.md index bd7475a56..db4c4b00b 100644 --- a/docs/how-to-orgs.md +++ b/docs/how-to-orgs.md @@ -17,7 +17,7 @@ For all [SLSA levels](/spec/v1.0/levels.md), you follow the same steps: What differs for each level is the robustness of the build and provenance. For more information about SLSA provenance see -[https://slsa.dev/provenance/](/provenance/v1.md). +[https://slsa.dev/provenance/](/provenance/v1). SLSA Build levels are progressive: SLSA Build L3 includes all the guarantees of SLSA Build L2, and SLSA Build L2 includes all the guarantees of SLSA Build L1. diff --git a/docs/spec/v1.0-rc2/threats.md b/docs/spec/v1.0-rc2/threats.md index 496e23d2a..58aaffb35 100644 --- a/docs/spec/v1.0-rc2/threats.md +++ b/docs/spec/v1.0-rc2/threats.md @@ -37,7 +37,7 @@ An adversary introduces a change through the official source control management interface without any special administrator privileges. SLSA v1.0 does not address this threat, but it may be addressed in a [future -version](future-directions.md). +version](future-directions). ### (B) Compromise source repo @@ -46,7 +46,7 @@ administrative interface, or through a compromise of the underlying infrastructure. SLSA v1.0 does not address this threat, but it may be addressed in a [future -version](future-directions.md). +version](future-directions). ### (C) Build from modified source diff --git a/docs/spec/v1.0/threats.md b/docs/spec/v1.0/threats.md index f188d5a53..a9dfb5979 100644 --- a/docs/spec/v1.0/threats.md +++ b/docs/spec/v1.0/threats.md @@ -39,7 +39,7 @@ An adversary introduces a change through the official source control management interface without any special administrator privileges. SLSA v1.0 does not address this threat, but it may be addressed in a [future -version](future-directions.md). +version](future-directions). ### (B) Compromise source repo @@ -48,7 +48,7 @@ administrative interface, or through a compromise of the underlying infrastructure. SLSA v1.0 does not address this threat, but it may be addressed in a [future -version](future-directions.md). +version](future-directions). ### (C) Build from modified source