You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "Alex Rodoni (JIRA)" <ji...@apache.org> on 2018/06/18 23:09:00 UTC

[jira] [Updated] (IMPALA-7182) Impala does not allow the use of insecure clusters with public IPs by default

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

Alex Rodoni updated IMPALA-7182:
--------------------------------
    Issue Type: Task  (was: Documentation)

> Impala does not allow the use of insecure clusters with public IPs by default
> -----------------------------------------------------------------------------
>
>                 Key: IMPALA-7182
>                 URL: https://issues.apache.org/jira/browse/IMPALA-7182
>             Project: IMPALA
>          Issue Type: Task
>          Components: Security
>    Affects Versions: Impala 2.12.0
>            Reporter: Sailesh Mukil
>            Assignee: Alex Rodoni
>            Priority: Critical
>              Labels: docs, security
>
> We made Impala more secure by using KRPC which doesn't allow the usage of insecure clusters (no auth or no encryption) with public IPs by default.
> We have a workaround which is to add the subnet to this flag 'trusted_subnets':
> https://github.com/apache/impala/blob/master/be/src/kudu/rpc/server_negotiation.cc#L70-L80
> Although we don't expect users to run production environments with this configuration, we need to document this as it's a slight behavioral change from Impala 2.11 to Impala 2.12.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org