JDK-6355984 : Remove transitionary certificate check in mustang's policy file.
- Type: Bug
- Component: security-libs
- Sub-Component: javax.crypto
- Affected Version: 6
- Priority: P4
- Status: Closed
- Resolution: Not an Issue
- OS: generic
- CPU: generic
- Submitted: 2005-11-28
- Updated: 2011-04-11
- Resolved: 2011-04-11
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 7 |
|---|
7Resolved  |
Related Reports
|
Relates :
|
|
|
Relates :
|
Description
As part of 6309875, we renewed the certificate that we use for signing the jar files. We normally only ship the unlimited policy files at milestones, so people would be without unlimited crypto until mustang-rc. Instead, we inserted a code snippet to check for either old or new policy files. This should be taken out eventually. We can do it for dolphin, or maybe later for mustang-GA.
Comments
|