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