7ed105adbf
Motivation OpenSslContext is expecting Java's PrivateKey and X509Certificate objects as input (for JdkSslContext API compatibility reasons) but doesn't really use them beyond turning them into PEM/PKCS#8 strings. This conversion can be entirely skipped if the user can pass in private keys and certificates in a format that Netty's OpenSSL code can digest. Modifications Two new classes have been added that act as a wrapper around the pre-encoded byte[] and also retain API compatibility to JdkSslContext. Result It's possible to pass PEM encoded bytes straight into OpenSSL without having to parse them (e.g. File to Java's PrivateKey) and then encode them (i.e. PrivateKey into PEM/PKCS#8). File pemPrivateKeyFile; byte[] pemBytes = readBytes(pemPrivateKeyFile); PemPrivateKey pemPrivateKey = PemPrivateKey.valueOf(pemBytes); SslContextBuilder.forServer(pemPrivateKey) .sslProvider(SslProvider.OPENSSL)
Netty Project
Netty is an asynchronous event-driven network application framework for rapid development of maintainable high performance protocol servers & clients.
Links
How to build
For the detailed information about building and developing Netty, please visit the developer guide. This page only gives very basic information.
You require the following to build Netty:
- Latest stable Oracle JDK 7
- Latest stable Apache Maven
- If you are on Linux, you need additional development packages installed on your system, because you'll build the native transport.
Note that this is build-time requirement. JDK 5 (for 3.x) or 6 (for 4.0+) is enough to run your Netty-based application.
Branches to look
Development of all versions takes place in each branch whose name is identical to <majorVersion>.<minorVersion>. For example, the development of 3.9 and 4.0 resides in the branch '3.9' and the branch '4.0' respectively.