3 ms·
Personally I'd just use Debian as my SBOM if one was required. For anything open source, just make new packages and upload them to Debian. It has probably many
by pabs3 5y ago
Personally I'd just use Debian as my SBOM if one was required. For anything open source, just make new packages and upload them to Debian. It has probably many of the things needed (including in-progress deterministic reproducible builds), apart from building proprietary software, but you can create Debian packages internally and use your own build servers and apt repository.
https://www.reproducible-builds.org/ https://www.reproducible-builds.org/
https://tests.reproducible-builds.org/debian/reproducible.html https://tests.reproducible-builds.org/debian/reproducible.ht...
Any other distro can be treated similarly really.
- rswail 5y agoThat's fine if you're running on a Linux platform, but if you're running on AWS/GCP/Azure with lambdas/workers/serverless, you need to have the SBOM for your own software. Not everything is going to be accepted as part of Debian as a distribution.
- pabs3 5y agoIf you are using a proprietary cloud platform there can be no real SBOM, because you're relying on software you can't even get a hash of. The SBOM for the part of the software that you do control when running on such platformas has to be something that the proprietary platform supports, which obviously will have zero overlap with Debian packaging, so in that situation you just need to look at what the platform supports. For situations where one is using Debian but also software not in Debian, you can create an internal apt repository and make internal .deb packages to put in the internal apt repository.