From 9d3e738757fd352fa307eb4c9852fa3cebd740bb Mon Sep 17 00:00:00 2001
From: Marco Verleun <marco@verleun.org>
Date: Tue, 7 Nov 2023 16:02:56 +0100
Subject: [PATCH] test

---
 slides/sbom/sboms.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/slides/sbom/sboms.md b/slides/sbom/sboms.md
index ea99c51..91a4013 100644
--- a/slides/sbom/sboms.md
+++ b/slides/sbom/sboms.md
@@ -53,7 +53,7 @@ But the end result is quite different:
 (Scanning was done with `grype` and since the writing of this presentation the numbers have increased)
 
 ---
-
+<!---
 ## Providing information about software components
 
 More and more organisations want to know which software components they are about to deploy in a well know format. Executive Order 14028 on Improving the Nation's Cybersecurity does the same.
@@ -111,4 +111,4 @@ How nice would it be if a simple lookup would reveal if a new CVE impacts our or
 
 Maintaining a database of SBOM's helps to identify which host, oci container image, appliance or application is using a vulnerable software component without the need the (re)scan them when new CVE's are announced (which is daily).
 
----
\ No newline at end of file
+--->
\ No newline at end of file