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 com.sun.activation.registries.
226
227 #
228 # List of comma-separated packages that start with or equal this string
229 # will cause a security exception to be thrown when
230 # passed to checkPackageDefinition unless the
231 # corresponding RuntimePermission ("defineClassInPackage."+package) has
232 # been granted.
233 #
234 # by default, none of the class loaders supplied with the JDK call
235 # checkPackageDefinition.
236 #
237 package.definition=sun.,\
238 com.sun.xml.internal.,\
239 com.sun.imageio.,\
240 com.sun.istack.internal.,\
241 com.sun.jmx.,\
242 com.sun.media.sound.,\
243 com.sun.naming.internal.,\
244 com.sun.proxy.,\
245 com.sun.corba.se.,\
246 com.sun.org.apache.bcel.internal.,\
247 com.sun.org.apache.regexp.internal.,\
248 com.sun.org.apache.xerces.internal.,\
249 com.sun.org.apache.xpath.internal.,\
250 com.sun.org.apache.xalan.internal.extensions.,\
251 com.sun.org.apache.xalan.internal.lib.,\
252 com.sun.org.apache.xalan.internal.res.,\
253 com.sun.org.apache.xalan.internal.templates.,\
254 com.sun.org.apache.xalan.internal.utils.,\
255 com.sun.org.apache.xalan.internal.xslt.,\
256 com.sun.org.apache.xalan.internal.xsltc.cmdline.,\
257 com.sun.org.apache.xalan.internal.xsltc.compiler.,\
258 com.sun.org.apache.xalan.internal.xsltc.trax.,\
259 com.sun.org.apache.xalan.internal.xsltc.util.,\
260 com.sun.org.apache.xml.internal.res.,\
261 com.sun.org.apache.xml.internal.resolver.helpers.,\
262 com.sun.org.apache.xml.internal.resolver.readers.,\
263 com.sun.org.apache.xml.internal.security.,\
264 com.sun.org.apache.xml.internal.serializer.utils.,\
265 com.sun.org.apache.xml.internal.utils.,\
266 com.sun.org.glassfish.,\
267 com.oracle.xmlns.internal.,\
268 com.oracle.webservices.internal.,\
269 oracle.jrockit.jfr.,\
270 org.jcp.xml.dsig.internal.,\
271 jdk.internal.,\
272 jdk.nashorn.internal.,\
273 jdk.nashorn.tools.,\
274 com.sun.activation.registries.
275
276 #
277 # Determines whether this properties file can be appended to
278 # or overridden on the command line via -Djava.security.properties
279 #
280 security.overridePropertiesFile=true
281
282 #
283 # Determines the default key and trust manager factory algorithms for
284 # the javax.net.ssl package.
285 #
286 ssl.KeyManagerFactory.algorithm=SunX509
287 ssl.TrustManagerFactory.algorithm=PKIX
288
289 #
290 # The Java-level namelookup cache policy for successful lookups:
291 #
292 # any negative value: caching forever
293 # any positive value: the number of seconds to cache an address for
294 # zero: do not cache
295 #
296 # default value is forever (FOREVER). For security reasons, this
297 # caching is made forever when a security manager is set. When a security
298 # manager is not set, the default behavior in this implementation
299 # is to cache for 30 seconds.
300 #
301 # NOTE: setting this to anything other than the default value can have
302 # serious security implications. Do not set it unless
303 # you are sure you are not exposed to DNS spoofing attack.
304 #
305 #networkaddress.cache.ttl=-1
306
307 # The Java-level namelookup cache policy for failed lookups:
308 #
309 # any negative value: cache forever
310 # any positive value: the number of seconds to cache negative lookup results
311 # zero: do not cache
312 #
313 # In some Microsoft Windows networking environments that employ
314 # the WINS name service in addition to DNS, name service lookups
315 # that fail may take a noticeably long time to return (approx. 5 seconds).
316 # For this reason the default caching policy is to maintain these
317 # results for 10 seconds.
318 #
319 #
320 networkaddress.cache.negative.ttl=10
321
322 #
323 # Properties to configure OCSP for certificate revocation checking
324 #
325
326 # Enable OCSP
327 #
328 # By default, OCSP is not used for certificate revocation checking.
329 # This property enables the use of OCSP when set to the value "true".
330 #
331 # NOTE: SocketPermission is required to connect to an OCSP responder.
332 #
333 # Example,
334 # ocsp.enable=true
335
336 #
337 # Location of the OCSP responder
338 #
339 # By default, the location of the OCSP responder is determined implicitly
340 # from the certificate being validated. This property explicitly specifies
341 # the location of the OCSP responder. The property is used when the
342 # Authority Information Access extension (defined in RFC 3280) is absent
343 # from the certificate or when it requires overriding.
344 #
345 # Example,
346 # ocsp.responderURL=http://ocsp.example.net:80
347
348 #
349 # Subject name of the OCSP responder's certificate
350 #
351 # By default, the certificate of the OCSP responder is that of the issuer
352 # of the certificate being validated. This property identifies the certificate
353 # of the OCSP responder when the default does not apply. Its value is a string
354 # distinguished name (defined in RFC 2253) which identifies a certificate in
355 # the set of certificates supplied during cert path validation. In cases where
356 # the subject name alone is not sufficient to uniquely identify the certificate
357 # then both the "ocsp.responderCertIssuerName" and
358 # "ocsp.responderCertSerialNumber" properties must be used instead. When this
359 # property is set then those two properties are ignored.
360 #
361 # Example,
362 # ocsp.responderCertSubjectName="CN=OCSP Responder, O=XYZ Corp"
363
364 #
365 # Issuer name of the OCSP responder's certificate
366 #
367 # By default, the certificate of the OCSP responder is that of the issuer
368 # of the certificate being validated. This property identifies the certificate
369 # of the OCSP responder when the default does not apply. Its value is a string
370 # distinguished name (defined in RFC 2253) which identifies a certificate in
371 # the set of certificates supplied during cert path validation. When this
372 # property is set then the "ocsp.responderCertSerialNumber" property must also
373 # be set. When the "ocsp.responderCertSubjectName" property is set then this
374 # property is ignored.
375 #
376 # Example,
377 # ocsp.responderCertIssuerName="CN=Enterprise CA, O=XYZ Corp"
378
379 #
380 # Serial number of the OCSP responder's certificate
381 #
382 # By default, the certificate of the OCSP responder is that of the issuer
383 # of the certificate being validated. This property identifies the certificate
384 # of the OCSP responder when the default does not apply. Its value is a string
385 # of hexadecimal digits (colon or space separators may be present) which
386 # identifies a certificate in the set of certificates supplied during cert path
387 # validation. When this property is set then the "ocsp.responderCertIssuerName"
388 # property must also be set. When the "ocsp.responderCertSubjectName" property
389 # is set then this property is ignored.
390 #
391 # Example,
392 # ocsp.responderCertSerialNumber=2A:FF:00
393
394 #
395 # Policy for failed Kerberos KDC lookups:
396 #
397 # When a KDC is unavailable (network error, service failure, etc), it is
398 # put inside a blacklist and accessed less often for future requests. The
399 # value (case-insensitive) for this policy can be:
400 #
401 # tryLast
402 # KDCs in the blacklist are always tried after those not on the list.
403 #
404 # tryLess[:max_retries,timeout]
405 # KDCs in the blacklist are still tried by their order in the configuration,
406 # but with smaller max_retries and timeout values. max_retries and timeout
407 # are optional numerical parameters (default 1 and 5000, which means once
408 # and 5 seconds). Please notes that if any of the values defined here is
409 # more than what is defined in krb5.conf, it will be ignored.
410 #
411 # Whenever a KDC is detected as available, it is removed from the blacklist.
412 # The blacklist is reset when krb5.conf is reloaded. You can add
413 # refreshKrb5Config=true to a JAAS configuration file so that krb5.conf is
414 # reloaded whenever a JAAS authentication is attempted.
415 #
416 # Example,
417 # krb5.kdc.bad.policy = tryLast
418 # krb5.kdc.bad.policy = tryLess:2,2000
419 krb5.kdc.bad.policy = tryLast
420
421 # Algorithm restrictions for certification path (CertPath) processing
422 #
423 # In some environments, certain algorithms or key lengths may be undesirable
424 # for certification path building and validation. For example, "MD2" is
425 # generally no longer considered to be a secure hash algorithm. This section
426 # describes the mechanism for disabling algorithms based on algorithm name
427 # and/or key length. This includes algorithms used in certificates, as well
428 # as revocation information such as CRLs and signed OCSP Responses.
429 # The syntax of the disabled algorithm string is described as follows:
430 # DisabledAlgorithms:
431 # " DisabledAlgorithm { , DisabledAlgorithm } "
432 #
433 # DisabledAlgorithm:
434 # AlgorithmName [Constraint] { '&' Constraint }
435 #
436 # AlgorithmName:
437 # (see below)
438 #
439 # Constraint:
440 # KeySizeConstraint | CAConstraint | DenyAfterConstraint |
441 # UsageConstraint
442 #
443 # KeySizeConstraint:
444 # keySize Operator KeyLength
445 #
446 # Operator:
447 # <= | < | == | != | >= | >
448 #
449 # KeyLength:
450 # Integer value of the algorithm's key length in bits
451 #
452 # CAConstraint:
453 # jdkCA
454 #
455 # DenyAfterConstraint:
456 # denyAfter YYYY-MM-DD
457 #
458 # UsageConstraint:
459 # usage [TLSServer] [TLSClient] [SignedJAR]
460 #
461 # The "AlgorithmName" is the standard algorithm name of the disabled
462 # algorithm. See "Java Cryptography Architecture Standard Algorithm Name
463 # Documentation" for information about Standard Algorithm Names. Matching
464 # is performed using a case-insensitive sub-element matching rule. (For
465 # example, in "SHA1withECDSA" the sub-elements are "SHA1" for hashing and
466 # "ECDSA" for signatures.) If the assertion "AlgorithmName" is a
467 # sub-element of the certificate algorithm name, the algorithm will be
468 # rejected during certification path building and validation. For example,
469 # the assertion algorithm name "DSA" will disable all certificate algorithms
470 # that rely on DSA, such as NONEwithDSA, SHA1withDSA. However, the assertion
471 # will not disable algorithms related to "ECDSA".
472 #
473 # A "Constraint" defines restrictions on the keys and/or certificates for
474 # a specified AlgorithmName:
475 #
476 # KeySizeConstraint:
477 # keySize Operator KeyLength
478 # The constraint requires a key of a valid size range if the
479 # "AlgorithmName" is of a key algorithm. The "KeyLength" indicates
480 # the key size specified in number of bits. For example,
481 # "RSA keySize <= 1024" indicates that any RSA key with key size less
482 # than or equal to 1024 bits should be disabled, and
483 # "RSA keySize < 1024, RSA keySize > 2048" indicates that any RSA key
484 # with key size less than 1024 or greater than 2048 should be disabled.
485 # This constraint is only used on algorithms that have a key size.
486 #
487 # CAConstraint:
488 # jdkCA
489 # This constraint prohibits the specified algorithm only if the
490 # algorithm is used in a certificate chain that terminates at a marked
491 # trust anchor in the lib/security/cacerts keystore. If the jdkCA
492 # constraint is not set, then all chains using the specified algorithm
493 # are restricted. jdkCA may only be used once in a DisabledAlgorithm
494 # expression.
495 # Example: To apply this constraint to SHA-1 certificates, include
496 # the following: "SHA1 jdkCA"
497 #
498 # DenyAfterConstraint:
499 # denyAfter YYYY-MM-DD
500 # This constraint prohibits a certificate with the specified algorithm
501 # from being used after the date regardless of the certificate's
502 # validity. JAR files that are signed and timestamped before the
503 # constraint date with certificates containing the disabled algorithm
504 # will not be restricted. The date is processed in the UTC timezone.
505 # This constraint can only be used once in a DisabledAlgorithm
506 # expression.
507 # Example: To deny usage of RSA 2048 bit certificates after Feb 3 2020,
508 # use the following: "RSA keySize == 2048 & denyAfter 2020-02-03"
509 #
510 # UsageConstraint:
511 # usage [TLSServer] [TLSClient] [SignedJAR]
512 # This constraint prohibits the specified algorithm for
513 # a specified usage. This should be used when disabling an algorithm
514 # for all usages is not practical. 'TLSServer' restricts the algorithm
515 # in TLS server certificate chains when server authentication is
516 # performed. 'TLSClient' restricts the algorithm in TLS client
517 # certificate chains when client authentication is performed.
518 # 'SignedJAR' constrains use of certificates in signed jar files.
519 # The usage type follows the keyword and more than one usage type can
520 # be specified with a whitespace delimiter.
521 # Example: "SHA1 usage TLSServer TLSClient"
522 #
523 # When an algorithm must satisfy more than one constraint, it must be
524 # delimited by an ampersand '&'. For example, to restrict certificates in a
525 # chain that terminate at a distribution provided trust anchor and contain
526 # RSA keys that are less than or equal to 1024 bits, add the following
527 # constraint: "RSA keySize <= 1024 & jdkCA".
528 #
529 # All DisabledAlgorithms expressions are processed in the order defined in the
530 # property. This requires lower keysize constraints to be specified
531 # before larger keysize constraints of the same algorithm. For example:
532 # "RSA keySize < 1024 & jdkCA, RSA keySize < 2048".
533 #
534 # Note: The algorithm restrictions do not apply to trust anchors or
535 # self-signed certificates.
536 #
537 # Note: This property is currently used by Oracle's PKIX implementation. It
538 # is not guaranteed to be examined and used by other implementations.
539 #
540 # Example:
541 # jdk.certpath.disabledAlgorithms=MD2, DSA, RSA keySize < 2048
542 #
543 #
544 jdk.certpath.disabledAlgorithms=MD2, MD5, SHA1 jdkCA & usage TLSServer, \
545 RSA keySize < 1024, DSA keySize < 1024, EC keySize < 224
546
547 #
548 # Algorithm restrictions for signed JAR files
549 #
550 # In some environments, certain algorithms or key lengths may be undesirable
551 # for signed JAR validation. For example, "MD2" is generally no longer
552 # considered to be a secure hash algorithm. This section describes the
553 # mechanism for disabling algorithms based on algorithm name and/or key length.
554 # JARs signed with any of the disabled algorithms or key sizes will be treated
555 # as unsigned.
556 #
557 # The syntax of the disabled algorithm string is described as follows:
558 # DisabledAlgorithms:
559 # " DisabledAlgorithm { , DisabledAlgorithm } "
560 #
561 # DisabledAlgorithm:
562 # AlgorithmName [Constraint] { '&' Constraint }
563 #
564 # AlgorithmName:
565 # (see below)
566 #
567 # Constraint:
568 # KeySizeConstraint | DenyAfterConstraint
569 #
570 # KeySizeConstraint:
571 # keySize Operator KeyLength
572 #
573 # DenyAfterConstraint:
574 # denyAfter YYYY-MM-DD
575 #
576 # Operator:
577 # <= | < | == | != | >= | >
578 #
579 # KeyLength:
580 # Integer value of the algorithm's key length in bits
581 #
582 # Note: This property is currently used by the JDK Reference
583 # implementation. It is not guaranteed to be examined and used by other
584 # implementations.
585 #
586 # See "jdk.certpath.disabledAlgorithms" for syntax descriptions.
587 #
588 jdk.jar.disabledAlgorithms=MD2, MD5, RSA keySize < 1024
589
590 #
591 # Algorithm restrictions for Secure Socket Layer/Transport Layer Security
592 # (SSL/TLS) processing
593 #
594 # In some environments, certain algorithms or key lengths may be undesirable
595 # when using SSL/TLS. This section describes the mechanism for disabling
596 # algorithms during SSL/TLS security parameters negotiation, including
597 # protocol version negotiation, cipher suites selection, peer authentication
598 # and key exchange mechanisms.
599 #
600 # Disabled algorithms will not be negotiated for SSL/TLS connections, even
601 # if they are enabled explicitly in an application.
602 #
603 # For PKI-based peer authentication and key exchange mechanisms, this list
604 # of disabled algorithms will also be checked during certification path
605 # building and validation, including algorithms used in certificates, as
606 # well as revocation information such as CRLs and signed OCSP Responses.
607 # This is in addition to the jdk.certpath.disabledAlgorithms property above.
608 #
609 # See the specification of "jdk.certpath.disabledAlgorithms" for the
610 # syntax of the disabled algorithm string.
611 #
612 # Note: The algorithm restrictions do not apply to trust anchors or
613 # self-signed certificates.
614 #
615 # Note: This property is currently used by the JDK Reference implementation.
616 # It is not guaranteed to be examined and used by other implementations.
617 #
618 # Example:
619 # jdk.tls.disabledAlgorithms=MD5, SSLv3, DSA, RSA keySize < 2048
620 jdk.tls.disabledAlgorithms=SSLv3, RC4, MD5withRSA, DH keySize < 768, \
621 EC keySize < 224
622
623 # Legacy algorithms for Secure Socket Layer/Transport Layer Security (SSL/TLS)
624 # processing in JSSE implementation.
625 #
626 # In some environments, a certain algorithm may be undesirable but it
627 # cannot be disabled because of its use in legacy applications. Legacy
628 # algorithms may still be supported, but applications should not use them
629 # as the security strength of legacy algorithms are usually not strong enough
630 # in practice.
631 #
632 # During SSL/TLS security parameters negotiation, legacy algorithms will
633 # not be negotiated unless there are no other candidates.
634 #
635 # The syntax of the legacy algorithms string is described as this Java
636 # BNF-style:
637 # LegacyAlgorithms:
638 # " LegacyAlgorithm { , LegacyAlgorithm } "
639 #
640 # LegacyAlgorithm:
641 # AlgorithmName (standard JSSE algorithm name)
642 #
643 # See the specification of security property "jdk.certpath.disabledAlgorithms"
644 # for the syntax and description of the "AlgorithmName" notation.
645 #
646 # Per SSL/TLS specifications, cipher suites have the form:
647 # SSL_KeyExchangeAlg_WITH_CipherAlg_MacAlg
648 # or
649 # TLS_KeyExchangeAlg_WITH_CipherAlg_MacAlg
650 #
651 # For example, the cipher suite TLS_RSA_WITH_AES_128_CBC_SHA uses RSA as the
652 # key exchange algorithm, AES_128_CBC (128 bits AES cipher algorithm in CBC
653 # mode) as the cipher (encryption) algorithm, and SHA-1 as the message digest
654 # algorithm for HMAC.
655 #
656 # The LegacyAlgorithm can be one of the following standard algorithm names:
657 # 1. JSSE cipher suite name, e.g., TLS_RSA_WITH_AES_128_CBC_SHA
658 # 2. JSSE key exchange algorithm name, e.g., RSA
659 # 3. JSSE cipher (encryption) algorithm name, e.g., AES_128_CBC
660 # 4. JSSE message digest algorithm name, e.g., SHA
661 #
662 # See SSL/TLS specifications and "Java Cryptography Architecture Standard
663 # Algorithm Name Documentation" for information about the algorithm names.
664 #
665 # Note: This property is currently used by the JDK Reference implementation.
666 # It is not guaranteed to be examined and used by other implementations.
667 # There is no guarantee the property will continue to exist or be of the
668 # same syntax in future releases.
669 #
670 # Example:
671 # jdk.tls.legacyAlgorithms=DH_anon, DES_CBC, SSL_RSA_WITH_RC4_128_MD5
672 #
673 jdk.tls.legacyAlgorithms= \
674 K_NULL, C_NULL, M_NULL, \
675 DHE_DSS_EXPORT, DHE_RSA_EXPORT, DH_anon_EXPORT, DH_DSS_EXPORT, \
676 DH_RSA_EXPORT, RSA_EXPORT, \
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 #
739 # The policy for the XML Signature secure validation mode. The mode is
740 # enabled by setting the property "org.jcp.xml.dsig.secureValidation" to
741 # true with the javax.xml.crypto.XMLCryptoContext.setProperty() method,
742 # or by running the code with a SecurityManager.
743 #
744 # Policy:
745 # Constraint {"," Constraint }
746 # Constraint:
747 # AlgConstraint | MaxTransformsConstraint | MaxReferencesConstraint |
748 # ReferenceUriSchemeConstraint | KeySizeConstraint | OtherConstraint
749 # AlgConstraint
750 # "disallowAlg" Uri
751 # MaxTransformsConstraint:
752 # "maxTransforms" Integer
753 # MaxReferencesConstraint:
754 # "maxReferences" Integer
755 # ReferenceUriSchemeConstraint:
756 # "disallowReferenceUriSchemes" String { String }
757 # KeySizeConstraint:
758 # "minKeySize" KeyAlg Integer
759 # OtherConstraint:
760 # "noDuplicateIds" | "noRetrievalMethodLoops"
761 #
762 # For AlgConstraint, Uri is the algorithm URI String that is not allowed.
763 # See the XML Signature Recommendation for more information on algorithm
764 # URI Identifiers. For KeySizeConstraint, KeyAlg is the standard algorithm
765 # name of the key type (ex: "RSA"). If the MaxTransformsConstraint,
766 # MaxReferencesConstraint or KeySizeConstraint (for the same key type) is
767 # specified more than once, only the last entry is enforced.
768 #
769 # Note: This property is currently used by the JDK Reference implementation. It
770 # is not guaranteed to be examined and used by other implementations.
771 #
772 jdk.xml.dsig.secureValidationPolicy=\
773 disallowAlg http://www.w3.org/TR/1999/REC-xslt-19991116,\
774 disallowAlg http://www.w3.org/2001/04/xmldsig-more#rsa-md5,\
775 disallowAlg http://www.w3.org/2001/04/xmldsig-more#hmac-md5,\
776 disallowAlg http://www.w3.org/2001/04/xmldsig-more#md5,\
777 maxTransforms 5,\
778 maxReferences 30,\
779 disallowReferenceUriSchemes file http https,\
780 minKeySize RSA 1024,\
781 minKeySize DSA 1024,\
782 noDuplicateIds,\
783 noRetrievalMethodLoops
784
785 #
786 # Serialization process-wide filter
787 #
788 # A filter, if configured, is used by java.io.ObjectInputStream during
789 # deserialization to check the contents of the stream.
790 # A filter is configured as a sequence of patterns, each pattern is either
791 # matched against the name of a class in the stream or defines a limit.
792 # Patterns are separated by ";" (semicolon).
793 # Whitespace is significant and is considered part of the pattern.
794 #
795 # If a pattern includes a "=", it sets a limit.
796 # If a limit appears more than once the last value is used.
797 # Limits are checked before classes regardless of the order in the sequence of patterns.
798 # If any of the limits are exceeded, the filter status is REJECTED.
799 #
800 # maxdepth=value - the maximum depth of a graph
801 # maxrefs=value - the maximum number of internal references
802 # maxbytes=value - the maximum number of bytes in the input stream
803 # maxarray=value - the maximum array length allowed
804 #
805 # Other patterns, from left to right, match the class or package name as
806 # returned from Class.getName.
807 # If the class is an array type, the class or package to be matched is the element type.
808 # Arrays of any number of dimensions are treated the same as the element type.
809 # For example, a pattern of "!example.Foo", rejects creation of any instance or
810 # array of example.Foo.
811 #
812 # If the pattern starts with "!", the status is REJECTED if the remaining pattern
813 # is matched; otherwise the status is ALLOWED if the pattern matches.
814 # If the pattern ends with ".**" it matches any class in the package and all subpackages.
815 # If the pattern ends with ".*" it matches any class in the package.
816 # If the pattern ends with "*", it matches any class with the pattern as a prefix.
817 # If the pattern is equal to the class name, it matches.
818 # Otherwise, the status is UNDECIDED.
819 #
820 #jdk.serialFilter=pattern;pattern
821
822 #
823 # RMI Registry Serial Filter
824 #
825 # The filter pattern uses the same format as jdk.serialFilter.
826 # This filter can override the builtin filter if additional types need to be
827 # allowed or rejected from the RMI Registry.
828 #
829 #sun.rmi.registry.registryFilter=pattern;pattern
830
831 #
832 # RMI Distributed Garbage Collector (DGC) Serial Filter
833 #
834 # The filter pattern uses the same format as jdk.serialFilter.
835 # This filter can override the builtin filter if additional types need to be
836 # allowed or rejected from the RMI DGC.
837 #
838 # The builtin DGC filter can approximately be represented as the filter pattern:
839 #
840 #sun.rmi.transport.dgcFilter=\
841 # java.rmi.server.ObjID;\
842 # java.rmi.server.UID;\
843 # java.rmi.dgc.VMID;\
844 # java.rmi.dgc.Lease;\
845 # maxdepth=5;maxarray=10000