This project is mirrored from https://github.com/slsa-framework/slsa.git. Pull mirroring updated .
  1. 07 Jun, 2021 2 commits
    • Mark Lodato's avatar
      Replace nouns with adjectives in requirements. · 068b4911
      Mark Lodato authored
      This reads better and is consistent with the new provenance
      requirements, which all use adjectives.
      
      Example: Isolation -> Isolated.
      068b4911
    • Mark Lodato's avatar
      Add SLSA 1.5 and split Tamper Resistant. · 67ba6585
      Mark Lodato authored
      Add a new level, SLSA 1.5, between 1 and 2. We will renumber all the
      levels to integers right before we finalize the first version. In the
      meantime, we keep numbering the same to reduce confusion.
      
      Split Tamper Resistant into Authenticated + Service Generated +
      Non-Falsifiable. This split makes the meaning more clear, particularly
      that SLSA 1 is unauthenticated. SLSA 1.5 requires only the first two,
      with non-falsifiable being a property at SLSA 2.
      67ba6585
  2. 04 Jun, 2021 3 commits
    • Kim Lewandowski's avatar
      fixing typo · 117a3256
      Kim Lewandowski authored
      117a3256
    • Joshua Lock's avatar
      Revert "Remove broken links to SRS Book PDF (#25)." · 7ac6f64c
      Joshua Lock authored
      The PDF is available again.
      
      This reverts commit 85861abf.
      7ac6f64c
    • Mark Lodato's avatar
      Rework SLSA requirements. · 2b328fb8
      Mark Lodato authored
      SLSA 1 is now fully defined and has lower requirements.
      
      Major changes:
      
      - Replace "Readability" with "Version Control", removed at SLSA 1.
      - Add "Build Service", required at SLSA 2.
      - Split "Provenance" into three rows, and do not require tamper
        resistance (e.g. signing) until SLSA 2.
      - Remove "Enforcement". This is now orthogonal to the level.
      - Do not require "Logging", "Policy", or "Common" until SLSA 2.
      - Simplify "Policy" to not talk about build entry point.
      
      Minor changes:
      
      - Rename "Change History" to "Verified History".
      2b328fb8
  3. 03 Jun, 2021 2 commits
  4. 02 Jun, 2021 3 commits
  5. 26 May, 2021 1 commit
  6. 18 May, 2021 3 commits
  7. 10 May, 2021 2 commits
  8. 07 May, 2021 1 commit
  9. 30 Apr, 2021 2 commits
  10. 26 Apr, 2021 1 commit
    • Mark Lodato's avatar
      Remove broken links to SRS Book PDF (#25). · 85861abf
      Mark Lodato authored
      Looks like Google took down the free copy of the book, so we just have
      to link to the landing page. That also means we can't use that as one of
      our "benefits of reproducible builds" links. :-(
      85861abf
  11. 22 Apr, 2021 1 commit
  12. 21 Apr, 2021 1 commit
  13. 19 Apr, 2021 2 commits
  14. 13 Apr, 2021 2 commits
  15. 12 Apr, 2021 3 commits
    • Mark Lodato's avatar
      Require Reproducibility or a justification. · fdcd336d
      Mark Lodato authored
      Previously we only "recommended" reproducibility. This was both very
      weak and also unenforceable.
      
      Now we require Reproducibility unless there is a justification why it is
      not. This is a much stronger motivation to make things Reproducible: it
      is the path of least resistance. Furthermore, this can now be checked
      in an automated way: either the "reproducible" bit is set or the
      "justification" is non-empty. We will likely want to have an enum of
      valid justifications, but that will be decided once we write detailed
      builder requirements.
      fdcd336d
    • Mark Lodato's avatar
      Add Reproducibility as a recommendation for SLSA 3. · 5310e40a
      Mark Lodato authored
      At SLSA 3, we now recommend reproducible builds. This is not a strict
      requirement because not all builds can become reproducible, as explained
      in the text. Once we write the detailed requirements, we will likely
      want to somehow explain that reproducible should be the default, while
      still allowing individual projects to opt-out.
      
      The reason for adding this recommendation is to move the industry
      towards reproducibility, which is a generally useful property. By having
      it as the "default" path, most software will just go with the past of
      least resistance rather than opting out.
      
      Note that this does not require *verifying* the reproduction for
      security. Instead, the builder just claims that it was reproducible,
      presumably by building it twice and making sure that the output is
      identical.
      5310e40a
    • Mark Lodato's avatar
      Merge pull request #16 from MarkLodato/nits · 684bbf7c
      Mark Lodato authored
      Small fixes 
      684bbf7c
  16. 09 Apr, 2021 2 commits
  17. 06 Apr, 2021 2 commits
  18. 02 Apr, 2021 3 commits
  19. 01 Apr, 2021 2 commits
    • Mark Lodato's avatar
      attestations: add more words about typing · a9e27a41
      Mark Lodato authored
      a9e27a41
    • Mark Lodato's avatar
      attestations: Simplify the model. · 5be970bc
      Mark Lodato authored
      - Add an Overview section explaiing the relationship between raw
        signatures and attestations.
      - Remove the policy diagram since it's not germaine to this doc.
      - Remove the Type fields, since they are an implementation detail.
      - Remove most of the requirements since they're not super helpful.
        Instead, make the Summary section explain the most important bits.
      - Move "Materials" to the Predicate layer and rename to "Link", since
        that is where it logically belongs and matches English.
      - Add a bunch of future items, based on feedback.
      5be970bc
  20. 30 Mar, 2021 2 commits