Skip to contentSkip to conversation

openssl: correct license comment

PATCH New Paul Eggleton 1 participant 1 message Oct 16, 2018

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 openssl: correct license comment

The comment here stated that openssl is dual-licensed, but that would mean that either of the two licenses could be used which is *not* the case [1]. However LICENSE = "openssl" *is* correct because in OE that maps to a generic license file which includes both licenses, which makes sense because there isn't really any such thing as OpenSSL that would be covered by the "OpenSSL license" and not the "SSLeay license". Correct the comment to avoid any confusion.

[1] https://www.openssl.org/source/license.html

---
 meta/recipes-connectivity/openssl/openssl_1.1.1.bb | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)
meta/recipes-connectivity/openssl/openssl_1.1.1.bb +2 -1
index 03518586877..0d80aba64d7 100644
@@ -4,7 +4,8 @@ HOMEPAGE = "http://www.openssl.org/"
 BUGTRACKER = "http://www.openssl.org/news/vulnerabilities.html"
 SECTION = "libs/network"
 
-# "openssl | SSLeay" dual license
+# "openssl" here actually means both OpenSSL and SSLeay licenses apply
+# (see meta/files/common-licenses/OpenSSL to which "openssl" is SPDXLICENSEMAPped)
 LICENSE = "openssl"
 LIC_FILES_CHKSUM = "file://LICENSE;md5=d57d511030c9d66ef5f5966bee5a7eff"
 
Signature · 1 line
2.17.2