cncf
[License Exception Request] Connect: allow OpenSSL license for swift-nio-ssl
Component details
The component is swift-nio-ssl, part of Swift's non-blocking networking stack, at the most recent version. (All versions I checked have the same problem, but let's focus on the latest version.)
The repository is https://github.com/apple/swift-nio-ssl. The repository as a whole claims to be available under an Apache 2 license, but it includes code that's licensed under the OpenSSL license. The text in that file also allows use under the CRYPTOGAMS license or GPL v2.
License name
OpenSSL
Code modified?
Unmodified
Changes contributed?
N/A
Any alternatives?
As far as I know, swift-nio-ssl is the only way to use HTTP/2 + TLS and have access to HTTP trailers on iOS.
Integrates with other components?
connect-swift is an RPC library that's part of the broader Connect project, which recently joined the CNCF Sandbox. swift-nio-ssl is a build-time dependency of the connect-swift subpackage that offers gRPC compatibility.
For context, swift-nio-ssl is also used in gRPC's Swift implementation: https://github.com/grpc/grpc-swift/blob/main/Package.swift#L81.
The CNCF Governing Board has approved this exception request in an October vote.
