[jira] [Commented] (FLINK-5030) Support hostname verification

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/FLINK-5030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16187673#comment-16187673 ] 

ASF GitHub Bot commented on FLINK-5030:
---------------------------------------

Github user VanessaHenderson commented on the issue:

    https://github.com/apache/flink/pull/3061
  
    @EronWright which PR was it closed in favor of? As far as I can see on Master StandaloneClientCluster is still using the non-canonical hostname?


> Support hostname verification
> -----------------------------
>
>                 Key: FLINK-5030
>                 URL: https://issues.apache.org/jira/browse/FLINK-5030
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Security
>            Reporter: Eron Wright 
>            Assignee: Eron Wright 
>             Fix For: 1.2.2
>
>
> _See [Dangerous Code|http://www.cs.utexas.edu/~shmat/shmat_ccs12.pdf] and [further commentary|https://tersesystems.com/2014/03/23/fixing-hostname-verification/] for useful background._
> When hostname verification is performed, it should use the hostname (not IP address) to match the certificate.   The current code is wrongly using the address.
> In technical terms, ensure that calls to `SSLContext::createSSLEngine` supply the expected hostname, not host address.
> Please audit all SSL setup code as to whether hostname verification is enabled, and file follow-ups where necessary.   For example, Akka 2.4 supports it but 2.3 doesn't ([ref|http://doc.akka.io/docs/akka/2.4.4/scala/http/client-side/https-support.html#Hostname_verification]).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)