From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gentoo-dev+bounces-98488-garchives=archives.gentoo.org@lists.gentoo.org>
Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
	 key-exchange X25519 server-signature RSA-PSS (2048 bits))
	(No client certificate requested)
	by finch.gentoo.org (Postfix) with ESMTPS id 94B6A158020
	for <garchives@archives.gentoo.org>; Sat, 12 Nov 2022 13:15:23 +0000 (UTC)
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
	by pigeon.gentoo.org (Postfix) with SMTP id 284C8E09A7;
	Sat, 12 Nov 2022 13:15:19 +0000 (UTC)
Received: from smtprelay07.ispgateway.de (smtprelay07.ispgateway.de [134.119.228.99])
	(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
	(No client certificate requested)
	by pigeon.gentoo.org (Postfix) with ESMTPS id E37D2E0953
	for <gentoo-dev@lists.gentoo.org>; Sat, 12 Nov 2022 13:15:18 +0000 (UTC)
Received: from [89.0.39.202] (helo=[192.168.1.12])
	by smtprelay07.ispgateway.de with esmtpsa  (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
	(Exim 4.94.2)
	(envelope-from <jstein@gentoo.org>)
	id 1otqLs-0005fg-C1; Sat, 12 Nov 2022 14:15:16 +0100
Message-ID: <a7976c9f-eda8-5e87-2f81-152d3f112d1f@gentoo.org>
Date: Sat, 12 Nov 2022 14:15:16 +0100
Precedence: bulk
List-Post: <mailto:gentoo-dev@lists.gentoo.org>
List-Help: <mailto:gentoo-dev+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-dev+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-dev+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-dev.gentoo.org>
X-BeenThere: gentoo-dev@lists.gentoo.org
Reply-to: gentoo-dev@lists.gentoo.org
X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101
 Thunderbird/102.4.2
Subject: Re: [gentoo-dev] [RFC] A new GLSA schema
To: Sam James <sam@gentoo.org>
Cc: gentoo-dev <gentoo-dev@lists.gentoo.org>
References: <Y2xhlbizeJmhJ/AC@gentoo.org>
 <626eaf6c-f41e-3dfd-2750-39c4522175c1@gentoo.org>
 <Y22W8kqJskaMxDpS@gentoo.org>
 <CAHY5Mef4mnJpTpYCsd5E=D5Ex-27vNxVWZwJMDu9Kc1iADPqhw@mail.gmail.com>
 <62C57F52-AAF6-4105-9276-EA5CAAEABB7E@gentoo.org>
 <018B23C1-7F65-4D99-A2E0-03B5280918FC@gentoo.org>
 <bcec086e-a8dd-a083-3bcc-641c8c521076@gentoo.org>
 <E2F113C3-5676-4978-B8C1-D790E3BAA4DD@gentoo.org>
Content-Language: de-DE
From: Jonas Stein <jstein@gentoo.org>
In-Reply-To: <E2F113C3-5676-4978-B8C1-D790E3BAA4DD@gentoo.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Df-Sender: anNAam9uYXNzdGVpbi5kZQ==
X-Archives-Salt: 3a61aedb-8b79-4819-ba50-ec3394612f52
X-Archives-Hash: 70efc944fbdf6862d1514b09909838cc

>> CSAF is exactly what we want with GLSA.
>> There are already many tools to parse and pretty print the CSAF documents.
> Thanks, I'll look into it more. Can you offer to help implement it in Portage?

Not this year, but I can try to help.
There are many ready to use tools around csaf already.

You can also combine it with https://securitytxt.org/

Here is an example:
https://www.bsi.bund.de/.well-known/security.txt

The line
CSAF: https://cert-bund.de/.well-known/csaf/provider-metadata.json
tells where to find the csaf data.

-- 
Best,
Jonas