095b6c9baa
We need it in both directions. Also I missed that in OBJ_obj2txt we allowed uint64_t components, but in my new OBJ_txt2obj we only allowed uint32_t. For consistency, upgrade that to uint64_t. Bug: chromium:706445 Change-Id: I38cfeea8ff64b9acf7998e552727c6c3b2cc600f Reviewed-on: https://boringssl-review.googlesource.com/23544 Commit-Queue: Steven Valdez <svaldez@google.com> Reviewed-by: Steven Valdez <svaldez@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> |
||
|---|---|---|
| .. | ||
| 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.