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 jdk.xml.internal.,\
227 com.sun.activation.registries.,\
228 com.sun.java.accessibility.
229
230 #
231 # List of comma-separated packages that start with or equal this string
232 # will cause a security exception to be thrown when
233 # passed to checkPackageDefinition unless the
234 # corresponding RuntimePermission ("defineClassInPackage."+package) has
235 # been granted.
236 #
237 # by default, none of the class loaders supplied with the JDK call
238 # checkPackageDefinition.
239 #
240 package.definition=sun.,\
241 com.sun.xml.internal.,\
242 com.sun.imageio.,\
243 com.sun.istack.internal.,\
244 com.sun.jmx.,\
245 com.sun.media.sound.,\
246 com.sun.naming.internal.,\
247 com.sun.proxy.,\
248 com.sun.corba.se.,\
249 com.sun.org.apache.bcel.internal.,\
250 com.sun.org.apache.regexp.internal.,\
251 com.sun.org.apache.xerces.internal.,\
252 com.sun.org.apache.xpath.internal.,\
253 com.sun.org.apache.xalan.internal.extensions.,\
254 com.sun.org.apache.xalan.internal.lib.,\
255 com.sun.org.apache.xalan.internal.res.,\
256 com.sun.org.apache.xalan.internal.templates.,\
257 com.sun.org.apache.xalan.internal.utils.,\
258 com.sun.org.apache.xalan.internal.xslt.,\
259 com.sun.org.apache.xalan.internal.xsltc.cmdline.,\
260 com.sun.org.apache.xalan.internal.xsltc.compiler.,\
261 com.sun.org.apache.xalan.internal.xsltc.trax.,\
262 com.sun.org.apache.xalan.internal.xsltc.util.,\
263 com.sun.org.apache.xml.internal.res.,\
264 com.sun.org.apache.xml.internal.resolver.helpers.,\
265 com.sun.org.apache.xml.internal.resolver.readers.,\
266 com.sun.org.apache.xml.internal.security.,\
267 com.sun.org.apache.xml.internal.serializer.utils.,\
268 com.sun.org.apache.xml.internal.utils.,\
269 com.sun.org.glassfish.,\
270 com.oracle.xmlns.internal.,\
271 com.oracle.webservices.internal.,\
272 oracle.jrockit.jfr.,\
273 org.jcp.xml.dsig.internal.,\
274 jdk.internal.,\
275 jdk.nashorn.internal.,\
276 jdk.nashorn.tools.,\
277 jdk.xml.internal.,\
278 com.sun.activation.registries.,\
279 com.sun.java.accessibility.
280
281 #
282 # Determines whether this properties file can be appended to
283 # or overridden on the command line via -Djava.security.properties
284 #
285 security.overridePropertiesFile=true
286
287 #
288 # Determines the default key and trust manager factory algorithms for
289 # the javax.net.ssl package.
290 #
291 ssl.KeyManagerFactory.algorithm=SunX509
292 ssl.TrustManagerFactory.algorithm=PKIX
293
294 #
295 # The Java-level namelookup cache policy for successful lookups:
296 #
297 # any negative value: caching forever
298 # any positive value: the number of seconds to cache an address for
299 # zero: do not cache
300 #
301 # default value is forever (FOREVER). For security reasons, this
302 # caching is made forever when a security manager is set. When a security
303 # manager is not set, the default behavior in this implementation
304 # is to cache for 30 seconds.
305 #
306 # NOTE: setting this to anything other than the default value can have
307 # serious security implications. Do not set it unless
308 # you are sure you are not exposed to DNS spoofing attack.
309 #
310 #networkaddress.cache.ttl=-1
311
312 # The Java-level namelookup cache policy for failed lookups:
313 #
314 # any negative value: cache forever
315 # any positive value: the number of seconds to cache negative lookup results
316 # zero: do not cache
317 #
318 # In some Microsoft Windows networking environments that employ
319 # the WINS name service in addition to DNS, name service lookups
320 # that fail may take a noticeably long time to return (approx. 5 seconds).
321 # For this reason the default caching policy is to maintain these
322 # results for 10 seconds.
323 #
324 #
325 networkaddress.cache.negative.ttl=10
326
327 #
328 # Properties to configure OCSP for certificate revocation checking
329 #
330
331 # Enable OCSP
332 #
333 # By default, OCSP is not used for certificate revocation checking.
334 # This property enables the use of OCSP when set to the value "true".
335 #
336 # NOTE: SocketPermission is required to connect to an OCSP responder.
337 #
338 # Example,
339 # ocsp.enable=true
340
341 #
342 # Location of the OCSP responder
343 #
344 # By default, the location of the OCSP responder is determined implicitly
345 # from the certificate being validated. This property explicitly specifies
346 # the location of the OCSP responder. The property is used when the
347 # Authority Information Access extension (defined in RFC 3280) is absent
348 # from the certificate or when it requires overriding.
349 #
350 # Example,
351 # ocsp.responderURL=http://ocsp.example.net:80
352
353 #
354 # Subject name of the OCSP responder's certificate
355 #
356 # By default, the certificate of the OCSP responder is that of the issuer
357 # of the certificate being validated. This property identifies the certificate
358 # of the OCSP responder when the default does not apply. Its value is a string
359 # distinguished name (defined in RFC 2253) which identifies a certificate in
360 # the set of certificates supplied during cert path validation. In cases where
361 # the subject name alone is not sufficient to uniquely identify the certificate
362 # then both the "ocsp.responderCertIssuerName" and
363 # "ocsp.responderCertSerialNumber" properties must be used instead. When this
364 # property is set then those two properties are ignored.
365 #
366 # Example,
367 # ocsp.responderCertSubjectName="CN=OCSP Responder, O=XYZ Corp"
368
369 #
370 # Issuer name of the OCSP responder's certificate
371 #
372 # By default, the certificate of the OCSP responder is that of the issuer
373 # of the certificate being validated. This property identifies the certificate
374 # of the OCSP responder when the default does not apply. Its value is a string
375 # distinguished name (defined in RFC 2253) which identifies a certificate in
376 # the set of certificates supplied during cert path validation. When this
377 # property is set then the "ocsp.responderCertSerialNumber" property must also
378 # be set. When the "ocsp.responderCertSubjectName" property is set then this
379 # property is ignored.
380 #
381 # Example,
382 # ocsp.responderCertIssuerName="CN=Enterprise CA, O=XYZ Corp"
383
384 #
385 # Serial number of the OCSP responder's certificate
386 #
387 # By default, the certificate of the OCSP responder is that of the issuer
388 # of the certificate being validated. This property identifies the certificate
389 # of the OCSP responder when the default does not apply. Its value is a string
390 # of hexadecimal digits (colon or space separators may be present) which
391 # identifies a certificate in the set of certificates supplied during cert path
392 # validation. When this property is set then the "ocsp.responderCertIssuerName"
393 # property must also be set. When the "ocsp.responderCertSubjectName" property
394 # is set then this property is ignored.
395 #
396 # Example,
397 # ocsp.responderCertSerialNumber=2A:FF:00
398
399 #
400 # Policy for failed Kerberos KDC lookups:
401 #
402 # When a KDC is unavailable (network error, service failure, etc), it is
403 # put inside a blacklist and accessed less often for future requests. The
404 # value (case-insensitive) for this policy can be:
405 #
406 # tryLast
407 # KDCs in the blacklist are always tried after those not on the list.
408 #
409 # tryLess[:max_retries,timeout]
410 # KDCs in the blacklist are still tried by their order in the configuration,
411 # but with smaller max_retries and timeout values. max_retries and timeout
412 # are optional numerical parameters (default 1 and 5000, which means once
413 # and 5 seconds). Please notes that if any of the values defined here is
414 # more than what is defined in krb5.conf, it will be ignored.
415 #
416 # Whenever a KDC is detected as available, it is removed from the blacklist.
417 # The blacklist is reset when krb5.conf is reloaded. You can add
418 # refreshKrb5Config=true to a JAAS configuration file so that krb5.conf is
419 # reloaded whenever a JAAS authentication is attempted.
420 #
421 # Example,
422 # krb5.kdc.bad.policy = tryLast
423 # krb5.kdc.bad.policy = tryLess:2,2000
424 krb5.kdc.bad.policy = tryLast
425
426 # Algorithm restrictions for certification path (CertPath) processing
427 #
428 # In some environments, certain algorithms or key lengths may be undesirable
429 # for certification path building and validation. For example, "MD2" is
430 # generally no longer considered to be a secure hash algorithm. This section
431 # describes the mechanism for disabling algorithms based on algorithm name
432 # and/or key length. This includes algorithms used in certificates, as well
433 # as revocation information such as CRLs and signed OCSP Responses.
434 # The syntax of the disabled algorithm string is described as follows:
435 # DisabledAlgorithms:
436 # " DisabledAlgorithm { , DisabledAlgorithm } "
437 #
438 # DisabledAlgorithm:
439 # AlgorithmName [Constraint] { '&' Constraint }
440 #
441 # AlgorithmName:
442 # (see below)
443 #
444 # Constraint:
445 # KeySizeConstraint | CAConstraint | DenyAfterConstraint |
446 # UsageConstraint
447 #
448 # KeySizeConstraint:
449 # keySize Operator KeyLength
450 #
451 # Operator:
452 # <= | < | == | != | >= | >
453 #
454 # KeyLength:
455 # Integer value of the algorithm's key length in bits
456 #
457 # CAConstraint:
458 # jdkCA
459 #
460 # DenyAfterConstraint:
461 # denyAfter YYYY-MM-DD
462 #
463 # UsageConstraint:
464 # usage [TLSServer] [TLSClient] [SignedJAR]
465 #
466 # The "AlgorithmName" is the standard algorithm name of the disabled
467 # algorithm. See "Java Cryptography Architecture Standard Algorithm Name
468 # Documentation" for information about Standard Algorithm Names. Matching
469 # is performed using a case-insensitive sub-element matching rule. (For
470 # example, in "SHA1withECDSA" the sub-elements are "SHA1" for hashing and
471 # "ECDSA" for signatures.) If the assertion "AlgorithmName" is a
472 # sub-element of the certificate algorithm name, the algorithm will be
473 # rejected during certification path building and validation. For example,
474 # the assertion algorithm name "DSA" will disable all certificate algorithms
475 # that rely on DSA, such as NONEwithDSA, SHA1withDSA. However, the assertion
476 # will not disable algorithms related to "ECDSA".
477 #
478 # A "Constraint" defines restrictions on the keys and/or certificates for
479 # a specified AlgorithmName:
480 #
481 # KeySizeConstraint:
482 # keySize Operator KeyLength
483 # The constraint requires a key of a valid size range if the
484 # "AlgorithmName" is of a key algorithm. The "KeyLength" indicates
485 # the key size specified in number of bits. For example,
486 # "RSA keySize <= 1024" indicates that any RSA key with key size less
487 # than or equal to 1024 bits should be disabled, and
488 # "RSA keySize < 1024, RSA keySize > 2048" indicates that any RSA key
489 # with key size less than 1024 or greater than 2048 should be disabled.
490 # This constraint is only used on algorithms that have a key size.
491 #
492 # CAConstraint:
493 # jdkCA
494 # This constraint prohibits the specified algorithm only if the
495 # algorithm is used in a certificate chain that terminates at a marked
496 # trust anchor in the lib/security/cacerts keystore. If the jdkCA
497 # constraint is not set, then all chains using the specified algorithm
498 # are restricted. jdkCA may only be used once in a DisabledAlgorithm
499 # expression.
500 # Example: To apply this constraint to SHA-1 certificates, include
501 # the following: "SHA1 jdkCA"
502 #
503 # DenyAfterConstraint:
504 # denyAfter YYYY-MM-DD
505 # This constraint prohibits a certificate with the specified algorithm
506 # from being used after the date regardless of the certificate's
507 # validity. JAR files that are signed and timestamped before the
508 # constraint date with certificates containing the disabled algorithm
509 # will not be restricted. The date is processed in the UTC timezone.
510 # This constraint can only be used once in a DisabledAlgorithm
511 # expression.
512 # Example: To deny usage of RSA 2048 bit certificates after Feb 3 2020,
513 # use the following: "RSA keySize == 2048 & denyAfter 2020-02-03"
514 #
515 # UsageConstraint:
516 # usage [TLSServer] [TLSClient] [SignedJAR]
517 # This constraint prohibits the specified algorithm for
518 # a specified usage. This should be used when disabling an algorithm
519 # for all usages is not practical. 'TLSServer' restricts the algorithm
520 # in TLS server certificate chains when server authentication is
521 # performed. 'TLSClient' restricts the algorithm in TLS client
522 # certificate chains when client authentication is performed.
523 # 'SignedJAR' constrains use of certificates in signed jar files.
524 # The usage type follows the keyword and more than one usage type can
525 # be specified with a whitespace delimiter.
526 # Example: "SHA1 usage TLSServer TLSClient"
527 #
528 # When an algorithm must satisfy more than one constraint, it must be
529 # delimited by an ampersand '&'. For example, to restrict certificates in a
530 # chain that terminate at a distribution provided trust anchor and contain
531 # RSA keys that are less than or equal to 1024 bits, add the following
532 # constraint: "RSA keySize <= 1024 & jdkCA".
533 #
534 # All DisabledAlgorithms expressions are processed in the order defined in the
535 # property. This requires lower keysize constraints to be specified
536 # before larger keysize constraints of the same algorithm. For example:
537 # "RSA keySize < 1024 & jdkCA, RSA keySize < 2048".
538 #
539 # Note: The algorithm restrictions do not apply to trust anchors or
540 # self-signed certificates.
541 #
542 # Note: This property is currently used by Oracle's PKIX implementation. It
543 # is not guaranteed to be examined and used by other implementations.
544 #
545 # Example:
546 # jdk.certpath.disabledAlgorithms=MD2, DSA, RSA keySize < 2048
547 #
548 #
549 jdk.certpath.disabledAlgorithms=MD2, MD5, SHA1 jdkCA & usage TLSServer, \
550 RSA keySize < 1024, DSA keySize < 1024, EC keySize < 224
551
552 #
553 # Algorithm restrictions for signed JAR files
554 #
555 # In some environments, certain algorithms or key lengths may be undesirable
556 # for signed JAR validation. For example, "MD2" is generally no longer
557 # considered to be a secure hash algorithm. This section describes the
558 # mechanism for disabling algorithms based on algorithm name and/or key length.
559 # JARs signed with any of the disabled algorithms or key sizes will be treated
560 # as unsigned.
561 #
562 # The syntax of the disabled algorithm string is described as follows:
563 # DisabledAlgorithms:
564 # " DisabledAlgorithm { , DisabledAlgorithm } "
565 #
566 # DisabledAlgorithm:
567 # AlgorithmName [Constraint] { '&' Constraint }
568 #
569 # AlgorithmName:
570 # (see below)
571 #
572 # Constraint:
573 # KeySizeConstraint | DenyAfterConstraint
574 #
575 # KeySizeConstraint:
576 # keySize Operator KeyLength
577 #
578 # DenyAfterConstraint:
579 # denyAfter YYYY-MM-DD
580 #
581 # Operator:
582 # <= | < | == | != | >= | >
583 #
584 # KeyLength:
585 # Integer value of the algorithm's key length in bits
586 #
587 # Note: This property is currently used by the JDK Reference
588 # implementation. It is not guaranteed to be examined and used by other
589 # implementations.
590 #
591 # See "jdk.certpath.disabledAlgorithms" for syntax descriptions.
592 #
593 jdk.jar.disabledAlgorithms=MD2, MD5, RSA keySize < 1024, DSA keySize < 1024
594
595 #
596 # Algorithm restrictions for Secure Socket Layer/Transport Layer Security
597 # (SSL/TLS) processing
598 #
599 # In some environments, certain algorithms or key lengths may be undesirable
600 # when using SSL/TLS. This section describes the mechanism for disabling
601 # algorithms during SSL/TLS security parameters negotiation, including
602 # protocol version negotiation, cipher suites selection, peer authentication
603 # and key exchange mechanisms.
604 #
605 # Disabled algorithms will not be negotiated for SSL/TLS connections, even
606 # if they are enabled explicitly in an application.
607 #
608 # For PKI-based peer authentication and key exchange mechanisms, this list
609 # of disabled algorithms will also be checked during certification path
610 # building and validation, including algorithms used in certificates, as
611 # well as revocation information such as CRLs and signed OCSP Responses.
612 # This is in addition to the jdk.certpath.disabledAlgorithms property above.
613 #
614 # See the specification of "jdk.certpath.disabledAlgorithms" for the
615 # syntax of the disabled algorithm string.
616 #
617 # Note: The algorithm restrictions do not apply to trust anchors or
618 # self-signed certificates.
619 #
620 # Note: This property is currently used by the JDK Reference implementation.
621 # It is not guaranteed to be examined and used by other implementations.
622 #
623 # Example:
624 # jdk.tls.disabledAlgorithms=MD5, SSLv3, DSA, RSA keySize < 2048
625 jdk.tls.disabledAlgorithms=SSLv3, RC4, DES, MD5withRSA, DH keySize < 1024, \
626 EC keySize < 224, 3DES_EDE_CBC, anon, NULL
627
628 # Legacy algorithms for Secure Socket Layer/Transport Layer Security (SSL/TLS)
629 # processing in JSSE implementation.
630 #
631 # In some environments, a certain algorithm may be undesirable but it
632 # cannot be disabled because of its use in legacy applications. Legacy
633 # algorithms may still be supported, but applications should not use them
634 # as the security strength of legacy algorithms are usually not strong enough
635 # in practice.
636 #
637 # During SSL/TLS security parameters negotiation, legacy algorithms will
638 # not be negotiated unless there are no other candidates.
639 #
640 # The syntax of the legacy algorithms string is described as this Java
641 # BNF-style:
642 # LegacyAlgorithms:
643 # " LegacyAlgorithm { , LegacyAlgorithm } "
644 #
645 # LegacyAlgorithm:
646 # AlgorithmName (standard JSSE algorithm name)
647 #
648 # See the specification of security property "jdk.certpath.disabledAlgorithms"
649 # for the syntax and description of the "AlgorithmName" notation.
650 #
651 # Per SSL/TLS specifications, cipher suites have the form:
652 # SSL_KeyExchangeAlg_WITH_CipherAlg_MacAlg
653 # or
654 # TLS_KeyExchangeAlg_WITH_CipherAlg_MacAlg
655 #
656 # For example, the cipher suite TLS_RSA_WITH_AES_128_CBC_SHA uses RSA as the
657 # key exchange algorithm, AES_128_CBC (128 bits AES cipher algorithm in CBC
658 # mode) as the cipher (encryption) algorithm, and SHA-1 as the message digest
659 # algorithm for HMAC.
660 #
661 # The LegacyAlgorithm can be one of the following standard algorithm names:
662 # 1. JSSE cipher suite name, e.g., TLS_RSA_WITH_AES_128_CBC_SHA
663 # 2. JSSE key exchange algorithm name, e.g., RSA
664 # 3. JSSE cipher (encryption) algorithm name, e.g., AES_128_CBC
665 # 4. JSSE message digest algorithm name, e.g., SHA
666 #
667 # See SSL/TLS specifications and "Java Cryptography Architecture Standard
668 # Algorithm Name Documentation" for information about the algorithm names.
669 #
670 # Note: This property is currently used by the JDK Reference implementation.
671 # It is not guaranteed to be examined and used by other implementations.
672 # There is no guarantee the property will continue to exist or be of the
673 # same syntax in future releases.
674 #
675 # Example:
676 # jdk.tls.legacyAlgorithms=DH_anon, DES_CBC, SSL_RSA_WITH_RC4_128_MD5
677 #
678 jdk.tls.legacyAlgorithms= \
679 K_NULL, C_NULL, M_NULL, \
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 # Import and export control rules on cryptographic software vary from
744 # country to country. By default, the JDK provides two different sets of
745 # cryptographic policy files:
746 #
747 # unlimited: These policy files contain no restrictions on cryptographic
748 # strengths or algorithms.
749 #
750 # limited: These policy files contain more restricted cryptographic
751 # strengths, and are still available if your country or
752 # usage requires the traditional restrictive policy.
753 #
754 # The JDK JCE framework uses the unlimited policy files by default.
755 # However the user may explicitly choose a set either by defining the
756 # "crypto.policy" Security property or by installing valid JCE policy
757 # jar files into the traditional JDK installation location. To better
758 # support older JDK Update releases, the "crypto.policy" property is not
759 # defined by default. See below for more information.
760 #
761 # The following logic determines which policy files are used:
762 #
763 # <java-home> refers to the directory where the JRE was
764 # installed and may be determined using the "java.home"
765 # System property.
766 #
767 # 1. If the Security property "crypto.policy" has been defined,
768 # then the following mechanism is used:
769 #
770 # The policy files are stored as jar files in subdirectories of
771 # <java-home>/lib/security/policy. Each directory contains a complete
772 # set of policy files.
773 #
774 # The "crypto.policy" Security property controls the directory
775 # selection, and thus the effective cryptographic policy.
776 #
777 # The default set of directories is:
778 #
779 # limited | unlimited
780 #
781 # 2. If the "crypto.policy" property is not set and the traditional
782 # US_export_policy.jar and local_policy.jar files
783 # (e.g. limited/unlimited) are found in the legacy
784 # <java-home>/lib/security directory, then the rules embedded within
785 # those jar files will be used. This helps preserve compatibility
786 # for users upgrading from an older installation.
787 #
788 # 3. If the jar files are not present in the legacy location
789 # and the "crypto.policy" Security property is not defined,
790 # then the JDK will use the unlimited settings (equivalent to
791 # crypto.policy=unlimited)
792 #
793 # Please see the JCA documentation for additional information on these
794 # files and formats.
795 #
796 # YOU ARE ADVISED TO CONSULT YOUR EXPORT/IMPORT CONTROL COUNSEL OR ATTORNEY
797 # TO DETERMINE THE EXACT REQUIREMENTS.
798 #
799 # Please note that the JCE for Java SE, including the JCE framework,
800 # cryptographic policy files, and standard JCE providers provided with
801 # the Java SE, have been reviewed and approved for export as mass market
802 # encryption item by the US Bureau of Industry and Security.
803 #
804 # Note: This property is currently used by the JDK Reference implementation.
805 # It is not guaranteed to be examined and used by other implementations.
806 #
807 #crypto.policy=unlimited
808
809 #
810 # The policy for the XML Signature secure validation mode. The mode is
811 # enabled by setting the property "org.jcp.xml.dsig.secureValidation" to
812 # true with the javax.xml.crypto.XMLCryptoContext.setProperty() method,
813 # or by running the code with a SecurityManager.
814 #
815 # Policy:
816 # Constraint {"," Constraint }
817 # Constraint:
818 # AlgConstraint | MaxTransformsConstraint | MaxReferencesConstraint |
819 # ReferenceUriSchemeConstraint | KeySizeConstraint | OtherConstraint
820 # AlgConstraint
821 # "disallowAlg" Uri
822 # MaxTransformsConstraint:
823 # "maxTransforms" Integer
824 # MaxReferencesConstraint:
825 # "maxReferences" Integer
826 # ReferenceUriSchemeConstraint:
827 # "disallowReferenceUriSchemes" String { String }
828 # KeySizeConstraint:
829 # "minKeySize" KeyAlg Integer
830 # OtherConstraint:
831 # "noDuplicateIds" | "noRetrievalMethodLoops"
832 #
833 # For AlgConstraint, Uri is the algorithm URI String that is not allowed.
834 # See the XML Signature Recommendation for more information on algorithm
835 # URI Identifiers. For KeySizeConstraint, KeyAlg is the standard algorithm
836 # name of the key type (ex: "RSA"). If the MaxTransformsConstraint,
837 # MaxReferencesConstraint or KeySizeConstraint (for the same key type) is
838 # specified more than once, only the last entry is enforced.
839 #
840 # Note: This property is currently used by the JDK Reference implementation. It
841 # is not guaranteed to be examined and used by other implementations.
842 #
843 jdk.xml.dsig.secureValidationPolicy=\
844 disallowAlg http://www.w3.org/TR/1999/REC-xslt-19991116,\
845 disallowAlg http://www.w3.org/2001/04/xmldsig-more#rsa-md5,\
846 disallowAlg http://www.w3.org/2001/04/xmldsig-more#hmac-md5,\
847 disallowAlg http://www.w3.org/2001/04/xmldsig-more#md5,\
848 maxTransforms 5,\
849 maxReferences 30,\
850 disallowReferenceUriSchemes file http https,\
851 minKeySize RSA 1024,\
852 minKeySize DSA 1024,\
853 minKeySize EC 224,\
854 noDuplicateIds,\
855 noRetrievalMethodLoops
856
857 #
858 # Serialization process-wide filter
859 #
860 # A filter, if configured, is used by java.io.ObjectInputStream during
861 # deserialization to check the contents of the stream.
862 # A filter is configured as a sequence of patterns, each pattern is either
863 # matched against the name of a class in the stream or defines a limit.
864 # Patterns are separated by ";" (semicolon).
865 # Whitespace is significant and is considered part of the pattern.
866 #
867 # If the system property jdk.serialFilter is also specified, it supersedes
868 # the security property value defined here.
869 #
870 # If a pattern includes a "=", it sets a limit.
871 # If a limit appears more than once the last value is used.
872 # Limits are checked before classes regardless of the order in the sequence of patterns.
873 # If any of the limits are exceeded, the filter status is REJECTED.
874 #
875 # maxdepth=value - the maximum depth of a graph
876 # maxrefs=value - the maximum number of internal references
877 # maxbytes=value - the maximum number of bytes in the input stream
878 # maxarray=value - the maximum array length allowed
879 #
880 # Other patterns, from left to right, match the class or package name as
881 # returned from Class.getName.
882 # If the class is an array type, the class or package to be matched is the element type.
883 # Arrays of any number of dimensions are treated the same as the element type.
884 # For example, a pattern of "!example.Foo", rejects creation of any instance or
885 # array of example.Foo.
886 #
887 # If the pattern starts with "!", the status is REJECTED if the remaining pattern
888 # is matched; otherwise the status is ALLOWED if the pattern matches.
889 # If the pattern ends with ".**" it matches any class in the package and all subpackages.
890 # If the pattern ends with ".*" it matches any class in the package.
891 # If the pattern ends with "*", it matches any class with the pattern as a prefix.
892 # If the pattern is equal to the class name, it matches.
893 # Otherwise, the status is UNDECIDED.
894 #
895 #jdk.serialFilter=pattern;pattern
896
897 #
898 # RMI Registry Serial Filter
899 #
900 # The filter pattern uses the same format as jdk.serialFilter.
901 # This filter can override the builtin filter if additional types need to be
902 # allowed or rejected from the RMI Registry or to decrease limits but not
903 # to increase limits.
904 # If the limits (maxdepth, maxrefs, or maxbytes) are exceeded, the object is rejected.
905 #
906 # Each non-array type is allowed or rejected if it matches one of the patterns,
907 # evaluated from left to right, and is otherwise allowed. Arrays of any
908 # component type, including subarrays and arrays of primitives, are allowed.
909 #
910 # Array construction of any component type, including subarrays and arrays of
911 # primitives, are allowed unless the length is greater than the maxarray limit.
912 # The filter is applied to each array element.
913 #
914 # The built-in filter allows subclasses of allowed classes and
915 # can approximately be represented as the pattern:
916 #
917 #sun.rmi.registry.registryFilter=\
918 # maxarray=1000000;\
919 # maxdepth=20;\
920 # java.lang.String;\
921 # java.lang.Number;\
922 # java.lang.reflect.Proxy;\
923 # java.rmi.Remote;\
924 # sun.rmi.server.UnicastRef;\
925 # sun.rmi.server.RMIClientSocketFactory;\
926 # sun.rmi.server.RMIServerSocketFactory;\
927 # java.rmi.activation.ActivationID;\
928 # java.rmi.server.UID
929 #
930 # RMI Distributed Garbage Collector (DGC) Serial Filter
931 #
932 # The filter pattern uses the same format as jdk.serialFilter.
933 # This filter can override the builtin filter if additional types need to be
934 # allowed or rejected from the RMI DGC.
935 #
936 # The builtin DGC filter can approximately be represented as the filter pattern:
937 #
938 #sun.rmi.transport.dgcFilter=\
939 # java.rmi.server.ObjID;\
940 # java.rmi.server.UID;\
941 # java.rmi.dgc.VMID;\
942 # java.rmi.dgc.Lease;\
943 # maxdepth=5;maxarray=10000
944
945 # CORBA ORBIorTypeCheckRegistryFilter
946 # Type check enhancement for ORB::string_to_object processing
947 #
948 # An IOR type check filter, if configured, is used by an ORB during
949 # an ORB::string_to_object invocation to check the veracity of the type encoded
950 # in the ior string.
951 #
952 # The filter pattern consists of a semi-colon separated list of class names.
953 # The configured list contains the binary class names of the IDL interface types
954 # corresponding to the IDL stub class to be instantiated.
955 # As such, a filter specifies a list of IDL stub classes that will be
956 # allowed by an ORB when an ORB::string_to_object is invoked.
957 # It is used to specify a white list configuration of acceptable
958 # IDL stub types which may be contained in a stringified IOR
959 # parameter passed as input to an ORB::string_to_object method.
960 #
961 # Note: This property is currently used by the JDK Reference implementation.
962 # It is not guaranteed to be examined and used by other implementations.
963 #
964 #com.sun.CORBA.ORBIorTypeCheckRegistryFilter=binary_class_name;binary_class_name
965
966 #
967 # JCEKS Encrypted Key Serial Filter
968 #
969 # This filter, if configured, is used by the JCEKS KeyStore during the
970 # deserialization of the encrypted Key object stored inside a key entry.
971 # If not configured or the filter result is UNDECIDED (i.e. none of the patterns
972 # matches), the filter configured by jdk.serialFilter will be consulted.
973 #
974 # If the system property jceks.key.serialFilter is also specified, it supersedes
975 # the security property value defined here.
976 #
977 # The filter pattern uses the same format as jdk.serialFilter. The default
978 # pattern allows java.lang.Enum, java.security.KeyRep, java.security.KeyRep$Type,
979 # and javax.crypto.spec.SecretKeySpec and rejects all the others.
980 jceks.key.serialFilter = java.lang.Enum;java.security.KeyRep;\
981 java.security.KeyRep$Type;javax.crypto.spec.SecretKeySpec;!*
982
983 #
984 # Policies for distrusting Certificate Authorities (CAs).
985 #
986 # This is a comma separated value of one or more case-sensitive strings, each
987 # of which represents a policy for determining if a CA should be distrusted.
988 # The supported values are:
989 #
990 # SYMANTEC_TLS : Distrust TLS Server certificates anchored by
991 # a Symantec root CA and issued after April 16, 2019.
992 #
993 # Leading and trailing whitespace surrounding each value are ignored.
994 # Unknown values are ignored. If the property is commented out or set to the
995 # empty String, no policies are enforced.
996 #
997 # Note: This property is currently used by the JDK Reference implementation.
998 # It is not guaranteed to be supported by other SE implementations. Also, this
999 # property does not override other security properties which can restrict
1000 # certificates such as jdk.tls.disabledAlgorithms or
1001 # jdk.certpath.disabledAlgorithms; those restrictions are still enforced even
1002 # if this property is not enabled.
1003 #
1004 jdk.security.caDistrustPolicies=SYMANTEC_TLS