Skip to content

Match signer chosing to algorithm registry - #1027

Merged
aaronlew02 merged 1 commit into
mainfrom
addsigningalgotosigner
Jul 22, 2025
Merged

Match signer chosing to algorithm registry#1027
aaronlew02 merged 1 commit into
mainfrom
addsigningalgotosigner

Conversation

@loosebazooka

Copy link
Copy Markdown
Member

Summary

Start integrating algorithm registry into sigstore-java.

KeylessSigner.signer(any impl) is now replaced with KeylessSigner.singer(AlgorithmRegistry.SigningAlgorithm)

No changes were made to how verification parses and operates on keys

Sigstore java still requires sha256 as the hashing algorithm across operations.

Release Note

Documentation

- Don't allow any arbitrary signer implementation
- Have the user select from a curated list
- We still only support sha256 for now
- Verification is unchanged for now in that we
  will parse the key instead of reading key details

Signed-off-by: Appu Goundan <appu@google.com>
@loosebazooka
loosebazooka requested a review from aaronlew02 July 22, 2025 15:10
@loosebazooka
loosebazooka marked this pull request as ready for review July 22, 2025 15:10
@aaronlew02
aaronlew02 merged commit 58a034f into main Jul 22, 2025
20 checks passed
@aaronlew02
aaronlew02 deleted the addsigningalgotosigner branch July 22, 2025 15:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants