JDK-5097015 : Case sensitivity issues in the Provider class
- Type: Bug
- Component: security-libs
- Sub-Component: java.security
- Affected Version: 5.0
- Priority: P3
- Status: Resolved
- Resolution: Fixed
- OS: generic
- CPU: generic
- Submitted: 2004-09-03
- Updated: 2004-11-09
- Resolved: 2004-11-09
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.
| Other | JDK 6 |
|---|---|
| 5.0u4Fixed | 6 betaFixed  |
Description
The changes to the Provider class in Tiger caused an unintended change in behavior. It used to be that
put("MessageDigest.MD2", "com.foo...");
put("messagedigest.MD5", "com.foo...");
put("MESSAGEDIGEST.SHA", "com.foo...");
all worked. Now the parsing code is case sensitive and only "MessageDigest" works (similarly for other engine types). Although the documentation is unclear about case sensitivity in this case, the previous behavior needs to be restored for compatibility.
In addition, the new code in the Provider.Service class treats attributes as case sensitive, even though our documentation explicitly defines them to be case insensitive (see http://java.sun.com/j2se/1.5.0/docs/guide/security/CryptoSpec.html#AppA under "Service Attributes"). This should be corrected as well.
Comments
|