You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@spark.apache.org by "Sean R. Owen (Jira)" <ji...@apache.org> on 2023/03/28 03:49:00 UTC

[jira] [Updated] (SPARK-42922) Use SecureRandom, instead of Random in security sensitive contexts

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

Sean R. Owen updated SPARK-42922:
---------------------------------
    Priority: Minor  (was: Major)

> Use SecureRandom, instead of Random in security sensitive contexts
> ------------------------------------------------------------------
>
>                 Key: SPARK-42922
>                 URL: https://issues.apache.org/jira/browse/SPARK-42922
>             Project: Spark
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 3.2.3, 3.3.2, 3.4.0, 3.5.0
>            Reporter: Mridul Muralidharan
>            Priority: Minor
>
> Most uses of Random in spark are either in test cases or where we need a pseudo random number which is repeatable.
> The following are usages where moving from Random to SecureRandom would be useful
> a) HttpAuthUtils.createCookieToken
> b) ThriftHttpServlet.RAN



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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