aboutcode-org / aboutcode-org/scancode-toolkit

OpenSSL license still detected for Apache-2.0 license

Offen
#3,381 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
bug
Vorherrschende Sprache
Python
Sterne
2.6k
Forks
791
Ø Merge
1 T. 12 Std.
Gemergte PRs (30 T.)
5

Beschreibung

### Description

The OpenSSL project have changed the main license from OpenSSL License to Apache-2.0 in 2021. For new versions of OpenSSL like 3.0.7 and 3.0.8 Scancode still finds the OpenSSL License for files where the license information is changed to Apache-2.0.

### How To Reproduce

A scan with scancode-toolkit-31.2.6 (options: -clpieu --licenses-reference --classify --license-text --license-text-diagnostics --strip-root --timeout 300) of OpenSSL-3.0.7 still results in wrong OpenSSL License findings. Scancode does not identify that the license of OpenSSL has been changed to Apache-2.0. There are some Apache-2.0 license findings but this are not the files with the changed license text like the example file ciphers.c. Over 3300 files in the OpenSSL package have a changed license text since version 3.0.0 released on 07.10.2021.

### System configuration

* A local scan on a Oracle VM VirtualBox with Linux
* scancode-toolkit-31.2.6

I have appended file finding_ciphers.c_sc.json (the cipher.c section of the OpenSSL-3.0.7.json scan result) to show that scancode-toolkit-31.2.6 released on 25.04.2023 still identifies the wrong license.

[finding_ciphers.c_sc.json.zip](https://github.com/nexB/scancode-toolkit/files/11380820/finding_ciphers.c_sc.json.zip)

Beitragsleitfaden

Beitragsleitfaden öffnen

Bewertung

Dieses Issue wurde noch nicht bewertet.

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.