Skip to content

feat(hash): remove OpenSSL-backed algorithms - #588

Draft
kssim wants to merge 1 commit into
eclipse-score:mainfrom
autocrypt-dot-io:feat/remove-crypto-hashes
Draft

kssim wants to merge 1 commit into
eclipse-score:mainfrom
autocrypt-dot-io:feat/remove-crypto-hashes

Conversation

@kssim

@kssim kssim commented Sep 16, 2026

Copy link
Copy Markdown

Remove SHA-1, SHA-384, and SHA-512 support together with the Baselibs OpenSSL integration. Keep native SHA-256 and CRC-32 for existing safety-integrity consumers, and update tests, build metadata, requirements, and design documentation.

Refs: eclipse-score/inc_security_crypto#125

@github-project-automation github-project-automation Bot moved this to In Progress in BAS - Baselibs FT Sep 16, 2026
@kssim kssim self-assigned this Sep 16, 2026
@github-actions github-actions Bot added documentation Improvements or additions to documentation comp-hash Related to score/hash component c++ C++ code bazel Bazel and Starlark build files labels Sep 16, 2026
@github-actions

Copy link
Copy Markdown
Contributor

Documentation preview for this pull request is available at:
pr-588: https://eclipse-score.github.io/baselibs/pr-588/

Remove SHA-1, SHA-384, and SHA-512 support together with the Baselibs OpenSSL integration. Keep native SHA-256 and CRC-32 for existing safety-integrity consumers, and update tests, build metadata, requirements, and design documentation.

Refs: eclipse-score/inc_security_crypto#125
@kssim
kssim force-pushed the feat/remove-crypto-hashes branch from 0dc2b0f to 148057e Compare September 16, 2026 01:30
@kssim
kssim deployed to workflow-approval September 16, 2026 01:30 — with GitHub Actions Active
@kssim
kssim deployed to workflow-approval September 16, 2026 01:30 — with GitHub Actions Active
@kssim
kssim deployed to workflow-approval September 16, 2026 01:30 — with GitHub Actions Active
@kssim
kssim deployed to workflow-approval September 16, 2026 01:30 — with GitHub Actions Active
@4og

4og commented Sep 16, 2026

Copy link
Copy Markdown
Member

@michaelsaborov, @eclipse-impl, can you please have a look because the ConfigManagement is the user of the hash lib? I have a feeling it's premature to delete this, or am I wrong?

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

Labels

bazel Bazel and Starlark build files c++ C++ code comp-hash Related to score/hash component documentation Improvements or additions to documentation

Projects

Status: In Progress

Development

Successfully merging this pull request may close these issues.

2 participants