"The Secure Software Supply Chain" by Kelsey Hightower (Strange Loop 2022)

Поділитися
Вставка
  • Опубліковано 1 гру 2024

КОМЕНТАРІ • 10

  • @ntippy
    @ntippy 2 роки тому +10

    This is StrangeLoop at its best. Educational and Entertaining.

  • @tonybaptista7560
    @tonybaptista7560 Рік тому

    Really enjoyed your presentation 👍

  • @lerneninverschiedenenforme7513

    highly underrated!

  • @Verrisin
    @Verrisin 2 роки тому +3

    package managers should use Content hashing for dependencies. Sensible, safer ... if it used something like IPFS it could even make the sharing simpler...

  • @sebastiengauthier58
    @sebastiengauthier58 2 роки тому +2

    Awesome talk!

  • @terpimost
    @terpimost 2 роки тому +1

    awesome talk!

  • @garfieldnate
    @garfieldnate 2 роки тому +5

    To be clear, this signing stuff only allows you to verify that a human looked at the list of dependencies, right? I think some more signatures should be in there, such as the signature of the company running the build (GitHub if using actions, etc.), as well as some sort of signed hash for any stdlib bundled in (for native, e.g. C++ apps). After that you also need each of the dependencies that were included to themselves be built with the same supply chain verification signature for any of this to mean anything, right?

  • @superscatboy
    @superscatboy 2 роки тому +1

    This guy is a *great* speaker!

  • @remram44
    @remram44 2 роки тому +4

    I don't get the security model. You are worried that dependencies might be untrustworthy... so you run their arbitrary build code anyway, and then have that compromised environment generate the BOM and sign it? This sequence of operations seems fundamentally flawed to me.

  • @K4iserchen
    @K4iserchen 2 роки тому +3

    29:17 moves on to not sha-pin his github actions O.O