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