JDK-8200152 : KerberosString should use UTF-8 by default
- Type: Bug
- Component: security-libs
- Sub-Component: org.ietf.jgss:krb5
- Priority: P3
- Status: Closed
- Resolution: Fixed
- Submitted: 2018-03-23
- Updated: 2018-06-27
- Resolved: 2018-04-10
The Version table provides details related to the release that this issue/RFE will be addressed.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
| JDK 11 |
|---|
11 b09Fixed  |
Related Reports
|
CSR :
|
|
|
Relates :
|
Sub Tasks
|
JDK-8201351 :
|
Description
In earlier version of Java kerberos, KerberosString was treated as pure ASCII and stored and loaded as a GeneralString. In JDK-6862679, we realized Windows is using UTF-8. A system property (sun.security.krb5.msinterop.kstring) was added so that when it's set to true UTF-8 is used. We keep the default encoding to ASCII to be compatible. In fact, RFC 3961 requires it to be UTF-8 string, and MIT krb5 also uses UTF-8. It's time to change the default to UTF-8. The system property can be kept.