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