804 # Due to the import control restrictions of some countries, the default

   807 # Import and export control rules on cryptographic software vary from

   805 # JCE policy files allow for strong but "limited" cryptographic key

   808 # country to country.  By default, Java provides two different sets of

   806 # lengths to be used.  If your country's cryptographic regulations allow,

   809 # cryptographic policy files[1]:

   807 # the "unlimited" strength policy files can be used instead, which contain

   810 #

   808 # no restrictions on cryptographic strengths.

   811 #     unlimited:  These policy files contain no restrictions on cryptographic

   809 #

   812 #                 strengths or algorithms

   810 # If your country has restrictions that don't fit either "limited" or

   813 #

   811 # "unlimited", an appropriate set of policy files should be created and

   814 #     limited:    These policy files contain more restricted cryptographic

   812 # configured before using this distribution.  The jurisdiction policy file

   815 #                 strengths

   813 # configuration must reflect the cryptographic restrictions appropriate

   816 #

   814 # for your country.

   817 # The default setting is determined by the value of the “crypto.policy”

   818 # Security property below. If your country or usage requires the

   819 # traditional restrictive policy, the “limited” Java cryptographic

   820 # policy is still available and may be appropriate for your environment.

   821 #

   822 # If you have restrictions that do not fit either use case mentioned

   823 # above, Java provides the capability to customize these policy files.

   824 # The “crypto.policy” security property points to a subdirectory

   825 # within <java-home>/conf/security/policy/ which can be customized.

   826 # Please see the <java-home>/conf/security/policy/README.txt file or consult

   827 # the Java Security Guide/JCA documentation for more information.

   819 # The policy files are flat text files organized into subdirectories of

   832 # [1] Please note that the JCE for Java SE, including the JCE framework,

   820 # <java-home>/conf/security/policy.  Each directory contains a complete

   833 # cryptographic policy files, and standard JCE providers provided with

   821 # set of policy files.

   834 # the Java SE, have been reviewed and approved for export as mass market

   822 #

   835 # encryption item by the US Bureau of Industry and Security.

   823 # The "crypto.policy" Security property controls the directory selection,

   824 # and thus the effective cryptographic policy.

   825 #

   826 # The default set of directories is:

   827 #

   828 #     limited | unlimited

   829 #

   830 # however other directories can be created and configured.

   831 #

   832 # Within a directory, the effective policy is the combined minimum

   833 # permissions of the grant statements in the file(s) with the filename

   834 # pattern "default_*.policy".  At least one grant is required.  For

   835 # example:

   836 #

   837 #     limited   =  Export (all) + Import (limited)  =  Limited

   838 #     unlimited =  Export (all) + Import (all)      =  Unlimited

   839 #

   840 # The effective exemption policy is the combined minimum permissions

   841 # of the grant statements in the file(s) with the filename pattern

   842 # "exempt_*.policy".  Exemption grants are optional.

   843 #

   844 #     limited   =  grants exemption permissions, by which the

   845 #                  effective policy can be circumvented.

   846 #                  e.g.  KeyRecovery/Escrow/Weakening.

   847 #

   848 # Please see the JCA documentation for additional information on these

   849 # files and formats.