Closed ChristopherSchultz closed 7 months ago
Note a couple of alternative attribute names were suggested in #130. I'm happy with this particular name but could live with either of the alternatives. If there are no objections, I intend to merge this in a week or so for inclusion in 6.1.
I ultimately chose secure_protocol
for several reasons:
ssl_protocol
is just wrong, since SSL is no longer usedtls_protocol
may be wrong in the future, once we switch to TBDtls_protocol
may also be wrong for some other protocol, say, sftp or whatevercipher_suite
nor key_size
have any ssl_
prefix as ssl_session_id
doesprotocol
without a prefix would be confusing with respect to HTTP/1.1, etc.; this is intended to be the security protocol in use for the requestTx for the PR. I'll follow-up shortly with a PR to add an entry to the change log etc.
This fixes #130