Contribute back SPECS/ntp/Get-rid-of-EVP_MD_CTX_FLAG_NON_FIPS_ALLOW.patch to upstream NTP project?
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 3.2k
- Forks
- 692
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
The patch posted in SPECS/ntp/Get-rid-of-EVP_MD_CTX_FLAG_NON_FIPS_ALLOW.patch could/should be contributed upstream to the NTP project (it would benefit multiple downstream projects like FreeBSD, multiple flavors of Linux, etc).
I would love to contribute it back on behalf of this project, but I don't know what license the patch was released under and so (for legal reasons), I don't feel comfortable putting myself on the line to contribute back the change.
Reproduction steps
N/A
Expected behavior
N/A
Additional context
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing SPECS/ntp/Get-rid-of-EVP_MD_CTX_FLAG_NON_FIPS_ALLOW.patch and the surrounding NTP packaging context, then check the patch’s licensing and provenance. Done means determining whether the change can be contributed to the upstream NTP project and documenting or completing the contribution path without unresolved licensing concerns.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- operating-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100