Add a way to get specific s2n errors
Open
Nobody has claimed this yet.
priority/low
size/medium
type/debug
type/usability
- Dominant language
- C
- Stars
- 4.8k
- Forks
- 803
- Avg merge
- 5d 22h
- Merged PRs (30d)
- 33
Description
Problem:
Currently, we have an API to get error type (s2n_error_get_type), but there isn't a good way to identify the specific s2n_error.
Proposed Solution:
Expose s2n_error
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 with the existing s2n_error_get_type API and the proposed solution in this issue. Determine how a caller should identify a specific s2n_error, then verify that the exposed interface distinguishes individual errors while preserving the existing error-type behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- cryptography, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100