JDK-8170498 : Update docs to reflect unlimited policy file by default
- Type: Sub-task
- Component: docs
- Sub-Component: guides
- Priority: P2
- Status: Resolved
- Resolution: Fixed
- Submitted: 2016-11-29
- Updated: 2017-09-07
- Resolved: 2017-09-07
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 9 |
|---|
9Fixed  |
Description
JCE Unlimited Strength Jurisdiction Policy Files ------------------------------------------------ This will be going away and will not be part of the JDK 9 download bundles. If folks need limited policy, they can either change the Security property or edit the unlimited files themselves. It's no longer a signed jar. crypto/CryptoSpec.html ---------------------- How to Make Applications"Exempt" from Cryptographic Restrictions Update: This will need to be updated slightly to say that it is no longer needed in JDK 9, but this will be left in in case limited policy files are used in other distros (e.g. likely IBM). jsse/JSSERefGuide.html ---------------------- How to enable 256 AES ciphersuites. Update: Same as above. SunProviders.html ----------------- Cipher: If stronger algorithms are needed (for example, AES with 256-bit keys). Update: Same as above. JSSE: AES_256 require stronger... Update: Same as above.