You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/docs/asciidoc/release_notes.adoc
+23Lines changed: 23 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -33,6 +33,17 @@ Changes per Jaybird 6 release.
33
33
See also <<whats-new-in-jaybird-6>>.
34
34
For known issues, consult <<known-issues>>.
35
35
36
+
=== Jaybird 6.0.6
37
+
38
+
The following was fixed or changed since Jaybird 6.0.6:
39
+
40
+
* Fixed: Legacy authentication fails with non-ASCII characters in password (https://github.com/FirebirdSQL/jaybird/issues/858[#858])
41
+
+
42
+
The hash that is sent instead of the actual password -- for authentication plugin `Legacy_Auth` or on Firebird 2.5 or older -- was incorrectly generated based on the `char` (UTF-16) value.
43
+
We now use UTF-8 bytes instead.
44
+
+
45
+
See also <<compat-legacy-auth>>.
46
+
36
47
=== Jaybird 6.0.5
37
48
38
49
The following was fixed or changed since Jaybird 6.0.4:
@@ -2357,3 +2368,15 @@ Be aware that this dependency does not support `embedded`.
2357
2368
For more information about this library, see https://github.com/mrotteveel/jaybird-fbclient[^].
2358
2369
2359
2370
In the future we may provide JARs with the embedded libraries of a specific Firebird version.
2371
+
2372
+
[#compat-legacy-auth]
2373
+
=== Legacy authentication in Jaybird 6.0.6 and higher
2374
+
2375
+
Since Jaybird 6.0.6 (and Jaybird 5.0.13), legacy authentication -- Firebird 2.5 or older, or using authentication plugin `Legacy_Auth` -- uses UTF-8 to derive the bytes for calculating the hash of the password to send to the server.
2376
+
It is possible UTF-8 is not the right character set on Firebird 2.5 and older.
2377
+
This possibly also applies for Firebird 3.0 and higher, if the password was set using connection encoding NONE on (Windows) systems where windows-1252 or similar is the default encoding.
2378
+
2379
+
You can use connection property `legacyAuthCharset` to specify a different Java character set name (for pure Java connections only).
2380
+
2381
+
If authentication against Firebird 2.5 or older starts to fail for you, then likely you need to specify `legacyAuthCharset=iso-8859-1`.
2382
+
Resetting your password, using https://firebirdsql.org/file/documentation/chunk/en/refdocs/fblangref25/fblangref25-security.html#fblangref25-security-auth-alter-user[`ALTER USER`] with connection encoding UTF8, might also resolve such failures.
0 commit comments