GitHub user EronWright opened a pull request:

    https://github.com/apache/flink/pull/3061

    [FLINK-5030] Support hostname verification

    Fixes FLINK-5030
    
    - updated SSL documentation
    - use canonical hostname for (netty/blob) client-to-server connections
    - ensure that a valid address is advertised for webui (not the bind
    address which might be 0.0.0.0)
    - improved configuration validation for keystore/truststore
    - advertise the FQDN of the AppMaster to Mesos
    - improved handling of SSL exceptions due to handshake failure
    - incorporate recent changes to JM address configuration
    - fix client to accurately report https


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/EronWright/flink feature-FLINK-5030-new-rebase

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/flink/pull/3061.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #3061
    
----
commit 52f41fdb7d65638e3179fd4c887ba102fb3596bf
Author: wrighe3 <[email protected]>
Date:   2016-12-17T02:05:38Z

    [FLINK-5030] Support hostname verification
    
    - updated SSL documentation
    - use canonical hostname for (netty/blob) client-to-server connections
    - ensure that a valid address is advertised for webui (not the bind
    address which might be 0.0.0.0)
    - improved configuration validation for keystore/truststore
    - advertise the FQDN of the AppMaster to Mesos
    - improved handling of SSL exceptions due to handshake failure
    - incorporate recent changes to JM address configuration
    - fix client to accurately report https

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to