-
Notifications
You must be signed in to change notification settings - Fork 87
FIPS Commercial
JRuby-OpenSSL (FIPS) is distributed under GPL-3.0 see LICENSE
The GPL-3 copyleft requires that any product conveying (distributing) this software, or a work based on it, must also be available to the recipient under GPL-3, including the Corresponding Source for the entire combined work.
For organizations embedding jruby-openssl inside a product whose overall
licensing is incompatible with GPL-3 e.g. proprietary, source-available
(BUSL / Elastic License / SSPL), or under another copyleft that does not permit
GPL-3 a separate commercial license can be granted that removes the GPL-3
license obligations for that integration.
Typical use cases that require a commercial license:
- shipping a closed-source on-prem product, virtual appliance, or container
image that bundles
jruby-opensslto deliver FIPS certified cryptography - redistributing
jruby-opensslas part of a commercial JRuby distribution or product built on top of - offering
jruby-opensslas part of a managed-service / SaaS product where your overall product licensing forbids the GPL-3 license
Use cases that do not require a commercial license:
- internal use within your organization, with no distribution to third parties
- redistribution as part of a GPL-3 compatible open-source product
- evaluation, research, and development
For commercial licensing inquiries, including pricing and support contact:
Karol Bucek <jossl+fips@kares.org>
If you're already subscribed to JRuby support via headius\enterprises or are planning to do so (custom support requirements), post your inquiry there.
Please include:
- brief description of the product or service that will embed the artifact
- expected deployment footprint (number of installations / customers / hosts)
- the licensing of your overall product
The commercial edition is published to a private gem registry and carries a commercial license in place of the GPL one. Access to the commercial registry is granted as part of a commercial agreement.
The commercial gem is the same jruby-openssl (FIPS variant) artifact as the
public edition. It grants a non-exclusive, non-transferable, worldwide license
to embed and redistribute the FIPS variant of jruby-openssl within your own
proprietary or otherwise non-GPL products, lifting GPL-3.0 copyleft obligations
that govern the public edition.
This license does not certify your product as FIPS-validated, it provides cryptography that runs inside the NIST-validated BC-FJA module in approved-only mode; overall FIPS compliance of your system remains your responsibility.
-
The bundled Bouncy Castle FIPS module remains under the Bouncy Castle license, (see LICENSE.bouncycastle and the FIPS module section in README.md), their licensing is independent of this offer
-
This file is informational, the binding licensing terms of the open-source distribution are those in LICENSE (GPL-3.0). Commercial terms, when granted, are set out in a separate agreement.
---
Generated content - edits made here will be overwritten.