[jira] [Resolved] (HADOOP-19152) Do not hard code security providers.
[ https://issues.apache.org/jira/browse/HADOOP-19152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz-wo Sze resolved HADOOP-19152. - Fix Version/s: 3.5.0 Hadoop Flags: Reviewed Release Note: Added a new conf "hadoop.security.crypto.jce.provider.auto-add" (default: true) to enable/disable auto-adding BouncyCastleProvider. This change also avoid statically loading the BouncyCastleProvider class. Resolution: Fixed The pull request is now merged. > Do not hard code security providers. > > > Key: HADOOP-19152 > URL: https://issues.apache.org/jira/browse/HADOOP-19152 > Project: Hadoop Common > Issue Type: Improvement > Components: security >Reporter: Tsz-wo Sze >Assignee: Tsz-wo Sze >Priority: Major > Labels: pull-request-available > Fix For: 3.5.0 > > > In order to support different security providers in different clusters, we > should not hard code a provider in our code. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-dev-h...@hadoop.apache.org
[jira] [Resolved] (HADOOP-19151) Support configurable SASL mechanism
[ https://issues.apache.org/jira/browse/HADOOP-19151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz-wo Sze resolved HADOOP-19151. - Fix Version/s: 3.5.0 Hadoop Flags: Reviewed Resolution: Fixed The pull request is now merged. > Support configurable SASL mechanism > --- > > Key: HADOOP-19151 > URL: https://issues.apache.org/jira/browse/HADOOP-19151 > Project: Hadoop Common > Issue Type: Improvement > Components: security >Reporter: Tsz-wo Sze >Assignee: Tsz-wo Sze >Priority: Major > Labels: pull-request-available > Fix For: 3.5.0 > > > Currently, the SASL mechanism is hard coded to DIGEST-MD5. As mentioned in > HADOOP-14811, DIGEST-MD5 is known to be insecure; see > [rfc6331|https://datatracker.ietf.org/doc/html/rfc6331]. > In this JIRA, we will make the SASL mechanism configurable. The default > mechanism will still be DIGEST-MD5 in order to maintain compatibility. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-dev-h...@hadoop.apache.org
[jira] [Created] (HADOOP-19152) Do not hard code security providers.
Tsz-wo Sze created HADOOP-19152: --- Summary: Do not hard code security providers. Key: HADOOP-19152 URL: https://issues.apache.org/jira/browse/HADOOP-19152 Project: Hadoop Common Issue Type: Improvement Components: security Reporter: Tsz-wo Sze Assignee: Tsz-wo Sze In order to support different security providers in different clusters, we should not hard code a provider in our code. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-dev-h...@hadoop.apache.org
[jira] [Created] (HADOOP-19151) Support configurable SASL mechanism
Tsz-wo Sze created HADOOP-19151: --- Summary: Support configurable SASL mechanism Key: HADOOP-19151 URL: https://issues.apache.org/jira/browse/HADOOP-19151 Project: Hadoop Common Issue Type: Improvement Components: security Reporter: Tsz-wo Sze Assignee: Tsz-wo Sze Currently, the SASL mechanism is hard coded to DIGEST-MD5. As mentioned in HADOOP-14811, DIGEST-MD5 is known to be insecure; see [rfc6331|https://datatracker.ietf.org/doc/html/rfc6331]. In this JIRA, we will make the SASL mechanism configurable. The default mechanism will still be DIGEST-MD5 in order to maintain compatibility. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-dev-h...@hadoop.apache.org
[jira] [Created] (HADOOP-19035) CrcUtil/CrcComposer should not throw IOException for non-IO
Tsz-wo Sze created HADOOP-19035: --- Summary: CrcUtil/CrcComposer should not throw IOException for non-IO Key: HADOOP-19035 URL: https://issues.apache.org/jira/browse/HADOOP-19035 Project: Hadoop Common Issue Type: Improvement Components: util Reporter: Tsz-wo Sze Assignee: Tsz-wo Sze CrcUtil and CrcComposer should throw specific exceptions for non-IO cases - IllegalArgumentException: invalid arguments - ArrayIndexOutOfBoundsException: index exceeds array size - IllegalStateException: unexpected computation state -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-dev-h...@hadoop.apache.org
[jira] [Created] (HADOOP-19012) Use CRC tables to improve galoisFieldMultiply in CrcUtil
Tsz-wo Sze created HADOOP-19012: --- Summary: Use CRC tables to improve galoisFieldMultiply in CrcUtil Key: HADOOP-19012 URL: https://issues.apache.org/jira/browse/HADOOP-19012 Project: Hadoop Common Issue Type: Improvement Components: util Reporter: Tsz-wo Sze CrcUtil.galoisFieldMultiply(p, q, m) supports multiplying two polynomials p, q modulo any modulus polynomial m over GF(2). Since the method is used for CRC calculations, the modulus polynomial m is restricted to either the GZIP_POLYNOMIAL or the CASTAGNOLI_POLYNOMIAL. We may use CRC tables in PureJavaCrc32/PureJavaCrc32C to speed up the computation. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-dev-h...@hadoop.apache.org
[jira] [Created] (HADOOP-17595) Add ApacheCon Event Banner to website
Tsz-wo Sze created HADOOP-17595: --- Summary: Add ApacheCon Event Banner to website Key: HADOOP-17595 URL: https://issues.apache.org/jira/browse/HADOOP-17595 Project: Hadoop Common Issue Type: Task Components: website Reporter: Tsz-wo Sze -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-dev-h...@hadoop.apache.org
[jira] [Created] (HADOOP-16868) ipc.Server readAndProcess threw NullPointerException
Tsz-wo Sze created HADOOP-16868:
---
Summary: ipc.Server readAndProcess threw NullPointerException
Key: HADOOP-16868
URL: https://issues.apache.org/jira/browse/HADOOP-16868
Project: Hadoop Common
Issue Type: Bug
Components: rpc-server
Reporter: Tsz-wo Sze
{code}
2020-01-18 10:19:02,109 INFO org.apache.hadoop.ipc.Server: Socket Reader #1 for
port 8020: readAndProcess from client xx.xx.xx.xx threw exception
[java.lang.NullPointerException]
java.lang.NullPointerException
at
org.apache.hadoop.ipc.Server$Connection.readAndProcess(Server.java:1676)
at org.apache.hadoop.ipc.Server$Listener.doRead(Server.java:935)
at
org.apache.hadoop.ipc.Server$Listener$Reader.doRunLoop(Server.java:791)
at org.apache.hadoop.ipc.Server$Listener$Reader.run(Server.java:762)
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-dev-h...@hadoop.apache.org
