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