[jira] [Resolved] (SPARK-36915) Pin actions to a full length commit SHA

["Sean R. Owen (Jira)" <ji...@apache.org>]

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

Sean R. Owen resolved SPARK-36915.
----------------------------------
    Fix Version/s: 3.3.0
       Resolution: Fixed

Issue resolved by pull request 34163
[https://github.com/apache/spark/pull/34163]

> Pin actions to a full length commit SHA
> ---------------------------------------
>
>                 Key: SPARK-36915
>                 URL: https://issues.apache.org/jira/browse/SPARK-36915
>             Project: Spark
>          Issue Type: Bug
>          Components: Project Infra
>    Affects Versions: 3.1.2
>            Reporter: Naveen S
>            Assignee: Naveen S
>            Priority: Major
>             Fix For: 3.3.0
>
>
> Pinning an action to a full-length commit SHA is currently the only way to use an action as
> an immutable release. Pinning to a particular SHA helps mitigate the risk of a bad actor adding a
> backdoor to the action's repository, as they would need to generate a SHA-1 collision for
> a valid Git object payload.
> [https://docs.github.com/en/actions/security-guides/security-hardening-for-github-actions#using-third-party-actions]
> [https://github.com/ossf/scorecard/blob/main/docs/checks.md#pinned-dependencies]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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