1 # 2 # This is the "master security properties file". 3 # 4 # An alternate java.security properties file may be specified 5 # from the command line via the system property 6 # 7 # -Djava.security.properties=<URL> 8 # 9 # This properties file appends to the master security properties file. 10 # If both properties files specify values for the same key, the value 11 # from the command-line properties file is selected, as it is the last 12 # one loaded. 13 # 14 # Also, if you specify 15 # 16 # -Djava.security.properties==<URL> (2 equals), 17 # 18 # then that properties file completely overrides the master security 19 # properties file. 20 # 21 # To disable the ability to specify an additional properties file from 22 # the command line, set the key security.overridePropertiesFile 23 # to false in the master security properties file. It is set to true 24 # by default. 25 26 # In this file, various security properties are set for use by 27 # java.security classes. This is where users can statically register 28 # Cryptography Package Providers ("providers" for short). The term 29 # "provider" refers to a package or set of packages that supply a 30 # concrete implementation of a subset of the cryptography aspects of 31 # the Java Security API. A provider may, for example, implement one or 32 # more digital signature algorithms or message digest algorithms. 33 # 34 # Each provider must implement a subclass of the Provider class. 35 # To register a provider in this master security properties file, 36 # specify the Provider subclass name and priority in the format 37 # 38 # security.provider.<n>=<className> 39 # 40 # This declares a provider, and specifies its preference 41 # order n. The preference order is the order in which providers are 42 # searched for requested algorithms (when no specific provider is 43 # requested). The order is 1-based; 1 is the most preferred, followed 44 # by 2, and so on. 45 # 46 # <className> must specify the subclass of the Provider class whose 47 # constructor sets the values of various properties that are required 48 # for the Java Security API to look up the algorithms or other 49 # facilities implemented by the provider. 50 # 51 # There must be at least one provider specification in java.security. 52 # There is a default provider that comes standard with the JDK. It 53 # is called the "SUN" provider, and its Provider subclass 54 # named Sun appears in the sun.security.provider package. Thus, the 55 # "SUN" provider is registered via the following: 56 # 57 # security.provider.1=sun.security.provider.Sun 58 # 59 # (The number 1 is used for the default provider.) 60 # 61 # Note: Providers can be dynamically registered instead by calls to 62 # either the addProvider or insertProviderAt method in the Security 63 # class. 64 65 # 66 # List of providers and their preference orders (see above): 67 # 68 security.provider.1=sun.security.provider.Sun 69 security.provider.2=sun.security.rsa.SunRsaSign 70 security.provider.3=sun.security.ec.SunEC 71 security.provider.4=com.sun.net.ssl.internal.ssl.Provider 72 security.provider.5=com.sun.crypto.provider.SunJCE 73 security.provider.6=sun.security.jgss.SunProvider 74 security.provider.7=com.sun.security.sasl.Provider 75 security.provider.8=org.jcp.xml.dsig.internal.dom.XMLDSigRI 76 security.provider.9=sun.security.smartcardio.SunPCSC 77 78 # 79 # Sun Provider SecureRandom seed source. 80 # 81 # Select the primary source of seed data for the "SHA1PRNG" and 82 # "NativePRNG" SecureRandom implementations in the "Sun" provider. 83 # (Other SecureRandom implementations might also use this property.) 84 # 85 # On Unix-like systems (for example, Solaris/Linux/MacOS), the 86 # "NativePRNG" and "SHA1PRNG" implementations obtains seed data from 87 # special device files such as file:/dev/random. 88 # 89 # On Windows systems, specifying the URLs "file:/dev/random" or 90 # "file:/dev/urandom" will enable the native Microsoft CryptoAPI seeding 91 # mechanism for SHA1PRNG. 92 # 93 # By default, an attempt is made to use the entropy gathering device 94 # specified by the "securerandom.source" Security property. If an 95 # exception occurs while accessing the specified URL: 96 # 97 # SHA1PRNG: 98 # the traditional system/thread activity algorithm will be used. 99 # 100 # NativePRNG: 101 # a default value of /dev/random will be used. If neither 102 # are available, the implementation will be disabled. 103 # "file" is the only currently supported protocol type. 104 # 105 # The entropy gathering device can also be specified with the System 106 # property "java.security.egd". For example: 107 # 108 # % java -Djava.security.egd=file:/dev/random MainClass 109 # 110 # Specifying this System property will override the 111 # "securerandom.source" Security property. 112 # 113 # In addition, if "file:/dev/random" or "file:/dev/urandom" is 114 # specified, the "NativePRNG" implementation will be more preferred than 115 # SHA1PRNG in the Sun provider. 116 # 117 securerandom.source=file:/dev/random 118 119 # 120 # A list of known strong SecureRandom implementations. 121 # 122 # To help guide applications in selecting a suitable strong 123 # java.security.SecureRandom implementation, Java distributions should 124 # indicate a list of known strong implementations using the property. 125 # 126 # This is a comma-separated list of algorithm and/or algorithm:provider 127 # entries. 128 # 129 securerandom.strongAlgorithms=NativePRNGBlocking:SUN 130 131 # 132 # Class to instantiate as the javax.security.auth.login.Configuration 133 # provider. 134 # 135 login.configuration.provider=sun.security.provider.ConfigFile 136 137 # 138 # Default login configuration file 139 # 140 #login.config.url.1=file:${user.home}/.java.login.config 141 142 # 143 # Class to instantiate as the system Policy. This is the name of the class 144 # that will be used as the Policy object. 145 # 146 policy.provider=sun.security.provider.PolicyFile 147 148 # The default is to have a single system-wide policy file, 149 # and a policy file in the user's home directory. 150 policy.url.1=file:${java.home}/lib/security/java.policy 151 policy.url.2=file:${user.home}/.java.policy 152 153 # whether or not we expand properties in the policy file 154 # if this is set to false, properties (${...}) will not be expanded in policy 155 # files. 156 policy.expandProperties=true 157 158 # whether or not we allow an extra policy to be passed on the command line 159 # with -Djava.security.policy=somefile. Comment out this line to disable 160 # this feature. 161 policy.allowSystemProperty=true 162 163 # whether or not we look into the IdentityScope for trusted Identities 164 # when encountering a 1.1 signed JAR file. If the identity is found 165 # and is trusted, we grant it AllPermission. 166 policy.ignoreIdentityScope=false 167 168 # 169 # Default keystore type. 170 # 171 keystore.type=jks 172 173 # 174 # Controls compatibility mode for the JKS keystore type. 175 # 176 # When set to 'true', the JKS keystore type supports loading 177 # keystore files in either JKS or PKCS12 format. When set to 'false' 178 # it supports loading only JKS keystore files. 179 # 180 keystore.type.compat=true 181 182 # 183 # List of comma-separated packages that start with or equal this string 184 # will cause a security exception to be thrown when 185 # passed to checkPackageAccess unless the 186 # corresponding RuntimePermission ("accessClassInPackage."+package) has 187 # been granted. 188 package.access=sun.,\ 189 com.sun.xml.internal.,\ 190 com.sun.imageio.,\ 191 com.sun.istack.internal.,\ 192 com.sun.jmx.,\ 193 com.sun.media.sound.,\ 194 com.sun.naming.internal.,\ 195 com.sun.proxy.,\ 196 com.sun.corba.se.,\ 197 com.sun.org.apache.bcel.internal.,\ 198 com.sun.org.apache.regexp.internal.,\ 199 com.sun.org.apache.xerces.internal.,\ 200 com.sun.org.apache.xpath.internal.,\ 201 com.sun.org.apache.xalan.internal.extensions.,\ 202 com.sun.org.apache.xalan.internal.lib.,\ 203 com.sun.org.apache.xalan.internal.res.,\ 204 com.sun.org.apache.xalan.internal.templates.,\ 205 com.sun.org.apache.xalan.internal.utils.,\ 206 com.sun.org.apache.xalan.internal.xslt.,\ 207 com.sun.org.apache.xalan.internal.xsltc.cmdline.,\ 208 com.sun.org.apache.xalan.internal.xsltc.compiler.,\ 209 com.sun.org.apache.xalan.internal.xsltc.trax.,\ 210 com.sun.org.apache.xalan.internal.xsltc.util.,\ 211 com.sun.org.apache.xml.internal.res.,\ 212 com.sun.org.apache.xml.internal.security.,\ 213 com.sun.org.apache.xml.internal.serializer.utils.,\ 214 com.sun.org.apache.xml.internal.utils.,\ 215 com.sun.org.glassfish.,\ 216 com.oracle.xmlns.internal.,\ 217 com.oracle.webservices.internal.,\ 218 oracle.jrockit.jfr.,\ 219 org.jcp.xml.dsig.internal.,\ 220 jdk.internal.,\ 221 jdk.nashorn.internal.,\ 222 jdk.nashorn.tools.,\ 223 com.sun.activation.registries. 224 225 # 226 # List of comma-separated packages that start with or equal this string 227 # will cause a security exception to be thrown when 228 # passed to checkPackageDefinition unless the 229 # corresponding RuntimePermission ("defineClassInPackage."+package) has 230 # been granted. 231 # 232 # by default, none of the class loaders supplied with the JDK call 233 # checkPackageDefinition. 234 # 235 package.definition=sun.,\ 236 com.sun.xml.internal.,\ 237 com.sun.imageio.,\ 238 com.sun.istack.internal.,\ 239 com.sun.jmx.,\ 240 com.sun.media.sound.,\ 241 com.sun.naming.internal.,\ 242 com.sun.proxy.,\ 243 com.sun.corba.se.,\ 244 com.sun.org.apache.bcel.internal.,\ 245 com.sun.org.apache.regexp.internal.,\ 246 com.sun.org.apache.xerces.internal.,\ 247 com.sun.org.apache.xpath.internal.,\ 248 com.sun.org.apache.xalan.internal.extensions.,\ 249 com.sun.org.apache.xalan.internal.lib.,\ 250 com.sun.org.apache.xalan.internal.res.,\ 251 com.sun.org.apache.xalan.internal.templates.,\ 252 com.sun.org.apache.xalan.internal.utils.,\ 253 com.sun.org.apache.xalan.internal.xslt.,\ 254 com.sun.org.apache.xalan.internal.xsltc.cmdline.,\ 255 com.sun.org.apache.xalan.internal.xsltc.compiler.,\ 256 com.sun.org.apache.xalan.internal.xsltc.trax.,\ 257 com.sun.org.apache.xalan.internal.xsltc.util.,\ 258 com.sun.org.apache.xml.internal.res.,\ 259 com.sun.org.apache.xml.internal.security.,\ 260 com.sun.org.apache.xml.internal.serializer.utils.,\ 261 com.sun.org.apache.xml.internal.utils.,\ 262 com.sun.org.glassfish.,\ 263 com.oracle.xmlns.internal.,\ 264 com.oracle.webservices.internal.,\ 265 oracle.jrockit.jfr.,\ 266 org.jcp.xml.dsig.internal.,\ 267 jdk.internal.,\ 268 jdk.nashorn.internal.,\ 269 jdk.nashorn.tools.,\ 270 com.sun.activation.registries. 271 272 # 273 # Determines whether this properties file can be appended to 274 # or overridden on the command line via -Djava.security.properties 275 # 276 security.overridePropertiesFile=true 277 278 # 279 # Determines the default key and trust manager factory algorithms for 280 # the javax.net.ssl package. 281 # 282 ssl.KeyManagerFactory.algorithm=SunX509 283 ssl.TrustManagerFactory.algorithm=PKIX 284 285 # 286 # The Java-level namelookup cache policy for successful lookups: 287 # 288 # any negative value: caching forever 289 # any positive value: the number of seconds to cache an address for 290 # zero: do not cache 291 # 292 # default value is forever (FOREVER). For security reasons, this 293 # caching is made forever when a security manager is set. When a security 294 # manager is not set, the default behavior in this implementation 295 # is to cache for 30 seconds. 296 # 297 # NOTE: setting this to anything other than the default value can have 298 # serious security implications. Do not set it unless 299 # you are sure you are not exposed to DNS spoofing attack. 300 # 301 #networkaddress.cache.ttl=-1 302 303 # The Java-level namelookup cache policy for failed lookups: 304 # 305 # any negative value: cache forever 306 # any positive value: the number of seconds to cache negative lookup results 307 # zero: do not cache 308 # 309 # In some Microsoft Windows networking environments that employ 310 # the WINS name service in addition to DNS, name service lookups 311 # that fail may take a noticeably long time to return (approx. 5 seconds). 312 # For this reason the default caching policy is to maintain these 313 # results for 10 seconds. 314 # 315 # 316 networkaddress.cache.negative.ttl=10 317 318 # 319 # Properties to configure OCSP for certificate revocation checking 320 # 321 322 # Enable OCSP 323 # 324 # By default, OCSP is not used for certificate revocation checking. 325 # This property enables the use of OCSP when set to the value "true". 326 # 327 # NOTE: SocketPermission is required to connect to an OCSP responder. 328 # 329 # Example, 330 # ocsp.enable=true 331 332 # 333 # Location of the OCSP responder 334 # 335 # By default, the location of the OCSP responder is determined implicitly 336 # from the certificate being validated. This property explicitly specifies 337 # the location of the OCSP responder. The property is used when the 338 # Authority Information Access extension (defined in RFC 3280) is absent 339 # from the certificate or when it requires overriding. 340 # 341 # Example, 342 # ocsp.responderURL=http://ocsp.example.net:80 343 344 # 345 # Subject name of the OCSP responder's certificate 346 # 347 # By default, the certificate of the OCSP responder is that of the issuer 348 # of the certificate being validated. This property identifies the certificate 349 # of the OCSP responder when the default does not apply. Its value is a string 350 # distinguished name (defined in RFC 2253) which identifies a certificate in 351 # the set of certificates supplied during cert path validation. In cases where 352 # the subject name alone is not sufficient to uniquely identify the certificate 353 # then both the "ocsp.responderCertIssuerName" and 354 # "ocsp.responderCertSerialNumber" properties must be used instead. When this 355 # property is set then those two properties are ignored. 356 # 357 # Example, 358 # ocsp.responderCertSubjectName="CN=OCSP Responder, O=XYZ Corp" 359 360 # 361 # Issuer name of the OCSP responder's certificate 362 # 363 # By default, the certificate of the OCSP responder is that of the issuer 364 # of the certificate being validated. This property identifies the certificate 365 # of the OCSP responder when the default does not apply. Its value is a string 366 # distinguished name (defined in RFC 2253) which identifies a certificate in 367 # the set of certificates supplied during cert path validation. When this 368 # property is set then the "ocsp.responderCertSerialNumber" property must also 369 # be set. When the "ocsp.responderCertSubjectName" property is set then this 370 # property is ignored. 371 # 372 # Example, 373 # ocsp.responderCertIssuerName="CN=Enterprise CA, O=XYZ Corp" 374 375 # 376 # Serial number 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 # of hexadecimal digits (colon or space separators may be present) which 382 # identifies a certificate in the set of certificates supplied during cert path 383 # validation. When this property is set then the "ocsp.responderCertIssuerName" 384 # property must also be set. When the "ocsp.responderCertSubjectName" property 385 # is set then this property is ignored. 386 # 387 # Example, 388 # ocsp.responderCertSerialNumber=2A:FF:00 389 390 # 391 # Policy for failed Kerberos KDC lookups: 392 # 393 # When a KDC is unavailable (network error, service failure, etc), it is 394 # put inside a blacklist and accessed less often for future requests. The 395 # value (case-insensitive) for this policy can be: 396 # 397 # tryLast 398 # KDCs in the blacklist are always tried after those not on the list. 399 # 400 # tryLess[:max_retries,timeout] 401 # KDCs in the blacklist are still tried by their order in the configuration, 402 # but with smaller max_retries and timeout values. max_retries and timeout 403 # are optional numerical parameters (default 1 and 5000, which means once 404 # and 5 seconds). Please notes that if any of the values defined here is 405 # more than what is defined in krb5.conf, it will be ignored. 406 # 407 # Whenever a KDC is detected as available, it is removed from the blacklist. 408 # The blacklist is reset when krb5.conf is reloaded. You can add 409 # refreshKrb5Config=true to a JAAS configuration file so that krb5.conf is 410 # reloaded whenever a JAAS authentication is attempted. 411 # 412 # Example, 413 # krb5.kdc.bad.policy = tryLast 414 # krb5.kdc.bad.policy = tryLess:2,2000 415 krb5.kdc.bad.policy = tryLast 416 417 # Algorithm restrictions for certification path (CertPath) processing 418 # 419 # In some environments, certain algorithms or key lengths may be undesirable 420 # for certification path building and validation. For example, "MD2" is 421 # generally no longer considered to be a secure hash algorithm. This section 422 # describes the mechanism for disabling algorithms based on algorithm name 423 # and/or key length. This includes algorithms used in certificates, as well 424 # as revocation information such as CRLs and signed OCSP Responses. 425 # 426 # The syntax of the disabled algorithm string is described as this Java 427 # BNF-style: 428 # DisabledAlgorithms: 429 # " DisabledAlgorithm { , DisabledAlgorithm } " 430 # 431 # DisabledAlgorithm: 432 # AlgorithmName [Constraint] 433 # 434 # AlgorithmName: 435 # (see below) 436 # 437 # Constraint: 438 # KeySizeConstraint 439 # 440 # KeySizeConstraint: 441 # keySize Operator DecimalInteger 442 # 443 # Operator: 444 # <= | < | == | != | >= | > 445 # 446 # DecimalInteger: 447 # DecimalDigits 448 # 449 # DecimalDigits: 450 # DecimalDigit {DecimalDigit} 451 # 452 # DecimalDigit: one of 453 # 1 2 3 4 5 6 7 8 9 0 454 # 455 # The "AlgorithmName" is the standard algorithm name of the disabled 456 # algorithm. See "Java Cryptography Architecture Standard Algorithm Name 457 # Documentation" for information about Standard Algorithm Names. Matching 458 # is performed using a case-insensitive sub-element matching rule. (For 459 # example, in "SHA1withECDSA" the sub-elements are "SHA1" for hashing and 460 # "ECDSA" for signatures.) If the assertion "AlgorithmName" is a 461 # sub-element of the certificate algorithm name, the algorithm will be 462 # rejected during certification path building and validation. For example, 463 # the assertion algorithm name "DSA" will disable all certificate algorithms 464 # that rely on DSA, such as NONEwithDSA, SHA1withDSA. However, the assertion 465 # will not disable algorithms related to "ECDSA". 466 # 467 # A "Constraint" provides further guidance for the algorithm being specified. 468 # The "KeySizeConstraint" requires a key of a valid size range if the 469 # "AlgorithmName" is of a key algorithm. The "DecimalInteger" indicates the 470 # key size specified in number of bits. For example, "RSA keySize <= 1024" 471 # indicates that any RSA key with key size less than or equal to 1024 bits 472 # should be disabled, and "RSA keySize < 1024, RSA keySize > 2048" indicates 473 # that any RSA key with key size less than 1024 or greater than 2048 should 474 # be disabled. Note that the "KeySizeConstraint" only makes sense to key 475 # algorithms. 476 # 477 # Note: This property is currently used by Oracle's PKIX implementation. It 478 # is not guaranteed to be examined and used by other implementations. 479 # 480 # Example: 481 # jdk.certpath.disabledAlgorithms=MD2, DSA, RSA keySize < 2048 482 # 483 # 484 jdk.certpath.disabledAlgorithms=MD2, MD5, RSA keySize < 1024 485 486 # Algorithm restrictions for Secure Socket Layer/Transport Layer Security 487 # (SSL/TLS) processing 488 # 489 # In some environments, certain algorithms or key lengths may be undesirable 490 # when using SSL/TLS. This section describes the mechanism for disabling 491 # algorithms during SSL/TLS security parameters negotiation, including 492 # protocol version negotiation, cipher suites selection, peer authentication 493 # and key exchange mechanisms. 494 # 495 # Disabled algorithms will not be negotiated for SSL/TLS connections, even 496 # if they are enabled explicitly in an application. 497 # 498 # For PKI-based peer authentication and key exchange mechanisms, this list 499 # of disabled algorithms will also be checked during certification path 500 # building and validation, including algorithms used in certificates, as 501 # well as revocation information such as CRLs and signed OCSP Responses. 502 # This is in addition to the jdk.certpath.disabledAlgorithms property above. 503 # 504 # See the specification of "jdk.certpath.disabledAlgorithms" for the 505 # syntax of the disabled algorithm string. 506 # 507 # Note: This property is currently used by Oracle's JSSE implementation. 508 # It is not guaranteed to be examined and used by other implementations. 509 # 510 # Example: 511 # jdk.tls.disabledAlgorithms=MD5, SSLv3, DSA, RSA keySize < 2048 512 jdk.tls.disabledAlgorithms=SSLv3, RC4, MD5withRSA, DH keySize < 768 513 514 # Legacy algorithms for Secure Socket Layer/Transport Layer Security (SSL/TLS) 515 # processing in JSSE implementation. 516 # 517 # In some environments, a certain algorithm may be undesirable but it 518 # cannot be disabled because of its use in legacy applications. Legacy 519 # algorithms may still be supported, but applications should not use them 520 # as the security strength of legacy algorithms are usually not strong enough 521 # in practice. 522 # 523 # During SSL/TLS security parameters negotiation, legacy algorithms will 524 # not be negotiated unless there are no other candidates. 525 # 526 # The syntax of the disabled algorithm string is described as this Java 527 # BNF-style: 528 # LegacyAlgorithms: 529 # " LegacyAlgorithm { , LegacyAlgorithm } " 530 # 531 # LegacyAlgorithm: 532 # AlgorithmName (standard JSSE algorithm name) 533 # 534 # See the specification of security property "jdk.certpath.disabledAlgorithms" 535 # for the syntax and description of the "AlgorithmName" notation. 536 # 537 # Per SSL/TLS specifications, cipher suites have the form: 538 # SSL_KeyExchangeAlg_WITH_CipherAlg_MacAlg 539 # or 540 # TLS_KeyExchangeAlg_WITH_CipherAlg_MacAlg 541 # 542 # For example, the cipher suite TLS_RSA_WITH_AES_128_CBC_SHA uses RSA as the 543 # key exchange algorithm, AES_128_CBC (128 bits AES cipher algorithm in CBC 544 # mode) as the cipher (encryption) algorithm, and SHA-1 as the message digest 545 # algorithm for HMAC. 546 # 547 # The LegacyAlgorithm can be one of the following standard algorithm names: 548 # 1. JSSE cipher suite name, e.g., TLS_RSA_WITH_AES_128_CBC_SHA 549 # 2. JSSE key exchange algorithm name, e.g., RSA 550 # 3. JSSE cipher (encryption) algorithm name, e.g., AES_128_CBC 551 # 4. JSSE message digest algorithm name, e.g., SHA 552 # 553 # See SSL/TLS specifications and "Java Cryptography Architecture Standard 554 # Algorithm Name Documentation" for information about the algorithm names. 555 # 556 # Note: This property is currently used by Oracle's JSSE implementation. 557 # It is not guaranteed to be examined and used by other implementations. 558 # There is no guarantee the property will continue to exist or be of the 559 # same syntax in future releases. 560 # 561 # Example: 562 # jdk.tls.legacyAlgorithms=DH_anon, DES_CBC, SSL_RSA_WITH_RC4_128_MD5 563 # 564 jdk.tls.legacyAlgorithms= \ 565 K_NULL, C_NULL, M_NULL, \ 566 DHE_DSS_EXPORT, DHE_RSA_EXPORT, DH_anon_EXPORT, DH_DSS_EXPORT, \ 567 DH_RSA_EXPORT, RSA_EXPORT, \ 568 DH_anon, ECDH_anon, \ 569 RC4_128, RC4_40, DES_CBC, DES40_CBC 570 571 # The pre-defined default finite field Diffie-Hellman ephemeral (DHE) 572 # parameters for Transport Layer Security (SSL/TLS/DTLS) processing. 573 # 574 # In traditional SSL/TLS/DTLS connections where finite field DHE parameters 575 # negotiation mechanism is not used, the server offers the client group 576 # parameters, base generator g and prime modulus p, for DHE key exchange. 577 # It is recommended to use dynamic group parameters. This property defines 578 # a mechanism that allows you to specify custom group parameters. 579 # 580 # The syntax of this property string is described as this Java BNF-style: 581 # DefaultDHEParameters: 582 # DefinedDHEParameters { , DefinedDHEParameters } 583 # 584 # DefinedDHEParameters: 585 # "{" DHEPrimeModulus , DHEBaseGenerator "}" 586 # 587 # DHEPrimeModulus: 588 # HexadecimalDigits 589 # 590 # DHEBaseGenerator: 591 # HexadecimalDigits 592 # 593 # HexadecimalDigits: 594 # HexadecimalDigit { HexadecimalDigit } 595 # 596 # HexadecimalDigit: one of 597 # 0 1 2 3 4 5 6 7 8 9 A B C D E F a b c d e f 598 # 599 # Whitespace characters are ignored. 600 # 601 # The "DefinedDHEParameters" defines the custom group parameters, prime 602 # modulus p and base generator g, for a particular size of prime modulus p. 603 # The "DHEPrimeModulus" defines the hexadecimal prime modulus p, and the 604 # "DHEBaseGenerator" defines the hexadecimal base generator g of a group 605 # parameter. It is recommended to use safe primes for the custom group 606 # parameters. 607 # 608 # If this property is not defined or the value is empty, the underlying JSSE 609 # provider's default group parameter is used for each connection. 610 # 611 # If the property value does not follow the grammar, or a particular group 612 # parameter is not valid, the connection will fall back and use the 613 # underlying JSSE provider's default group parameter. 614 # 615 # Note: This property is currently used by OpenJDK's JSSE implementation. It 616 # is not guaranteed to be examined and used by other implementations. 617 # 618 # Example: 619 # jdk.tls.server.defaultDHEParameters= 620 # { \ 621 # FFFFFFFF FFFFFFFF C90FDAA2 2168C234 C4C6628B 80DC1CD1 \ 622 # 29024E08 8A67CC74 020BBEA6 3B139B22 514A0879 8E3404DD \ 623 # EF9519B3 CD3A431B 302B0A6D F25F1437 4FE1356D 6D51C245 \ 624 # E485B576 625E7EC6 F44C42E9 A637ED6B 0BFF5CB6 F406B7ED \ 625 # EE386BFB 5A899FA5 AE9F2411 7C4B1FE6 49286651 ECE65381 \ 626 # FFFFFFFF FFFFFFFF, 2} 627 628 # Algorithm restrictions for signed JAR files 629 # 630 # In some environments, certain algorithms or key lengths may be undesirable 631 # for signed JAR validation. For example, "MD2" is generally no longer 632 # considered to be a secure hash algorithm. This section describes the 633 # mechanism for disabling algorithms based on algorithm name and/or key length. 634 # JARs signed with any of the disabled algorithms or key sizes will be treated 635 # as unsigned. 636 # 637 # The syntax of the disabled algorithm string is described as follows: 638 # DisabledAlgorithms: 639 # " DisabledAlgorithm { , DisabledAlgorithm } " 640 # 641 # DisabledAlgorithm: 642 # AlgorithmName [Constraint] 643 # 644 # AlgorithmName: 645 # (see below) 646 # 647 # Constraint: 648 # KeySizeConstraint 649 # 650 # KeySizeConstraint: 651 # keySize Operator KeyLength 652 # 653 # Operator: 654 # <= | < | == | != | >= | > 655 # 656 # KeyLength: 657 # Integer value of the algorithm's key length in bits 658 # 659 # Note: This property is currently used by the JDK Reference 660 # implementation. It is not guaranteed to be examined and used by other 661 # implementations. 662 # 663 jdk.jar.disabledAlgorithms=MD2, RSA keySize < 1024