SwiftNIO SSL is a Swift package that contains an implementation of TLS based on OpenSSL-compatible libraries (that is, any library that ships a libssl that is compatible with OpenSSL's). This package allows users of SwiftNIO to write protocol clients and servers that use TLS to secure data in flight.
The name is inspired primarily by the names of the libraries this package supports (e.g. OpenSSL, LibreSSL, and friends), and not because we don't know the name of the protocol. We know the protocol is TLS!
Using SwiftNIO SSL
SwiftNIO SSL provides two
ChannelHandlers to use to secure a data stream: the
OpenSSLClientHandler and the
OpenSSLServerHandler. Each of these can be added to a
Channel to secure the communications on that channel.
Additionally, we provide a number of low-level primitives for configuring your TLS connections. These will be shown below.
To secure a server connection, you will need a X.509 certificate chain in a file (either PEM or DER, but PEM is far easier), and the associated private key for the leaf certificate. These objects can then be wrapped up in a
TLSConfiguration object that is used to initialize the
let configuration = TLSConfiguration.forServer(certificateChain: [.file("cert.pem")], privateKey: .file("key.pem")) let sslContext = try SSLContext(configuration: configuration) let handler = try OpenSSLServerHandler(context: sslContext) // Add the created handler to the pipeline.
For clients, it is a bit simpler as there is no need to have a certificate chain or private key (though clients may have these things). Setup for clients may be done like this:
let configuration = TLSConfiguration.forClient() let sslContext = try SSLContext(configuration: configuration) let handler = try OpenSSLClientHandler(context: sslContext) // Add the created handler to the pipeline.
This binding can cause numerous issues during the build process on different systems, depending on the environment you're in. These will usually manifest as build errors, either during the compilation stage (due to missing development headers) or during the linker stage (due to an inability to find a library to link).
If you encounter any of these errors, here are your options.
On Darwin systems, there is no easily-available copy of
libssl.dylib with accompanying development headers. For this reason, we recommend installing libressl from Homebrew (
brew install libressl).
On Linux distributions it is almost always possible to get development headers for the system copy of libssl (e.g. via
apt-get install libssl-dev). If you encounter problems during the compile phase, try running this command.
In some unusual situations you may encounter problems during the link phase. This is usually the result of having an extremely locked down system that does not grant you sufficient permissions to the
libssl.so on the system.
Help us keep the lights on
1.2.0 - Jul 24, 2018
- Support users supplying a passphrase callback for private keys with passphrases on both the
OpenSSLPrivateKeyand to the
OpenSSLPKCS12Bundlestructure for accessing the contents of a PKCS#12 bundle. (#23)
- Fixed a bug where the initializer for
OpenSSLCertificatethat used a buffer of memory could accidentally escape a pointer from a
- Improved syscall handling, reducing the risk of errors from return codes like EINTR. (#24)
1.1.1 - May 22, 2018
EmbeddedChannelin tests to ensure that write promises are succeeded. (#15)
1.1.0 - Apr 30, 2018
- Expose the OpenSSL MD5 header file in
1.0.1 - Mar 26, 2018
- Stopped performing
@testableimports of NIO. (#11)