Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-8186093

A comment in the java.security configuration file incorrectly says that "strong but limited" is the default value

    XMLWordPrintable

Details

    • b22
    • Not verified

    Backports

      Description

        # Due to the import control restrictions of some countries, the default
        # JCE policy files allow for strong but "limited" cryptographic key
        # lengths to be used. If your country's cryptographic regulations allow,
        # the "unlimited" strength policy files can be used instead, which contain
        # no restrictions on cryptographic strengths.

        Since this is set by the configure" step, this section should be updated to describe the situation without naming the default, and let the user find the default value down further in the file.

        Attachments

          Issue Links

            backported by

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8186948 A comment in the java.security configuration file incorrectly says that "strong but limited" is the default value

            • P3 - Major loss of function.
            • Resolved

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8195253 A comment in the java.security configuration file incorrectly says that "strong but limited" is the default value

            • P3 - Major loss of function.
            • Resolved
            relates to

            Bug - A problem which impairs or prevents the functions of the product. JDK-8190229 Non-ASCII characters in java.security file after 8186093

            • P4 - Minor loss of function, or other problem where easy workaround is present.
            • Closed

            Enhancement - null JDK-8170157 Enable unlimited cryptographic policy by default in Oracle JDK builds

            • P2 - Crashes, loss of data, severe memory leak.
            • Resolved

            Activity

              People

                wetmore Bradford Wetmore
                wetmore Bradford Wetmore
                Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved: