Skip to content

fix: clarify GPL license version in README#344

Open
MarkAtwood wants to merge 2 commits into
wolfSSL:masterfrom
MarkAtwood:fix/readme-license-version
Open

fix: clarify GPL license version in README#344
MarkAtwood wants to merge 2 commits into
wolfSSL:masterfrom
MarkAtwood:fix/readme-license-version

Conversation

@MarkAtwood

@MarkAtwood MarkAtwood commented Jun 17, 2026

Copy link
Copy Markdown

Summary

README.md references "GPLv2" without the "or later" qualifier, misrepresenting wolfSSL's actual license (GPL-2.0-or-later). Updated to use SPDX identifiers for clarity.

No code changes -- README only.

Copilot AI review requested due to automatic review settings June 17, 2026 17:58

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Note

Copilot was unable to run its full agentic suite in this review.

Updates README licensing text to accurately reflect wolfSSL’s GPL “or later” licensing option.

Changes:

  • Clarifies the bullet list reference from “GPLv2” to “GPLv2 or later”.
  • Simplifies the Licensing section wording while keeping the “or later” qualifier.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread README.md Outdated
* Progressive algorithm support (ChaCha20, Poly1305, Curve/Ed25519, etc)
* [Commercial support](https://www.wolfssl.com/products/support-and-maintenance/) available direct from wolfSSL engineers
* [Commercial licenses](https://www.wolfssl.com/license/) available (in addition to standard GPLv2)
* [Commercial licenses](https://www.wolfssl.com/license/) available (in addition to standard GPLv2 or later)
Comment thread README.md Outdated
# Licensing

wolfSSL and wolfCrypt are either licensed for use under the GPLv2 (or at your option any later version) or a standard commercial license. For users who cannot use wolfSSL under GPLv2 (or any later version), a commercial license to wolfSSL and wolfCrypt is available. For license inquiries, please contact wolfSSL Inc. directly at licensing@wolfssl.com.
wolfSSL and wolfCrypt are either licensed for use under the GPLv2 or later or a standard commercial license. For users who cannot use wolfSSL under GPLv2 or later, a commercial license to wolfSSL and wolfCrypt is available. For license inquiries, please contact wolfSSL Inc. directly at licensing@wolfssl.com.
@MarkAtwood MarkAtwood requested review from cconlon, dgarske and wolfSSL-Bot and removed request for dgarske June 17, 2026 18:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants