boringssl

Files

T

History

David Benjamin 8648c53690 Refer to RFCs consistently.

We were a mix of "RFC1234" and "RFC 1234". Apparently there is actually
an answer for this, which is with a space textually and without a space
in the citation/reference tag:
https://datatracker.ietf.org/doc/html/rfc7322#section-3.5

Change-Id: I0c44023163fe3a2a3ffe28cbc644d4c952dc8f1e
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/48965
Reviewed-by: Adam Langley <agl@google.com>

2021-08-20 16:36:15 +00:00

obj_dat.h

Add SHA-512-256.

2020-04-15 21:23:37 +00:00

obj_mac.num

Add SHA-512-256.

2020-04-15 21:23:37 +00:00

obj_test.cc

Make ASN1_OBJECT opaque.

2021-06-30 21:01:26 +00:00

obj_xref.c

Run the comment converter on libcrypto.

2017-08-18 21:49:04 +00:00

obj.c

Make ASN1_OBJECT opaque.

2021-06-30 21:01:26 +00:00

objects.go

Halve the size of the kNIDsIn* constants

2019-11-20 15:09:27 +00:00

objects.txt

Refer to RFCs consistently.

2021-08-20 16:36:15 +00:00

README

Reimplement objects.pl in Go.

2016-12-21 22:14:13 +00:00

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.