flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eron Wright (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (FLINK-5030) Support hostname verification
Date Thu, 10 May 2018 00:25:00 GMT

     [ https://issues.apache.org/jira/browse/FLINK-5030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Eron Wright  resolved FLINK-5030.
---------------------------------
    Resolution: Won't Fix

I think this is obsolete and/or covered by FLINK-9103

> 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 
>            Priority: Major
>
> _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
(v7.6.3#76005)

Mime
View raw message