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
..
src	Fix handling of non direct backed PemEncoded.	2016-08-16 09:04:38 +02:00
pom.xml	[maven-release-plugin] prepare for next development iteration	2016-07-27 13:29:56 +02:00