PLEASE REMOVE ME FROM THIS EMAIL!!!!
From: "C. Scott Andreas" <sc...@paradoxica.net> Reply-To: "dev@cassandra.apache.org" <dev@cassandra.apache.org> Date: Wednesday, July 26, 2023 at 6:19 AM To: "dev@cassandra.apache.org" <dev@cassandra.apache.org> Subject: Re: [DISCUSS] Using ACCP or tc-native by default Jeremiah, that’s my understanding as well. ACCP accelerates a subset of functions and delegates the rest. In years of using ACCP with Cassandra, I have yet to see an issue - or any case in which adopting ACCP was anything other than a strict benefit. - Scott On Jul 26, 2023, at 5:33 AM, J. D. Jordan <jeremiah.jor...@gmail.com> wrote: I thought the crypto providers were supposed to “ask the next one down the line” if something is not supported? Have you tried some unsupported thing and seen it break? My understanding of the providers being an ordered list was that isn’t supposed to happen. -Jeremiah On Jul 26, 2023, at 3:23 AM, Mick Semb Wever <m...@apache.org> wrote: That means that if somebody is on 4.0 and they upgrade to 5.0, if they use some ciphers / protocols / algorithms which are not in Corretto, it might break their upgrade. If there's any risk of breaking upgrades we have to go with (2). We support a variation of JCE configurations, and I don't see we have the test coverage in place to de-risk it other than going with (2). Once the yaml configuration is in place we can then change the default in the next major version 6.0.
