Question about commercial use / alternative license

[YuvalAmit8471]

Description
This is not a bug report. It’s a license clarification request regarding commercial use.

Steps to Reproduce
N/A — no reproducible steps. This is a policy question.

Expected Behavior
A clear statement on whether GPLv3 licensed SSLClient can be used inside a commercial, closed-source product (distributed to customers).

Actual Behavior
N/A — information request only.

Environment
N/A

IDE
N/A

---

Hi,

First, thank you for your great work on SSLClient.

I noticed the project is licensed under GPLv3. I’d like to clarify if the library can be used inside a commercial (closed-source) product. My understanding is that GPLv3 generally requires derivative/distributed works to be GPL-compatible and therefore open the source code, which would not fit our use case.

1. Is there any permitted way to use SSLClient in a closed-source, commercially distributed application under the current license?
2. If not, would you consider offering an alternative license (e.g., MIT, BSD-3, or Apache-2.0) or a dual-license / commercial license option?

Happy to provide more details about our use case (linkage model, distribution, etc.) if helpful.

Thanks!

[github-actions]

The following fields are missing: Description, Steps to Reproduce, Expected Behavior, Actual Behavior, Environment, IDE. Please update the issue with this information.

[YuvalAmit8471]

Updated the issue to follow the repository’s issue template (added Description/Steps/Expected/Actual/Environment/IDE). This is a license clarification request rather than a bug report. Thanks!

[anthonyhoegberg]

Im also interested in this topic, currently had to rewrite a lot of code for manual management and other connection approaches but this would be cool to have