Roger Kapsi b963595988 Fix handling of non direct backed PemEncoded. ... Motivation: The private key and certificate that are passed into #serKeyMaterial() could be PemEncoded in which case the #toPEM() methods return the identity of the value. That in turn will fail in the #toBIO() step because the underlying ByteBuf is not necessarily direct. Modifications: - Use toBIO(...) which also works with non direct PemEncoded values - Add unit test. Result: Correct handling of PemEncoded.		2016-08-16 09:04:38 +02:00
..
java/io/netty/handler	Fix handling of non direct backed PemEncoded.	2016-08-16 09:04:38 +02:00
resources/io/netty/handler/ssl	Using distinct aliases when building the trust manager factory, and renamed trustCertChain into trustCertCollection.	2016-03-22 21:12:10 +01:00