There was a similar, but not identical, discussion around these topics
four years ago, when the code was changed to remove SSLv3 and SSLv2
support. See DERBY-6764 for the full details.
I think it would certainly be possible to change the code in a similar way
to allow more configurability, but I
Greetings, Apache software enthusiasts!
(You’re getting this because you’re on one or more dev@ or users@ lists
for some Apache Software Foundation project.)
ApacheCon North America, in Montreal, is now just 80 days away, and
early bird prices end in just two weeks - on July 21. Prices will
Hello,
I cannot find a way to force the server to just use TLSv1.2. Currently
it says:
Apache Derby Network Server - 10.13.1.1 - (1765088) Enabled Protocols
are TLSv1, TLSv1.1, TLSv1.2
even when using
-Dhttps.protocols=TLSv1.2
or similar settings found on the internet. Then I saw in the
Yes, this is a known result of DERBY-6987. The default security
policy file for Derby no longer allows unlimited access to your
computer's local filesystem.
Please see these resource for how to adjust your security settings to
explicitly authorize loading your jar into Derby:
