[
https://issues.apache.org/jira/browse/CASSANDRA-18624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17745308#comment-17745308
]
Stefan Miklosovic commented on CASSANDRA-18624:
-----------------------------------------------
[~ayushi29as] I took your branch, removed the last commit (I am sorry for the
noise) and put one commit on top of that where I put various minor
improvements, mostly logging related etc.
Based on the ML thread, it seems like we might eventually use Corretto as
default. The patch does not include a flag for failing the startup when the
crypto provider is not properly installed / heathchecked. Feel free to take the
branch below and implement that. It is all your work after all, I do not want
to hijack anything. However please be aware that the freez window for 5.0 is
getting closer day by day and we should better hurry up a bit with this.
https://github.com/apache/cassandra/pull/2505/commits
> 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: 10h
> 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: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
