[
https://issues.apache.org/jira/browse/FLINK-9312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16467571#comment-16467571
]
ASF GitHub Bot commented on FLINK-9312:
---------------------------------------
Github user sihuazhou commented on a diff in the pull request:
https://github.com/apache/flink/pull/5966#discussion_r186769177
--- Diff:
flink-runtime/src/main/java/org/apache/flink/runtime/io/network/netty/NettyServer.java
---
@@ -170,8 +171,8 @@ public void initChannel(SocketChannel channel) throws
Exception {
localAddress = (InetSocketAddress)
bindFuture.channel().localAddress();
- long end = System.currentTimeMillis();
- LOG.info("Successful initialization (took {} ms). Listening on
SocketAddress {}.", (end - start),
bindFuture.channel().localAddress().toString());
+ final long duration = (start - System.nanoTime()) / 1_000_000;
+ LOG.info("Successful initialization (took {} ms). Listening on
SocketAddress {}.", duration, localAddress);
--- End diff --
Is this should be `final long duration = (System.nanoTime() - start) /
1_000_000;`
> Perform mutual authentication during SSL handshakes
> ---------------------------------------------------
>
> Key: FLINK-9312
> URL: https://issues.apache.org/jira/browse/FLINK-9312
> Project: Flink
> Issue Type: New Feature
> Components: Security
> Reporter: Stephan Ewen
> Priority: Major
> Fix For: 1.6.0
>
>
> Currently, the Flink processes encrypted connections via SSL:
> - Data exchange TM - TM
> - RPC JM - TM
> - Blob Service JM - TM
> However, the server side always accepts any client to build up the
> connection, meaning the connections are not strongly authenticated.
> Activating SSL mutual authentication solves that - only processes that have
> the same certificate can connect.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
