Skip to content

Issue 1314: Clarify the security implications and recommended usage of entries in the HashAlgorithm vocabulary - #1474

Open
henrylyons wants to merge 3 commits into
spdx:developfrom
henrylyons:issue-1314-hash-guidance
Open

henrylyons wants to merge 3 commits into
spdx:developfrom
henrylyons:issue-1314-hash-guidance

Conversation

@henrylyons

Copy link
Copy Markdown
Contributor

Summary

Clarifies the security implications and recommended usage of entries in the HashAlgorithm vocabulary (#1314).

Changes

  • Recommend SHA-256 or stronger for cryptographic integrity verification.
  • Clarify that MD2, MD4, MD5, and SHA-1 are not collision resistant.
  • Identify Adler-32 as a non-cryptographic checksum.
  • Describe MD6 as experimental and non-standardized.
  • Deprecate the Dilithium, Kyber, and FALCON entries because they are not hash algorithms.
  • Correct the SHA-1 description so it no longer characterizes SHA-1 as secure.

@bact bact added the Profile:Security Security profile and related matters label Oct 7, 2026
@bact bact modified the milestones: 3.1-rc2, 3.1 Oct 7, 2026

@goneall goneall left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Discussed on the 3 November, 2026 tech call - We decided not to provide specific advice for usage of hash or cryptographic algorithms in the spec itself - it should be provided in the using guidance in the using repo.

@JPEWdev

JPEWdev commented Nov 10, 2026

Copy link
Copy Markdown
Contributor

Fixes #1459

@henrylyons
henrylyons force-pushed the issue-1314-hash-guidance branch from 1dbe028 to 9bc0bd8 Compare November 12, 2026 00:36
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
@goneall
goneall requested review from bact and zvr November 17, 2026 01:52

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Profile:Security Security profile and related matters

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants