javax.net.ssl, https clients and close_notify -
javax.net.ssl, https clients and close_notify -
simple netty implementation of https server utilizing javax.net.ssl, self-signed certificate. server up, , request made using dhc restlet. on server side get:
io.netty.handler.ssl.sslhandler sethandshakefailure warning: sslengine.closeinbound() raised exception due closed connection. javax.net.ssl.sslexception: inbound closed before receiving peer's close_notify: possible truncation attack? @ sun.security.ssl.alerts.getsslexception(unknown source) @ sun.security.ssl.sslengineimpl.fatal(unknown source) @ sun.security.ssl.sslengineimpl.fatal(unknown source) @ sun.security.ssl.sslengineimpl.closeinbound(unknown source) @ io.netty.handler.ssl.sslhandler.sethandshakefailure(sslhandler.java:905) @ io.netty.handler.ssl.sslhandler.channelinactive(sslhandler.java:576) @ io.netty.channel.defaultchannelhandlercontext.invokechannelinactive(defaultchannelhandlercontext.java:819) @ io.netty.channel.defaultchannelhandlercontext.access$1300(defaultchannelhandlercontext.java:38) @ io.netty.channel.defaultchannelhandlercontext$5.run(defaultchannelhandlercontext.java:808) @ io.netty.channel.singlethreadeventexecutor.runalltasks(singlethreadeventexecutor.java:259) @ io.netty.channel.nio.nioeventloop.run(nioeventloop.java:305) @ io.netty.channel.singlethreadeventexecutor$2.run(singlethreadeventexecutor.java:110) @ java.lang.thread.run(unknown source)
and on client side:
no response. certificate valid? click here check.
issuing same request @ chrome's address bar, same server-side exception. issuing same @ firefox's address bar, same exception while firefox displaying warning page certificate not beingness trusted ca. this exception seems generic , not straight indicating state of protocol is. mean these 3 clients (chrome, firefox, dhc restlet), not playing protocol nicely , disappearing on server rather sending close_notify? or client-side behavior mandated ssl rfc's or security oriented client-side design?
i have contacted dhc restlet team , have told me workaround:
chrome doesn't provide api managing certificates. in other words, have no api automatically take certificate nor way how raise 'untrusted certificate' dialog. but, can utilize little workaround:
open https url in tab. manually take certificate. go dhc , work because certificate has been accepted manually (is stored in chrome) previous step.usually have once.
ssl https dhc
Comments
Post a Comment