crypto/tls: expose implemented cipher suites #30739
Conversation
…y to avoid accidental manipulation) - Added function to query cipher by ID if available (returning a copy to avoid accidental manipulation) - Added function to query cipher by Name if available (returning a copy to avoid accidental manipulation) - Exposed some cipher flags
|
We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google. ℹ️ Googlers: Go here for more info. |
googlebot
added
the
cla: no
|
The CLA hasn't been signed in over a month, and the patch now has conflicts; closing for now. If both are solved, feel free to reopen or post a new PR. |
3 participants
Allows to dynamically retrieve a list of available cipher suites. This change allows a variety of applicatoins:
Ciphers are returned as copies, in order to avoid messing up internal stuff.
In contrast to the already discussed solutions, this one reduced the amount of necessary changes. Maintainability will be equal to before. This should not contain any breaking changes, as it only makes former private variables public, respectively, adds functions.
Fixes #30325 and #21167