[
https://issues.apache.org/jira/browse/HADOOP-19962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Siyao Meng updated HADOOP-19962:
--------------------------------
Release Note:
MachineList now accepts IPv6 CIDR entries (for example 2001:db8::/32) in
hadoop.proxyuser.$superuser.hosts, in the hosts and hosts.blocked lists of
service level authorization and in FileBasedIPList files. IPv4 entries behave
as before.
Behavior change: an IPv6 client checked against a list that contains an IPv4
CIDR entry used to fail with an IllegalArgumentException, which dropped the RPC
connection. It is now evaluated normally and never matches an IPv4 range. If a
blocked host list contains only IPv4 ranges, add the IPv6 ranges that should
also be blocked.
> Support IPv6 CIDR rules in MachineList
> --------------------------------------
>
> Key: HADOOP-19962
> URL: https://issues.apache.org/jira/browse/HADOOP-19962
> Project: Hadoop Common
> Issue Type: Sub-task
> Reporter: Siyao Meng
> Assignee: Siyao Meng
> Priority: Major
> Labels: pull-request-available
>
> MachineList uses the IPv4-only SubnetUtils class. IPv6 CIDR rules therefore
> fail in address-based security policies. Add family-aware prefix matching for
> IPv4 and IPv6. Preserve existing IPv4 behavior. Reject invalid prefixes and
> addresses from the wrong family.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
