Interoperability checks for OID values #78

Open
opened 2019-03-04 11:50:21 -06:00 by gilles-peskine-arm · 2 comments
gilles-peskine-arm commented 2019-03-04 11:50:21 -06:00 (Migrated from github.com)

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
### 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 <!-- Required Please add only one X to one of the following types. Do not fill multiple types (split the issue otherwise.) Please note this is not a GitHub task list, indenting the boxes or changing the format to add a '.' or '*' in front of them would change the meaning incorrectly. The only changes to be made are to add a description text under the description heading and to add a 'x' to the correct box. --> [ ] Question [x] Enhancement [ ] Bug
ciarmcom commented 2019-03-06 15:40:20 -06:00 (Migrated from github.com)

Internal Jira reference: https://jira.arm.com/browse/IOTCRYPT-718

*Internal Jira reference: https://jira.arm.com/browse/IOTCRYPT-718*
adbridge commented 2019-11-04 06:47:17 -06:00 (Migrated from github.com)

Apologies, this was closed in error by the automated bot - re-opening.

Apologies, this was closed in error by the automated bot - re-opening.
Sign in to join this conversation.
No milestone
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
gh-ARMmbed/mbed-crypto#78
No description provided.