1 #
2 # This is the "master security properties file".
3 #
4 # An alternate java.security properties file may be specified
5 # from the command line via the system property
6 #
7 # -Djava.security.properties=<URL>
8 #
9 # This properties file appends to the master security properties file.
10 # If both properties files specify values for the same key, the value
11 # from the command-line properties file is selected, as it is the last
12 # one loaded.
13 #
14 # Also, if you specify
15 #
16 # -Djava.security.properties==<URL> (2 equals),
17 #
18 # then that properties file completely overrides the master security
19 # properties file.
20 #
21 # To disable the ability to specify an additional properties file from
22 # the command line, set the key security.overridePropertiesFile
23 # to false in the master security properties file. It is set to true
24 # by default.
25
26 # In this file, various security properties are set for use by
27 # java.security classes. This is where users can statically register
28 # Cryptography Package Providers ("providers" for short). The term
29 # "provider" refers to a package or set of packages that supply a
30 # concrete implementation of a subset of the cryptography aspects of
31 # the Java Security API. A provider may, for example, implement one or
32 # more digital signature algorithms or message digest algorithms.
33 #
34 # Each provider must implement a subclass of the Provider class.
35 # To register a provider in this master security properties file,
36 # specify the Provider subclass name and priority in the format
37 #
38 # security.provider.<n>=<className>
39 #
40 # This declares a provider, and specifies its preference
41 # order n. The preference order is the order in which providers are
42 # searched for requested algorithms (when no specific provider is
43 # requested). The order is 1-based; 1 is the most preferred, followed
44 # by 2, and so on.
45 #
46 # <className> must specify the subclass of the Provider class whose
47 # constructor sets the values of various properties that are required
48 # for the Java Security API to look up the algorithms or other
49 # facilities implemented by the provider.
50 #
51 # There must be at least one provider specification in java.security.
52 # There is a default provider that comes standard with the JDK. It
53 # is called the "SUN" provider, and its Provider subclass
54 # named Sun appears in the sun.security.provider package. Thus, the
55 # "SUN" provider is registered via the following:
56 #
57 # security.provider.1=sun.security.provider.Sun
58 #
59 # (The number 1 is used for the default provider.)
60 #
61 # Note: Providers can be dynamically registered instead by calls to
62 # either the addProvider or insertProviderAt method in the Security
63 # class.
64
65 #
66 # List of providers and their preference orders (see above):
67 #
68 security.provider.1=sun.security.provider.Sun
69 security.provider.2=sun.security.rsa.SunRsaSign
70 security.provider.3=sun.security.ec.SunEC
71 security.provider.4=com.sun.net.ssl.internal.ssl.Provider
72 security.provider.5=com.sun.crypto.provider.SunJCE
73 security.provider.6=sun.security.jgss.SunProvider
74 security.provider.7=com.sun.security.sasl.Provider
75 security.provider.8=org.jcp.xml.dsig.internal.dom.XMLDSigRI
76 security.provider.9=sun.security.smartcardio.SunPCSC
77 security.provider.10=sun.security.mscapi.SunMSCAPI
78
79 #
80 # Sun Provider SecureRandom seed source.
81 #
82 # Select the primary source of seed data for the "SHA1PRNG" and
83 # "NativePRNG" SecureRandom implementations in the "Sun" provider.
84 # (Other SecureRandom implementations might also use this property.)
85 #
86 # On Unix-like systems (for example, Solaris/Linux/MacOS), the
87 # "NativePRNG" and "SHA1PRNG" implementations obtains seed data from
88 # special device files such as file:/dev/random.
89 #
90 # On Windows systems, specifying the URLs "file:/dev/random" or
91 # "file:/dev/urandom" will enable the native Microsoft CryptoAPI seeding
92 # mechanism for SHA1PRNG.
93 #
94 # By default, an attempt is made to use the entropy gathering device
95 # specified by the "securerandom.source" Security property. If an
96 # exception occurs while accessing the specified URL:
97 #
98 # SHA1PRNG:
99 # the traditional system/thread activity algorithm will be used.
100 #
101 # NativePRNG:
102 # a default value of /dev/random will be used. If neither
103 # are available, the implementation will be disabled.
104 # "file" is the only currently supported protocol type.
105 #
106 # The entropy gathering device can also be specified with the System
107 # property "java.security.egd". For example:
108 #
109 # % java -Djava.security.egd=file:/dev/random MainClass
110 #
111 # Specifying this System property will override the
112 # "securerandom.source" Security property.
113 #
114 # In addition, if "file:/dev/random" or "file:/dev/urandom" is
115 # specified, the "NativePRNG" implementation will be more preferred than
116 # SHA1PRNG in the Sun provider.
117 #
118 securerandom.source=file:/dev/random
119
120 #
121 # A list of known strong SecureRandom implementations.
122 #
123 # To help guide applications in selecting a suitable strong
124 # java.security.SecureRandom implementation, Java distributions should
125 # indicate a list of known strong implementations using the property.
126 #
127 # This is a comma-separated list of algorithm and/or algorithm:provider
128 # entries.
129 #
130 securerandom.strongAlgorithms=Windows-PRNG:SunMSCAPI,SHA1PRNG:SUN
131
132 #
133 # Class to instantiate as the javax.security.auth.login.Configuration
134 # provider.
135 #
136 login.configuration.provider=sun.security.provider.ConfigFile
137
138 #
139 # Default login configuration file
140 #
141 #login.config.url.1=file:${user.home}/.java.login.config
142
143 #
144 # Class to instantiate as the system Policy. This is the name of the class
145 # that will be used as the Policy object.
146 #
147 policy.provider=sun.security.provider.PolicyFile
148
149 # The default is to have a single system-wide policy file,
150 # and a policy file in the user's home directory.
151 policy.url.1=file:${java.home}/lib/security/java.policy
152 policy.url.2=file:${user.home}/.java.policy
153
154 # whether or not we expand properties in the policy file
155 # if this is set to false, properties (${...}) will not be expanded in policy
156 # files.
157 policy.expandProperties=true
158
159 # whether or not we allow an extra policy to be passed on the command line
160 # with -Djava.security.policy=somefile. Comment out this line to disable
161 # this feature.
162 policy.allowSystemProperty=true
163
164 # whether or not we look into the IdentityScope for trusted Identities
165 # when encountering a 1.1 signed JAR file. If the identity is found
166 # and is trusted, we grant it AllPermission.
167 policy.ignoreIdentityScope=false
168
169 #
170 # Default keystore type.
171 #
172 keystore.type=jks
173
174 #
175 # Controls compatibility mode for the JKS keystore type.
176 #
177 # When set to 'true', the JKS keystore type supports loading
178 # keystore files in either JKS or PKCS12 format. When set to 'false'
179 # it supports loading only JKS keystore files.
180 #
181 keystore.type.compat=true
182
183 #
184 # List of comma-separated packages that start with or equal this string
185 # will cause a security exception to be thrown when
186 # passed to checkPackageAccess unless the
187 # corresponding RuntimePermission ("accessClassInPackage."+package) has
188 # been granted.
189 package.access=sun.,\
190 com.sun.xml.internal.,\
191 com.sun.imageio.,\
192 com.sun.istack.internal.,\
193 com.sun.jmx.,\
194 com.sun.media.sound.,\
195 com.sun.naming.internal.,\
196 com.sun.proxy.,\
197 com.sun.corba.se.,\
198 com.sun.org.apache.bcel.internal.,\
199 com.sun.org.apache.regexp.internal.,\
200 com.sun.org.apache.xerces.internal.,\
201 com.sun.org.apache.xpath.internal.,\
202 com.sun.org.apache.xalan.internal.extensions.,\
203 com.sun.org.apache.xalan.internal.lib.,\
204 com.sun.org.apache.xalan.internal.res.,\
205 com.sun.org.apache.xalan.internal.templates.,\
206 com.sun.org.apache.xalan.internal.utils.,\
207 com.sun.org.apache.xalan.internal.xslt.,\
208 com.sun.org.apache.xalan.internal.xsltc.cmdline.,\
209 com.sun.org.apache.xalan.internal.xsltc.compiler.,\
210 com.sun.org.apache.xalan.internal.xsltc.trax.,\
211 com.sun.org.apache.xalan.internal.xsltc.util.,\
212 com.sun.org.apache.xml.internal.res.,\
213 com.sun.org.apache.xml.internal.resolver.helpers.,\
214 com.sun.org.apache.xml.internal.resolver.readers.,\
215 com.sun.org.apache.xml.internal.security.,\
216 com.sun.org.apache.xml.internal.serializer.utils.,\
217 com.sun.org.apache.xml.internal.utils.,\
218 com.sun.org.glassfish.,\
219 com.oracle.xmlns.internal.,\
220 com.oracle.webservices.internal.,\
221 oracle.jrockit.jfr.,\
222 org.jcp.xml.dsig.internal.,\
223 jdk.internal.,\
224 jdk.nashorn.internal.,\
225 jdk.nashorn.tools.,\
226 com.sun.activation.registries.,\
227 com.sun.java.accessibility.
228
229 #
230 # List of comma-separated packages that start with or equal this string
231 # will cause a security exception to be thrown when
232 # passed to checkPackageDefinition unless the
233 # corresponding RuntimePermission ("defineClassInPackage."+package) has
234 # been granted.
235 #
236 # by default, none of the class loaders supplied with the JDK call
237 # checkPackageDefinition.
238 #
239 package.definition=sun.,\
240 com.sun.xml.internal.,\
241 com.sun.imageio.,\
242 com.sun.istack.internal.,\
243 com.sun.jmx.,\
244 com.sun.media.sound.,\
245 com.sun.naming.internal.,\
246 com.sun.proxy.,\
247 com.sun.corba.se.,\
248 com.sun.org.apache.bcel.internal.,\
249 com.sun.org.apache.regexp.internal.,\
250 com.sun.org.apache.xerces.internal.,\
251 com.sun.org.apache.xpath.internal.,\
252 com.sun.org.apache.xalan.internal.extensions.,\
253 com.sun.org.apache.xalan.internal.lib.,\
254 com.sun.org.apache.xalan.internal.res.,\
255 com.sun.org.apache.xalan.internal.templates.,\
256 com.sun.org.apache.xalan.internal.utils.,\
257 com.sun.org.apache.xalan.internal.xslt.,\
258 com.sun.org.apache.xalan.internal.xsltc.cmdline.,\
259 com.sun.org.apache.xalan.internal.xsltc.compiler.,\
260 com.sun.org.apache.xalan.internal.xsltc.trax.,\
261 com.sun.org.apache.xalan.internal.xsltc.util.,\
262 com.sun.org.apache.xml.internal.res.,\
263 com.sun.org.apache.xml.internal.resolver.helpers.,\
264 com.sun.org.apache.xml.internal.resolver.readers.,\
265 com.sun.org.apache.xml.internal.security.,\
266 com.sun.org.apache.xml.internal.serializer.utils.,\
267 com.sun.org.apache.xml.internal.utils.,\
268 com.sun.org.glassfish.,\
269 com.oracle.xmlns.internal.,\
270 com.oracle.webservices.internal.,\
271 oracle.jrockit.jfr.,\
272 org.jcp.xml.dsig.internal.,\
273 jdk.internal.,\
274 jdk.nashorn.internal.,\
275 jdk.nashorn.tools.,\
276 com.sun.activation.registries.,\
277 com.sun.java.accessibility.
278
279 #
280 # Determines whether this properties file can be appended to
281 # or overridden on the command line via -Djava.security.properties
282 #
283 security.overridePropertiesFile=true
284
285 #
286 # Determines the default key and trust manager factory algorithms for
287 # the javax.net.ssl package.
288 #
289 ssl.KeyManagerFactory.algorithm=SunX509
290 ssl.TrustManagerFactory.algorithm=PKIX
291
292 #
293 # The Java-level namelookup cache policy for successful lookups:
294 #
295 # any negative value: caching forever
296 # any positive value: the number of seconds to cache an address for
297 # zero: do not cache
298 #
299 # default value is forever (FOREVER). For security reasons, this
300 # caching is made forever when a security manager is set. When a security
301 # manager is not set, the default behavior in this implementation
302 # is to cache for 30 seconds.
303 #
304 # NOTE: setting this to anything other than the default value can have
305 # serious security implications. Do not set it unless
306 # you are sure you are not exposed to DNS spoofing attack.
307 #
308 #networkaddress.cache.ttl=-1
309
310 # The Java-level namelookup cache policy for failed lookups:
311 #
312 # any negative value: cache forever
313 # any positive value: the number of seconds to cache negative lookup results
314 # zero: do not cache
315 #
316 # In some Microsoft Windows networking environments that employ
317 # the WINS name service in addition to DNS, name service lookups
318 # that fail may take a noticeably long time to return (approx. 5 seconds).
319 # For this reason the default caching policy is to maintain these
320 # results for 10 seconds.
321 #
322 #
323 networkaddress.cache.negative.ttl=10
324
325 #
326 # Properties to configure OCSP for certificate revocation checking
327 #
328
329 # Enable OCSP
330 #
331 # By default, OCSP is not used for certificate revocation checking.
332 # This property enables the use of OCSP when set to the value "true".
333 #
334 # NOTE: SocketPermission is required to connect to an OCSP responder.
335 #
336 # Example,
337 # ocsp.enable=true
338
339 #
340 # Location of the OCSP responder
341 #
342 # By default, the location of the OCSP responder is determined implicitly
343 # from the certificate being validated. This property explicitly specifies
344 # the location of the OCSP responder. The property is used when the
345 # Authority Information Access extension (defined in RFC 3280) is absent
346 # from the certificate or when it requires overriding.
347 #
348 # Example,
349 # ocsp.responderURL=http://ocsp.example.net:80
350
351 #
352 # Subject name of the OCSP responder's certificate
353 #
354 # By default, the certificate of the OCSP responder is that of the issuer
355 # of the certificate being validated. This property identifies the certificate
356 # of the OCSP responder when the default does not apply. Its value is a string
357 # distinguished name (defined in RFC 2253) which identifies a certificate in
358 # the set of certificates supplied during cert path validation. In cases where
359 # the subject name alone is not sufficient to uniquely identify the certificate
360 # then both the "ocsp.responderCertIssuerName" and
361 # "ocsp.responderCertSerialNumber" properties must be used instead. When this
362 # property is set then those two properties are ignored.
363 #
364 # Example,
365 # ocsp.responderCertSubjectName="CN=OCSP Responder, O=XYZ Corp"
366
367 #
368 # Issuer name of the OCSP responder's certificate
369 #
370 # By default, the certificate of the OCSP responder is that of the issuer
371 # of the certificate being validated. This property identifies the certificate
372 # of the OCSP responder when the default does not apply. Its value is a string
373 # distinguished name (defined in RFC 2253) which identifies a certificate in
374 # the set of certificates supplied during cert path validation. When this
375 # property is set then the "ocsp.responderCertSerialNumber" property must also
376 # be set. When the "ocsp.responderCertSubjectName" property is set then this
377 # property is ignored.
378 #
379 # Example,
380 # ocsp.responderCertIssuerName="CN=Enterprise CA, O=XYZ Corp"
381
382 #
383 # Serial number of the OCSP responder's certificate
384 #
385 # By default, the certificate of the OCSP responder is that of the issuer
386 # of the certificate being validated. This property identifies the certificate
387 # of the OCSP responder when the default does not apply. Its value is a string
388 # of hexadecimal digits (colon or space separators may be present) which
389 # identifies a certificate in the set of certificates supplied during cert path
390 # validation. When this property is set then the "ocsp.responderCertIssuerName"
391 # property must also be set. When the "ocsp.responderCertSubjectName" property
392 # is set then this property is ignored.
393 #
394 # Example,
395 # ocsp.responderCertSerialNumber=2A:FF:00
396
397 #
398 # Policy for failed Kerberos KDC lookups:
399 #
400 # When a KDC is unavailable (network error, service failure, etc), it is
401 # put inside a blacklist and accessed less often for future requests. The
402 # value (case-insensitive) for this policy can be:
403 #
404 # tryLast
405 # KDCs in the blacklist are always tried after those not on the list.
406 #
407 # tryLess[:max_retries,timeout]
408 # KDCs in the blacklist are still tried by their order in the configuration,
409 # but with smaller max_retries and timeout values. max_retries and timeout
410 # are optional numerical parameters (default 1 and 5000, which means once
411 # and 5 seconds). Please notes that if any of the values defined here is
412 # more than what is defined in krb5.conf, it will be ignored.
413 #
414 # Whenever a KDC is detected as available, it is removed from the blacklist.
415 # The blacklist is reset when krb5.conf is reloaded. You can add
416 # refreshKrb5Config=true to a JAAS configuration file so that krb5.conf is
417 # reloaded whenever a JAAS authentication is attempted.
418 #
419 # Example,
420 # krb5.kdc.bad.policy = tryLast
421 # krb5.kdc.bad.policy = tryLess:2,2000
422 krb5.kdc.bad.policy = tryLast
423
424 # Algorithm restrictions for certification path (CertPath) processing
425 #
426 # In some environments, certain algorithms or key lengths may be undesirable
427 # for certification path building and validation. For example, "MD2" is
428 # generally no longer considered to be a secure hash algorithm. This section
429 # describes the mechanism for disabling algorithms based on algorithm name
430 # and/or key length. This includes algorithms used in certificates, as well
431 # as revocation information such as CRLs and signed OCSP Responses.
432 # The syntax of the disabled algorithm string is described as follows:
433 # DisabledAlgorithms:
434 # " DisabledAlgorithm { , DisabledAlgorithm } "
435 #
436 # DisabledAlgorithm:
437 # AlgorithmName [Constraint] { '&' Constraint }
438 #
439 # AlgorithmName:
440 # (see below)
441 #
442 # Constraint:
443 # KeySizeConstraint | CAConstraint | DenyAfterConstraint |
444 # UsageConstraint
445 #
446 # KeySizeConstraint:
447 # keySize Operator KeyLength
448 #
449 # Operator:
450 # <= | < | == | != | >= | >
451 #
452 # KeyLength:
453 # Integer value of the algorithm's key length in bits
454 #
455 # CAConstraint:
456 # jdkCA
457 #
458 # DenyAfterConstraint:
459 # denyAfter YYYY-MM-DD
460 #
461 # UsageConstraint:
462 # usage [TLSServer] [TLSClient] [SignedJAR]
463 #
464 # The "AlgorithmName" is the standard algorithm name of the disabled
465 # algorithm. See "Java Cryptography Architecture Standard Algorithm Name
466 # Documentation" for information about Standard Algorithm Names. Matching
467 # is performed using a case-insensitive sub-element matching rule. (For
468 # example, in "SHA1withECDSA" the sub-elements are "SHA1" for hashing and
469 # "ECDSA" for signatures.) If the assertion "AlgorithmName" is a
470 # sub-element of the certificate algorithm name, the algorithm will be
471 # rejected during certification path building and validation. For example,
472 # the assertion algorithm name "DSA" will disable all certificate algorithms
473 # that rely on DSA, such as NONEwithDSA, SHA1withDSA. However, the assertion
474 # will not disable algorithms related to "ECDSA".
475 #
476 # A "Constraint" defines restrictions on the keys and/or certificates for
477 # a specified AlgorithmName:
478 #
479 # KeySizeConstraint:
480 # keySize Operator KeyLength
481 # The constraint requires a key of a valid size range if the
482 # "AlgorithmName" is of a key algorithm. The "KeyLength" indicates
483 # the key size specified in number of bits. For example,
484 # "RSA keySize <= 1024" indicates that any RSA key with key size less
485 # than or equal to 1024 bits should be disabled, and
486 # "RSA keySize < 1024, RSA keySize > 2048" indicates that any RSA key
487 # with key size less than 1024 or greater than 2048 should be disabled.
488 # This constraint is only used on algorithms that have a key size.
489 #
490 # CAConstraint:
491 # jdkCA
492 # This constraint prohibits the specified algorithm only if the
493 # algorithm is used in a certificate chain that terminates at a marked
494 # trust anchor in the lib/security/cacerts keystore. If the jdkCA
495 # constraint is not set, then all chains using the specified algorithm
496 # are restricted. jdkCA may only be used once in a DisabledAlgorithm
497 # expression.
498 # Example: To apply this constraint to SHA-1 certificates, include
499 # the following: "SHA1 jdkCA"
500 #
501 # DenyAfterConstraint:
502 # denyAfter YYYY-MM-DD
503 # This constraint prohibits a certificate with the specified algorithm
504 # from being used after the date regardless of the certificate's
505 # validity. JAR files that are signed and timestamped before the
506 # constraint date with certificates containing the disabled algorithm
507 # will not be restricted. The date is processed in the UTC timezone.
508 # This constraint can only be used once in a DisabledAlgorithm
509 # expression.
510 # Example: To deny usage of RSA 2048 bit certificates after Feb 3 2020,
511 # use the following: "RSA keySize == 2048 & denyAfter 2020-02-03"
512 #
513 # UsageConstraint:
514 # usage [TLSServer] [TLSClient] [SignedJAR]
515 # This constraint prohibits the specified algorithm for
516 # a specified usage. This should be used when disabling an algorithm
517 # for all usages is not practical. 'TLSServer' restricts the algorithm
518 # in TLS server certificate chains when server authentication is
519 # performed. 'TLSClient' restricts the algorithm in TLS client
520 # certificate chains when client authentication is performed.
521 # 'SignedJAR' constrains use of certificates in signed jar files.
522 # The usage type follows the keyword and more than one usage type can
523 # be specified with a whitespace delimiter.
524 # Example: "SHA1 usage TLSServer TLSClient"
525 #
526 # When an algorithm must satisfy more than one constraint, it must be
527 # delimited by an ampersand '&'. For example, to restrict certificates in a
528 # chain that terminate at a distribution provided trust anchor and contain
529 # RSA keys that are less than or equal to 1024 bits, add the following
530 # constraint: "RSA keySize <= 1024 & jdkCA".
531 #
532 # All DisabledAlgorithms expressions are processed in the order defined in the
533 # property. This requires lower keysize constraints to be specified
534 # before larger keysize constraints of the same algorithm. For example:
535 # "RSA keySize < 1024 & jdkCA, RSA keySize < 2048".
536 #
537 # Note: The algorithm restrictions do not apply to trust anchors or
538 # self-signed certificates.
539 #
540 # Note: This property is currently used by Oracle's PKIX implementation. It
541 # is not guaranteed to be examined and used by other implementations.
542 #
543 # Example:
544 # jdk.certpath.disabledAlgorithms=MD2, DSA, RSA keySize < 2048
545 #
546 #
547 jdk.certpath.disabledAlgorithms=MD2, MD5, SHA1 jdkCA & usage TLSServer, \
548 RSA keySize < 1024, DSA keySize < 1024, EC keySize < 224
549
550 #
551 # Algorithm restrictions for signed JAR files
552 #
553 # In some environments, certain algorithms or key lengths may be undesirable
554 # for signed JAR validation. For example, "MD2" is generally no longer
555 # considered to be a secure hash algorithm. This section describes the
556 # mechanism for disabling algorithms based on algorithm name and/or key length.
557 # JARs signed with any of the disabled algorithms or key sizes will be treated
558 # as unsigned.
559 #
560 # The syntax of the disabled algorithm string is described as follows:
561 # DisabledAlgorithms:
562 # " DisabledAlgorithm { , DisabledAlgorithm } "
563 #
564 # DisabledAlgorithm:
565 # AlgorithmName [Constraint] { '&' Constraint }
566 #
567 # AlgorithmName:
568 # (see below)
569 #
570 # Constraint:
571 # KeySizeConstraint | DenyAfterConstraint
572 #
573 # KeySizeConstraint:
574 # keySize Operator KeyLength
575 #
576 # DenyAfterConstraint:
577 # denyAfter YYYY-MM-DD
578 #
579 # Operator:
580 # <= | < | == | != | >= | >
581 #
582 # KeyLength:
583 # Integer value of the algorithm's key length in bits
584 #
585 # Note: This property is currently used by the JDK Reference
586 # implementation. It is not guaranteed to be examined and used by other
587 # implementations.
588 #
589 # See "jdk.certpath.disabledAlgorithms" for syntax descriptions.
590 #
591 jdk.jar.disabledAlgorithms=MD2, MD5, RSA keySize < 1024
592
593 #
594 # Algorithm restrictions for Secure Socket Layer/Transport Layer Security
595 # (SSL/TLS) processing
596 #
597 # In some environments, certain algorithms or key lengths may be undesirable
598 # when using SSL/TLS. This section describes the mechanism for disabling
599 # algorithms during SSL/TLS security parameters negotiation, including
600 # protocol version negotiation, cipher suites selection, peer authentication
601 # and key exchange mechanisms.
602 #
603 # Disabled algorithms will not be negotiated for SSL/TLS connections, even
604 # if they are enabled explicitly in an application.
605 #
606 # For PKI-based peer authentication and key exchange mechanisms, this list
607 # of disabled algorithms will also be checked during certification path
608 # building and validation, including algorithms used in certificates, as
609 # well as revocation information such as CRLs and signed OCSP Responses.
610 # This is in addition to the jdk.certpath.disabledAlgorithms property above.
611 #
612 # See the specification of "jdk.certpath.disabledAlgorithms" for the
613 # syntax of the disabled algorithm string.
614 #
615 # Note: The algorithm restrictions do not apply to trust anchors or
616 # self-signed certificates.
617 #
618 # Note: This property is currently used by the JDK Reference implementation.
619 # It is not guaranteed to be examined and used by other implementations.
620 #
621 # Example:
622 # jdk.tls.disabledAlgorithms=MD5, SSLv3, DSA, RSA keySize < 2048
623 jdk.tls.disabledAlgorithms=SSLv3, RC4, MD5withRSA, DH keySize < 768, \
624 EC keySize < 224
625
626 # Legacy algorithms for Secure Socket Layer/Transport Layer Security (SSL/TLS)
627 # processing in JSSE implementation.
628 #
629 # In some environments, a certain algorithm may be undesirable but it
630 # cannot be disabled because of its use in legacy applications. Legacy
631 # algorithms may still be supported, but applications should not use them
632 # as the security strength of legacy algorithms are usually not strong enough
633 # in practice.
634 #
635 # During SSL/TLS security parameters negotiation, legacy algorithms will
636 # not be negotiated unless there are no other candidates.
637 #
638 # The syntax of the legacy algorithms string is described as this Java
639 # BNF-style:
640 # LegacyAlgorithms:
641 # " LegacyAlgorithm { , LegacyAlgorithm } "
642 #
643 # LegacyAlgorithm:
644 # AlgorithmName (standard JSSE algorithm name)
645 #
646 # See the specification of security property "jdk.certpath.disabledAlgorithms"
647 # for the syntax and description of the "AlgorithmName" notation.
648 #
649 # Per SSL/TLS specifications, cipher suites have the form:
650 # SSL_KeyExchangeAlg_WITH_CipherAlg_MacAlg
651 # or
652 # TLS_KeyExchangeAlg_WITH_CipherAlg_MacAlg
653 #
654 # For example, the cipher suite TLS_RSA_WITH_AES_128_CBC_SHA uses RSA as the
655 # key exchange algorithm, AES_128_CBC (128 bits AES cipher algorithm in CBC
656 # mode) as the cipher (encryption) algorithm, and SHA-1 as the message digest
657 # algorithm for HMAC.
658 #
659 # The LegacyAlgorithm can be one of the following standard algorithm names:
660 # 1. JSSE cipher suite name, e.g., TLS_RSA_WITH_AES_128_CBC_SHA
661 # 2. JSSE key exchange algorithm name, e.g., RSA
662 # 3. JSSE cipher (encryption) algorithm name, e.g., AES_128_CBC
663 # 4. JSSE message digest algorithm name, e.g., SHA
664 #
665 # See SSL/TLS specifications and "Java Cryptography Architecture Standard
666 # Algorithm Name Documentation" for information about the algorithm names.
667 #
668 # Note: This property is currently used by the JDK Reference implementation.
669 # It is not guaranteed to be examined and used by other implementations.
670 # There is no guarantee the property will continue to exist or be of the
671 # same syntax in future releases.
672 #
673 # Example:
674 # jdk.tls.legacyAlgorithms=DH_anon, DES_CBC, SSL_RSA_WITH_RC4_128_MD5
675 #
676 jdk.tls.legacyAlgorithms= \
677 K_NULL, C_NULL, M_NULL, \
678 DHE_DSS_EXPORT, DHE_RSA_EXPORT, DH_anon_EXPORT, DH_DSS_EXPORT, \
679 DH_RSA_EXPORT, RSA_EXPORT, \
680 DH_anon, ECDH_anon, \
681 RC4_128, RC4_40, DES_CBC, DES40_CBC, \
682 3DES_EDE_CBC
683
684 # The pre-defined default finite field Diffie-Hellman ephemeral (DHE)
685 # parameters for Transport Layer Security (SSL/TLS/DTLS) processing.
686 #
687 # In traditional SSL/TLS/DTLS connections where finite field DHE parameters
688 # negotiation mechanism is not used, the server offers the client group
689 # parameters, base generator g and prime modulus p, for DHE key exchange.
690 # It is recommended to use dynamic group parameters. This property defines
691 # a mechanism that allows you to specify custom group parameters.
692 #
693 # The syntax of this property string is described as this Java BNF-style:
694 # DefaultDHEParameters:
695 # DefinedDHEParameters { , DefinedDHEParameters }
696 #
697 # DefinedDHEParameters:
698 # "{" DHEPrimeModulus , DHEBaseGenerator "}"
699 #
700 # DHEPrimeModulus:
701 # HexadecimalDigits
702 #
703 # DHEBaseGenerator:
704 # HexadecimalDigits
705 #
706 # HexadecimalDigits:
707 # HexadecimalDigit { HexadecimalDigit }
708 #
709 # HexadecimalDigit: one of
710 # 0 1 2 3 4 5 6 7 8 9 A B C D E F a b c d e f
711 #
712 # Whitespace characters are ignored.
713 #
714 # The "DefinedDHEParameters" defines the custom group parameters, prime
715 # modulus p and base generator g, for a particular size of prime modulus p.
716 # The "DHEPrimeModulus" defines the hexadecimal prime modulus p, and the
717 # "DHEBaseGenerator" defines the hexadecimal base generator g of a group
718 # parameter. It is recommended to use safe primes for the custom group
719 # parameters.
720 #
721 # If this property is not defined or the value is empty, the underlying JSSE
722 # provider's default group parameter is used for each connection.
723 #
724 # If the property value does not follow the grammar, or a particular group
725 # parameter is not valid, the connection will fall back and use the
726 # underlying JSSE provider's default group parameter.
727 #
728 # Note: This property is currently used by OpenJDK's JSSE implementation. It
729 # is not guaranteed to be examined and used by other implementations.
730 #
731 # Example:
732 # jdk.tls.server.defaultDHEParameters=
733 # { \
734 # FFFFFFFF FFFFFFFF C90FDAA2 2168C234 C4C6628B 80DC1CD1 \
735 # 29024E08 8A67CC74 020BBEA6 3B139B22 514A0879 8E3404DD \
736 # EF9519B3 CD3A431B 302B0A6D F25F1437 4FE1356D 6D51C245 \
737 # E485B576 625E7EC6 F44C42E9 A637ED6B 0BFF5CB6 F406B7ED \
738 # EE386BFB 5A899FA5 AE9F2411 7C4B1FE6 49286651 ECE65381 \
739 # FFFFFFFF FFFFFFFF, 2}
740
741 # Cryptographic Jurisdiction Policy defaults
742 #
743 # Due to the import control restrictions of some countries, the default
744 # JCE policy files allow for strong but "limited" cryptographic key
745 # lengths to be used. If your country's cryptographic regulations allow,
746 # the "unlimited" strength policy files can be used instead, which contain
747 # no restrictions on cryptographic strengths.
748 #
749 # YOU ARE ADVISED TO CONSULT YOUR EXPORT/IMPORT CONTROL COUNSEL OR ATTORNEY
750 # TO DETERMINE THE EXACT REQUIREMENTS.
751 #
752 # <java-home> (below) refers to the directory where the JRE was
753 # installed. It is determined based on whether you are running JCE
754 # on a JRE or a JRE contained within the Java Development Kit, or
755 # JDK(TM). The JDK contains the JRE, but at a different level in the
756 # file hierarchy. For example, if the JDK is installed in
757 # /home/user1/jdk1.8.0 on Unix or in C:\jdk1.8.0 on Windows, then
758 # <java-home> is:
759 #
760 # /home/user1/jdk1.8.0/jre [Unix]
761 # C:\jdk1.8.0\jre [Windows]
762 #
763 # If on the other hand the JRE is installed in /home/user1/jre1.8.0
764 # on Unix or in C:\jre1.8.0 on Windows, and the JDK is not
765 # installed, then <java-home> is:
766 #
767 # /home/user1/jre1.8.0 [Unix]
768 # C:\jre1.8.0 [Windows]
769 #
770 # On Windows, for each JDK installation, there may be additional
771 # JREs installed under the "Program Files" directory. Please make
772 # sure that you install the unlimited strength policy JAR files
773 # for all JREs that you plan to use.
774 #
775 # The policy files are jar files organized into subdirectories of
776 # <java-home>/lib/security/policy. Each directory contains a complete
777 # set of policy files.
778 #
779 # The "crypto.policy" Security property controls the directory selection,
780 # and thus the effective cryptographic policy.
781 #
782 # The default set of directories is:
783 #
784 # limited | unlimited
785 #
786 # however other directories can be created and configured.
787 #
788 # To support older JDK Update releases, the crypto.policy property
789 # is not defined by default. When the property is not defined, an
790 # update release binary aware of the new property will use the following
791 # logic to decide what crypto policy files get used :
792 #
793 # * If the US_export_policy.jar and local_policy.jar files are located
794 # in the (legacy) <java-home>/lib/security directory, then the rules
795 # embedded in those jar files will be used. This helps preserve compatibility
796 # for users upgrading from an older installation.
797 #
798 # * If crypto.policy is not defined and no such jar files are present in
799 # the legacy locations, then the JDK will use the limited settings
800 # (equivalent to crypto.policy=limited)
801 #
802 # Please see the JCA documentation for additional information on these
803 # files and formats.
804 #crypto.policy=unlimited
805
806 #
807 # The policy for the XML Signature secure validation mode. The mode is
808 # enabled by setting the property "org.jcp.xml.dsig.secureValidation" to
809 # true with the javax.xml.crypto.XMLCryptoContext.setProperty() method,
810 # or by running the code with a SecurityManager.
811 #
812 # Policy:
813 # Constraint {"," Constraint }
814 # Constraint:
815 # AlgConstraint | MaxTransformsConstraint | MaxReferencesConstraint |
816 # ReferenceUriSchemeConstraint | KeySizeConstraint | OtherConstraint
817 # AlgConstraint
818 # "disallowAlg" Uri
819 # MaxTransformsConstraint:
820 # "maxTransforms" Integer
821 # MaxReferencesConstraint:
822 # "maxReferences" Integer
823 # ReferenceUriSchemeConstraint:
824 # "disallowReferenceUriSchemes" String { String }
825 # KeySizeConstraint:
826 # "minKeySize" KeyAlg Integer
827 # OtherConstraint:
828 # "noDuplicateIds" | "noRetrievalMethodLoops"
829 #
830 # For AlgConstraint, Uri is the algorithm URI String that is not allowed.
831 # See the XML Signature Recommendation for more information on algorithm
832 # URI Identifiers. For KeySizeConstraint, KeyAlg is the standard algorithm
833 # name of the key type (ex: "RSA"). If the MaxTransformsConstraint,
834 # MaxReferencesConstraint or KeySizeConstraint (for the same key type) is
835 # specified more than once, only the last entry is enforced.
836 #
837 # Note: This property is currently used by the JDK Reference implementation. It
838 # is not guaranteed to be examined and used by other implementations.
839 #
840 jdk.xml.dsig.secureValidationPolicy=\
841 disallowAlg http://www.w3.org/TR/1999/REC-xslt-19991116,\
842 disallowAlg http://www.w3.org/2001/04/xmldsig-more#rsa-md5,\
843 disallowAlg http://www.w3.org/2001/04/xmldsig-more#hmac-md5,\
844 disallowAlg http://www.w3.org/2001/04/xmldsig-more#md5,\
845 maxTransforms 5,\
846 maxReferences 30,\
847 disallowReferenceUriSchemes file http https,\
848 minKeySize RSA 1024,\
849 minKeySize DSA 1024,\
850 noDuplicateIds,\
851 noRetrievalMethodLoops
852
853 #
854 # Serialization process-wide filter
855 #
856 # A filter, if configured, is used by java.io.ObjectInputStream during
857 # deserialization to check the contents of the stream.
858 # A filter is configured as a sequence of patterns, each pattern is either
859 # matched against the name of a class in the stream or defines a limit.
860 # Patterns are separated by ";" (semicolon).
861 # Whitespace is significant and is considered part of the pattern.
862 #
863 # If a pattern includes a "=", it sets a limit.
864 # If a limit appears more than once the last value is used.
865 # Limits are checked before classes regardless of the order in the sequence of patterns.
866 # If any of the limits are exceeded, the filter status is REJECTED.
867 #
868 # maxdepth=value - the maximum depth of a graph
869 # maxrefs=value - the maximum number of internal references
870 # maxbytes=value - the maximum number of bytes in the input stream
871 # maxarray=value - the maximum array length allowed
872 #
873 # Other patterns, from left to right, match the class or package name as
874 # returned from Class.getName.
875 # If the class is an array type, the class or package to be matched is the element type.
876 # Arrays of any number of dimensions are treated the same as the element type.
877 # For example, a pattern of "!example.Foo", rejects creation of any instance or
878 # array of example.Foo.
879 #
880 # If the pattern starts with "!", the status is REJECTED if the remaining pattern
881 # is matched; otherwise the status is ALLOWED if the pattern matches.
882 # If the pattern ends with ".**" it matches any class in the package and all subpackages.
883 # If the pattern ends with ".*" it matches any class in the package.
884 # If the pattern ends with "*", it matches any class with the pattern as a prefix.
885 # If the pattern is equal to the class name, it matches.
886 # Otherwise, the status is UNDECIDED.
887 #
888 #jdk.serialFilter=pattern;pattern
889
890 #
891 # RMI Registry Serial Filter
892 #
893 # The filter pattern uses the same format as jdk.serialFilter.
894 # This filter can override the builtin filter if additional types need to be
895 # allowed or rejected from the RMI Registry.
896 #
897 #sun.rmi.registry.registryFilter=pattern;pattern
898
899 #
900 # RMI Distributed Garbage Collector (DGC) Serial Filter
901 #
902 # The filter pattern uses the same format as jdk.serialFilter.
903 # This filter can override the builtin filter if additional types need to be
904 # allowed or rejected from the RMI DGC.
905 #
906 # The builtin DGC filter can approximately be represented as the filter pattern:
907 #
908 #sun.rmi.transport.dgcFilter=\
909 # java.rmi.server.ObjID;\
910 # java.rmi.server.UID;\
911 # java.rmi.dgc.VMID;\
912 # java.rmi.dgc.Lease;\
913 # maxdepth=5;maxarray=10000