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
+26Lines changed: 26 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -35,6 +35,20 @@ For known issues, consult <<known-issues>>.
35
35
Future maintenance releases of Jaybird 5 may stop expanding Java support to include newly released Java versions.
36
36
If you use Java 17 or higher, we recommend upgrading to https://firebirdsql.org/en/jdbc-driver/#jaybird6[Jaybird 6].
37
37
38
+
[#jaybird-5-0-13-changelog]
39
+
=== Jaybird 5.0.13
40
+
41
+
The following has been changed or fixed since Jaybird 5.0.12:
42
+
43
+
* Fixed: Legacy authentication fails with non-ASCII characters in password (https://github.com/FirebirdSQL/jaybird/issues/931[#931])
44
+
+
45
+
This fix was backported from Jaybird 6.0.6.
46
+
+
47
+
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.
48
+
We now use UTF-8 bytes instead.
49
+
+
50
+
See also <<compat-legacy-auth>>.
51
+
38
52
[#jaybird-5-0-12-changelog]
39
53
=== Jaybird 5.0.12
40
54
@@ -1859,3 +1873,15 @@ For more information about this library, see https://github.com/mrotteveel/jaybi
1859
1873
1860
1874
In Jaybird 6 we will move the Type 2 support to a separate library.
1861
1875
In the future we may provide JARs with the embedded libraries of a specific Firebird version.
1876
+
1877
+
[#compat-legacy-auth]
1878
+
=== Legacy authentication in Jaybird 6.0.6 and higher
1879
+
1880
+
Since Jaybird 5.0.13 (and Jaybird 6.0.6), 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.
1881
+
It is possible UTF-8 is not the right character set on Firebird 2.5 and older.
1882
+
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.
1883
+
1884
+
You can use connection property `legacyAuthCharset` to specify a different Java character set name (for pure Java connections only).
1885
+
1886
+
If authentication against Firebird 2.5 or older starts to fail for you, then likely you need to specify `legacyAuthCharset=iso-8859-1`.
1887
+
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