tree 3af8b84a347b59e4e115693031a8608fff8191c6
parent 91f3df0a20f6d3dd3e2f749b4a2730b68c3d585e
author David Benjamin <davidben@google.com> 1758906898 -0400
committer Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> 1759172056 -0700

Introduce cipher constants without the leading 0x03

It is confusing to always have to explain that our API believes
different notion of cipher suite ID than the IETF does. The only gap at
this point is that we don't have constants defined.

Define the constants for the cipher suites we implement, then deprecate
all the old stuff. Switch ourselves internally to only pass the 16-bit
IDs around, which avoids some confusing 0xffffs. The leading 0x03 can be
pasted on at the legacy SSL_CIPHER_get_id function.

The new constants were named to match the IANA names, minus the leading
TLS_. This means a few constants don't match their CK values in name.

There are TLS1_CK_ constants for a host of cipher suites we don't
implement. I've left them alone for now, but I think we can remove them
in a follow-up commit.

Change-Id: Ifeb9cdceb351610fab7633c4068a8729a64ff11b
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/82307
Auto-Submit: David Benjamin <davidben@google.com>
Reviewed-by: Lily Chen <chlily@google.com>
Commit-Queue: Lily Chen <chlily@google.com>