RFE: Introduce new test for expected crypto algorithms in a Temurin runtime
- Dominant language
- HTML
- Stars
- 155
- Forks
- 346
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 36
Description
We’ve received a couple of user reports for unexpected sets of crypto algorithms in the Alpine 8u Temurin build (see [temurin-build#3002](https://github.com/adoptium/temurin-build/issues/3002) and the referenced [temurin-build#2963](https://github.com/adoptium/temurin-build/issues/2963)).
In a discussion at the PMC we thought it would potentially be good candidate for a new test for the expected set.
Contributor guide
Research direction
Start by reading temurin-build#3002 and temurin-build#2963, then review the referenced PMC discussion to determine the expected crypto-algorithm set for the Alpine 8u Temurin build. The work is done when a new test checks that runtime algorithms match that expected set and exposes unexpected results.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- security, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100