Interoperability checks for OID values
- Dominant language
- C
- Stars
- 108
- Forks
- 95
- PR merge metrics
- No merged PRs in 30d
Description
### Description
The OID module defines many OIDs. Mbed TLS tests that it has the correct values indirectly by using parsing those values in X.509 test data and by making TLS connections. With the split of Mbed Crypto and Mbed TLS, there's nothing to verify that we have the correct values for all the OID constants in Mbed Crypto itself. We should add some verification mechanism, e.g. asking some other library to parse our OIDs or checking the value against some online database.
Related: #77 — test the OID functions.
### Issue request type
[ ] Question
[x] Enhancement
[ ] Bug
Contributor guide
Research direction
Start by reading the OID module and the existing indirect checks through X.509 test data and TLS connections, then review related issue #77. Choose a verification mechanism such as another library or an online database, and consider all OID constants covered. Done means the values in Mbed Crypto are independently checked.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- cryptography
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100