[
https://issues.apache.org/jira/browse/CASSANDRA-18624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17744108#comment-17744108
]
Michael Semb Wever commented on CASSANDRA-18624:
------------------------------------------------
bq. Should not we default to in-built crypto provider instead and forcing a
user to specifically enable this crypto provider if he is on x86?
For the first release cycle i'm inclined to this approach.
bq. Do we need to somehow differentiate or are we going to ship it for x86 only?
Please no.
Either we bundle with both arch deps, or neither.
We cannot hardcode the architecture in the dependency's classifier.
> Make Corretto Crypto Provider the Default
> -----------------------------------------
>
> Key: CASSANDRA-18624
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18624
> Project: Cassandra
> Issue Type: Improvement
> Components: Dependencies
> Reporter: Jordan West
> Assignee: Ayushi Singh
> Priority: Normal
> Attachments: image.png
>
> Time Spent: 8h 20m
> Remaining Estimate: 0h
>
> [Amazon Corretto Crypto Provider|
> https://github.com/corretto/amazon-corretto-crypto-provider] is an
> alternative provider of TLS and cryptographic functions that has significant
> performance benefits for Cassandra. It is Apache 2.0 licensed and has been
> deployed in several existing large fleets.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
