47b8f00fdc
OBJ_txt2obj is currently implemented using BIGNUMs which is absurd. It also depends on the giant OID table, which is undesirable. Write a new one and expose the low-level function so Chromium can use it without the OID table. Bug: chromium:706445 Change-Id: I61ff750a914194f8776cb8d81ba5d3eb5eaa3c3d Reviewed-on: https://boringssl-review.googlesource.com/23364 Commit-Queue: David Benjamin <davidben@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> Reviewed-by: Steven Valdez <svaldez@google.com> |
||
---|---|---|
.. | ||
CMakeLists.txt | ||
obj_dat.h | ||
obj_mac.num | ||
obj_test.cc | ||
obj_xref.c | ||
obj.c | ||
objects.go | ||
objects.txt | ||
README |
The files nid.h, obj_mac.num, and obj_dat.h are generated from objects.txt and obj_mac.num. To regenerate them, run: go run objects.go objects.txt contains the list of all built-in OIDs. It is processed by objects.go to output obj_mac.num, obj_dat.h, and nid.h. obj_mac.num is the list of NID values for each OID. This is an input/output file so NID values are stable across regenerations. nid.h is the header which defines macros for all the built-in OIDs in C. obj_dat.h contains the ASN1_OBJECTs corresponding to built-in OIDs themselves along with lookup tables for search by short name, OID, etc.