Examples of com.facebook.presto.jdbc.internal.netty.handler.ssl.SslHandler$PendingWrite

Package com.facebook.presto.jdbc.internal.netty.handler.ssl

Examples of com.facebook.presto.jdbc.internal.netty.handler.ssl.SslHandler$PendingWrite

com.facebook.presto.jdbc.internal.netty.handler.ssl.SslHandler
kipedia.org/wiki/Transport_Layer_Security">SSL · TLS and StartTLS support to a {@link Channel}. Please refer to the "SecureChat" example in the distribution or the web site for the detailed usage.
Beginning the handshake

You must make sure not to write a message while the {@linkplain #handshake() handshake} is in progress unless you arerenegotiating. You will be notified by the {@link ChannelFuture} which isreturned by the {@link #handshake()} method when the handshakeprocess succeeds or fails.
Handshake

If {@link #isIssueHandshake()} is {@code false}(default) you will need to take care of calling {@link #handshake()} by your own. In mostsituations were {@link SslHandler} is used in 'client mode' you want to issue a handshake oncethe connection was established. if {@link #setIssueHandshake(boolean)} is set to {@code true}you don't need to worry about this as the {@link SslHandler} will take care of it.

Renegotiation

If {@link #isEnableRenegotiation() enableRenegotiation} is {@code true}(default) and the initial handshake has been done successfully, you can call {@link #handshake()} to trigger the renegotiation.
If {@link #isEnableRenegotiation() enableRenegotiation} is {@code false}, an attempt to trigger renegotiation will result in the connection closure.
Please note that TLS renegotiation had a security issue before. If your runtime environment did not fix it, please make sure to disable TLS renegotiation by calling {@link #setEnableRenegotiation(boolean)} with{@code false}. For more information, please refer to the following documents:
Closing the session

To close the SSL session, the {@link #close()} method should becalled to send the {@code close_notify} message to the remote peer. Oneexception is when you close the {@link Channel} - {@link SslHandler}intercepts the close request and send the {@code close_notify} messagebefore the channel closure automatically. Once the SSL session is closed, it is not reusable, and consequently you should create a new {@link SslHandler} with a new {@link SSLEngine} as explained in thefollowing section.
Restarting the session

To restart the SSL session, you must remove the existing closed {@link SslHandler} from the {@link ChannelPipeline}, insert a new {@link SslHandler} with a new {@link SSLEngine} into the pipeline,and start the handshake process as described in the first section.
Implementing StartTLS

StartTLS is the communication pattern that secures the wire in the middle of the plaintext connection. Please note that it is different from SSL · TLS, that secures the wire from the beginning of the connection. Typically, StartTLS is composed of three steps:
1. Client sends a StartTLS request to server.
2. Server sends a StartTLS response to client.
3. Client begins SSL handshake.
If you implement a server, you need to:
1. create a new {@link SslHandler} instance with {@code startTls} flag setto {@code true},
2. insert the {@link SslHandler} to the {@link ChannelPipeline}, and
3. write a StartTLS response.
Please note that you must insert {@link SslHandler} before sendingthe StartTLS response. Otherwise the client can send begin SSL handshake before {@link SslHandler} is inserted to the {@link ChannelPipeline}, causing data corruption.
The client-side implementation is much simpler.
1. Write a StartTLS request,
2. wait for the StartTLS response,
3. create a new {@link SslHandler} instance with {@code startTls} flag setto {@code false},
4. insert the {@link SslHandler} to the {@link ChannelPipeline}, and
5. Initiate SSL handshake by calling {@link SslHandler#handshake()}.
Known issues

Because of a known issue with the current implementation of the SslEngine that comes with Java it may be possible that you see blocked IO-Threads while a full GC is done.
So if you are affected you can workaround this problem by adjust the cache settings like shown below:
```
 SslContext context = ...; context.getServerSessionContext().setSessionCacheSize(someSaneSize); context.getServerSessionContext().setSessionTime(someSameTimeout); 
```
What values to use here depends on the nature of your application and should be set based on monitoring and debugging of it. For more details see #832 in our issue tracker. @apiviz.landmark @apiviz.uses com.facebook.presto.jdbc.internal.netty.handler.ssl.SslBufferPool


                SSLEngine sslEngine = SSLContext.getDefault().createSSLEngine(remoteAddress.getHostString(), remoteAddress.getPort());
                sslEngine.setSSLParameters(sslParameters);
                sslEngine.setUseClientMode(true);


                SslHandler sslHandler = new SslHandler(sslEngine);
                future.getChannel().getPipeline().addBefore("codec", "ssl", sslHandler);
                ChannelFuture handshakeFuture = sslHandler.handshake();
                handshakeFuture.addListener(callbackConnectionListener);
            }
            else {
                callbackConnectionListener.operationComplete(future);
            }

View Full Code Here

     */
    protected abstract SelectedProtocol getProtocol(SSLEngine engine);


    public void handleUpstream(ChannelHandlerContext ctx, ChannelEvent e) throws Exception {
        // Get the SslHandler from the ChannelPipeline so we can obtain the SslEngine from it.
        SslHandler handler = ctx.getPipeline().get(SslHandler.class);
        if (handler == null) {
            // SslHandler is needed by SPDY by design.
            throw new IllegalStateException("SslHandler is needed for SPDY");
        }


        ChannelPipeline pipeline = ctx.getPipeline();
        SelectedProtocol protocol = getProtocol(handler.getEngine());
        switch (protocol) {
        case None:
            // Not done with choosing the protocol, so just return here for now,
            return;
        case SpdyVersion2:

View Full Code Here

                        String[] enabledProtocols = config.getEnabledSslProtocols();
                        if (enabledProtocols != null) {
                            engine.setEnabledProtocols(enabledProtocols);
                        }


                        SslHandler sslHandler = new SslHandler(engine);
                        realChannel.getPipeline().addFirst("ssl", sslHandler);
                        sslHandshakeFuture = sslHandler.handshake();
                    }


                    // Send the HTTP request.
                    final HttpRequest req = new DefaultHttpRequest(
                            HttpVersion.HTTP_1_1, HttpMethod.POST, serverPath);

View Full Code Here

TOP

Related Classes of com.facebook.presto.jdbc.internal.netty.handler.ssl.SslHandler$PendingWrite

com.facebook.presto.jdbc.internal.airlift.http.client.netty.NettyConnectionPool$SslConnectionListener

com.facebook.presto.jdbc.internal.netty.buffer.ChannelBuffer

com.facebook.presto.jdbc.internal.netty.channel.Channel

com.facebook.presto.jdbc.internal.netty.channel.ChannelFuture

com.facebook.presto.jdbc.internal.netty.channel.ChannelFutureListener

com.facebook.presto.jdbc.internal.netty.channel.ChannelHandlerContext

com.facebook.presto.jdbc.internal.netty.channel.ChannelStateEvent

com.facebook.presto.jdbc.internal.netty.channel.DownstreamMessageEvent

com.facebook.presto.jdbc.internal.netty.channel.MessageEvent

com.facebook.presto.jdbc.internal.netty.channel.socket.http.HttpTunnelingClientSocketChannel

All source code are property of their respective owners. Java is a trademark of Sun Microsystems, Inc and owned by ORACLE Inc. Contact coftware#gmail.com.

Examples of com.facebook.presto.jdbc.internal.netty.handler.ssl.SslHandler$PendingWrite

Beginning the handshake

Handshake

Renegotiation

Closing the session

Restarting the session

Implementing StartTLS

Known issues

Related Classes of com.facebook.presto.jdbc.internal.netty.handler.ssl.SslHandler$PendingWrite