JDK-8190229 : Non-ASCII characters in java.security file after 8186093
  • Type: Bug
  • Component: security-libs
  • Sub-Component: java.security
  • Affected Version: 10
  • Priority: P4
  • Status: Closed
  • Resolution: Fixed
  • Submitted: 2017-10-26
  • Updated: 2018-03-28
  • Resolved: 2018-01-18
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.
JDK 11
11 b01Fixed
Related Reports
Relates :  
JDK-8186093 - A comment in the java.security configuration file incorrectly says that "strong but limited" is the default value
Description
It looks like some editor highlighting got inserted surrounding "crypto.policy" and "limited"

# The default setting is determined by the value of the �������crypto.policy�������
# Security property below. If your country or usage requires the
# traditional restrictive policy, the �������limited������� Java cryptographic
# policy is still available and may be appropriate for your environment.
#
# If you have restrictions that do not fit either use case mentioned
# above, Java provides the capability to customize these policy files.
# The �������crypto.policy������� security property points to a subdirectory
Comments
Not sure what editor I used, but should definitely not be using those characters.
18-01-2018