On 11-08-2020 21:24, Adam McMahon wrote:
> I am using 1.8.0_131 on windows. There is no log file in my firebird
> directory (which seems very odd). My install folder is simply
> Firebird_3_0.
I am pretty certain that the problem is that you don't have the
unlimited strength cryptography jurisdiction policy in your Java
installation, which causes Jaybird not being able to initialize
encryption (which is also the cause for the exception you initially had).
I would recommend updating to a more recent Java 8 version (current
latest is Java 8 update 262), as since Java 8 update 161 the unlimited
strength cryptography jurisdiction policy is enabled by default.
For Java 8 update 131, see
https://stackoverflow.com/questions/3862800/invalidkeyexception-illegal-key-size/3864276#3864276
how to enable this. However, I see that the necessary policy file can no
longer be downloaded from the Oracle site. When upgrading to a more
recent version, keep in mind that the license changed of Oracle Java
(after update 202 if I'm not mistaken), so you might want to consider
switching to AdoptOpenJDK instead)
Alternatively, disable wire crypt in firebird.conf by setting WireCrypt
= Disabled and restart the server.
See also
https://www.firebirdsql.org/file/documentation/drivers_documentation/java/faq.html#encryption-key-did-not-meet-algorithm-requirements-of-symmetricarc4-337248282
I do see some things in the way Jaybird creates these exceptions and the
logging that make this harder to diagnose than necessary.
Mark
--
Mark Rotteveel