[
https://issues.apache.org/jira/browse/CASSANDRA-18434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17722230#comment-17722230
]
Brandon Williams commented on CASSANDRA-18434:
----------------------------------------------
Hi Sudeep, welcome and thanks for the patch!
Unfortunately, this isn't correct, there is no 'accepted_protocols' field,
there is only the 'protocol' field. The proposal at the end of [this
comment|https://issues.apache.org/jira/browse/CASSANDRA-13325?focusedCommentId=17205879&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17205879]
from Jon Meredith is what has been implemented and needs to be expounded on in
the yaml.
> yaml should explain behavior from CASSANDRA-13325
> -------------------------------------------------
>
> Key: CASSANDRA-18434
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18434
> Project: Cassandra
> Issue Type: Bug
> Components: Feature/Encryption
> Reporter: Brandon Williams
> Assignee: Sudeep Rao
> Priority: Normal
> Labels: lhf
> Fix For: 4.0.x, 4.1.x, 5.x
>
>
> After CASSANDRA-13325, it is possible in the yaml to set the 'protocol'
> option in a given encryption_options to the csv list of acceptable protocols,
> as we do in [this
> test|https://github.com/apache/cassandra-dtest/blob/trunk/cqlsh_tests/test_cqlsh.py#L185]
> to limit it to TLSv1.2. However, there is no way to know this from the yaml
> today, so some comments/example would be helpful.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
