Skip to content

Commit ea4fb3b

Browse files
committed
Add license and notice for ubuntu importer
Signed-off-by: Tushar Goel <[email protected]>
1 parent 7b01a57 commit ea4fb3b

File tree

1 file changed

+42
-2
lines changed

1 file changed

+42
-2
lines changed

vulnerabilities/importers/ubuntu.py

+42-2
Original file line numberDiff line numberDiff line change
@@ -19,8 +19,48 @@
1919

2020

2121
class UbuntuImporter(OvalImporter):
22-
spdx_license_expression = "GPL"
23-
license_url = "https://ubuntu.com/legal/terms"
22+
spdx_license_expression = "LicenseRef-scancode-other-permissive"
23+
notice = """
24+
From: Seth Arnold <[email protected]>
25+
Date: Wed, Jan 25, 2023 at 2:02 AM
26+
Subject: Re: [ubuntu-hardened] Usage of Ubuntu Security Data in VulnerableCode
27+
To: Tushar Goel <[email protected]>
28+
29+
30+
31+
On Wed, Jan 11, 2023 at 06:27:38PM +0530, Tushar Goel wrote:
32+
> We would like to integrate the Ubuntu usn data[1][2] and
33+
> Ubuntu security data (OVAL format)[3] in vulnerablecode[4]
34+
> which is a FOSS db of FOSS vulnerability data. We were not
35+
> able to know under which license this security data comes.
36+
> We would be grateful to have your acknowledgement over usage of
37+
> the ubuntu security data in vulnerablecode and have
38+
> some kind of licensing declaration from your side.
39+
40+
Hello Tushar, we do not have an explicit license on this data.
41+
42+
We share our data with the intention that others will use it. Please
43+
feel free to use it for the general furtherance of security.
44+
45+
Much of the data that's contained within our databases is sourced from
46+
third parties, who also shared their data with the intention that others
47+
will use it. I'm not sure what it would look like to try to put a license
48+
on data that is crowd-sourced from thousands of contributors. (If you were
49+
to start such a project today, it'd probably be one of the first things to
50+
formalize. But when CVE was started two decades ago, the primary goal was
51+
sharing knowledge and simplifying the vulnerability remediation process,
52+
and licensing the data was, as far as I can remember, not considered.
53+
Sharing was the goal.)
54+
55+
I will ask that vulnerablecode 'be nice' to our infrastructure that
56+
hosts the databases -- some automated uses of our infrastructure by
57+
vulnerability scanner tools has lead to significant load and engineering
58+
effort. In general, please prefer a small handful of systems updating
59+
mirrors roughly twice a day rather than thousands of hosts pulling
60+
data hourly.
61+
62+
Thanks
63+
"""
2464

2565
def __init__(self, *args, **kwargs):
2666
super().__init__(*args, **kwargs)

0 commit comments

Comments
 (0)