Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Date: Tue, 17 Jun 2014 05:13:02 +0000 (UTC)
From: "Andrew Wang (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: <JIRA.12721587.1402981229106.143789.1402981982443@arcas>
In-Reply-To: <JIRA.12721587.1402981229106@arcas>
References: <JIRA.12721587.1402981229106@arcas>
Subject: [jira] [Updated] (HADOOP-10713) Document thread-safety of
 CryptoCodec#generateSecureRandom
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Andrew Wang updated HADOOP-10713:
---------------------------------

    Attachment: HADOOP-10713.001.patch

Trivial patch attached. While I was looking at this, I also wondered whether this API should be like {{SecureRandom#nextBytes(byte[])}}, taking a {{byte[]}}, rather than taking an int numBytes and returning a new array. [~hitliuyi] any thoughts? It might save us some allocations.

> Document thread-safety of CryptoCodec#generateSecureRandom
> ----------------------------------------------------------
>
>                 Key: HADOOP-10713
>                 URL: https://issues.apache.org/jira/browse/HADOOP-10713
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: security
>    Affects Versions: fs-encryption (HADOOP-10150 and HDFS-6134)
>            Reporter: Andrew Wang
>            Assignee: Andrew Wang
>            Priority: Trivial
>             Fix For: 3.0.0
>
>         Attachments: HADOOP-10713.001.patch
>
>
> Random implementations have to deal with thread-safety; this should be specified in the javadoc so implementors know to do this for CryptoCodec subclasses.


--
This message was sent by Atlassian JIRA
(v6.2#6252)