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.security.,\ 214 com.sun.org.apache.xml.internal.serializer.utils.,\ 215 com.sun.org.apache.xml.internal.utils.,\ 216 com.sun.org.glassfish.,\ 217 com.oracle.xmlns.internal.,\ 218 com.oracle.webservices.internal.,\ 219 oracle.jrockit.jfr.,\ 220 org.jcp.xml.dsig.internal.,\ 221 jdk.internal.,\ 222 jdk.nashorn.internal.,\ 223 jdk.nashorn.tools.,\ 224 com.sun.activation.registries.,\ 225 com.sun.java.accessibility. 226 227 # 228 # List of comma-separated packages that start with or equal this string 229 # will cause a security exception to be thrown when 230 # passed to checkPackageDefinition unless the 231 # corresponding RuntimePermission ("defineClassInPackage."+package) has 232 # been granted. 233 # 234 # by default, none of the class loaders supplied with the JDK call 235 # checkPackageDefinition. 236 # 237 package.definition=sun.,\ 238 com.sun.xml.internal.,\ 239 com.sun.imageio.,\ 240 com.sun.istack.internal.,\ 241 com.sun.jmx.,\ 242 com.sun.media.sound.,\ 243 com.sun.naming.internal.,\ 244 com.sun.proxy.,\ 245 com.sun.corba.se.,\ 246 com.sun.org.apache.bcel.internal.,\ 247 com.sun.org.apache.regexp.internal.,\ 248 com.sun.org.apache.xerces.internal.,\ 249 com.sun.org.apache.xpath.internal.,\ 250 com.sun.org.apache.xalan.internal.extensions.,\ 251 com.sun.org.apache.xalan.internal.lib.,\ 252 com.sun.org.apache.xalan.internal.res.,\ 253 com.sun.org.apache.xalan.internal.templates.,\ 254 com.sun.org.apache.xalan.internal.utils.,\ 255 com.sun.org.apache.xalan.internal.xslt.,\ 256 com.sun.org.apache.xalan.internal.xsltc.cmdline.,\ 257 com.sun.org.apache.xalan.internal.xsltc.compiler.,\ 258 com.sun.org.apache.xalan.internal.xsltc.trax.,\ 259 com.sun.org.apache.xalan.internal.xsltc.util.,\ 260 com.sun.org.apache.xml.internal.res.,\ 261 com.sun.org.apache.xml.internal.security.,\ 262 com.sun.org.apache.xml.internal.serializer.utils.,\ 263 com.sun.org.apache.xml.internal.utils.,\ 264 com.sun.org.glassfish.,\ 265 com.oracle.xmlns.internal.,\ 266 com.oracle.webservices.internal.,\ 267 oracle.jrockit.jfr.,\ 268 org.jcp.xml.dsig.internal.,\ 269 jdk.internal.,\ 270 jdk.nashorn.internal.,\ 271 jdk.nashorn.tools.,\ 272 com.sun.activation.registries.,\ 273 com.sun.java.accessibility. 274 275 # 276 # Determines whether this properties file can be appended to 277 # or overridden on the command line via -Djava.security.properties 278 # 279 security.overridePropertiesFile=true 280 281 # 282 # Determines the default key and trust manager factory algorithms for 283 # the javax.net.ssl package. 284 # 285 ssl.KeyManagerFactory.algorithm=SunX509 286 ssl.TrustManagerFactory.algorithm=PKIX 287 288 # 289 # The Java-level namelookup cache policy for successful lookups: 290 # 291 # any negative value: caching forever 292 # any positive value: the number of seconds to cache an address for 293 # zero: do not cache 294 # 295 # default value is forever (FOREVER). For security reasons, this 296 # caching is made forever when a security manager is set. When a security 297 # manager is not set, the default behavior in this implementation 298 # is to cache for 30 seconds. 299 # 300 # NOTE: setting this to anything other than the default value can have 301 # serious security implications. Do not set it unless 302 # you are sure you are not exposed to DNS spoofing attack. 303 # 304 #networkaddress.cache.ttl=-1 305 306 # The Java-level namelookup cache policy for failed lookups: 307 # 308 # any negative value: cache forever 309 # any positive value: the number of seconds to cache negative lookup results 310 # zero: do not cache 311 # 312 # In some Microsoft Windows networking environments that employ 313 # the WINS name service in addition to DNS, name service lookups 314 # that fail may take a noticeably long time to return (approx. 5 seconds). 315 # For this reason the default caching policy is to maintain these 316 # results for 10 seconds. 317 # 318 # 319 networkaddress.cache.negative.ttl=10 320 321 # 322 # Properties to configure OCSP for certificate revocation checking 323 # 324 325 # Enable OCSP 326 # 327 # By default, OCSP is not used for certificate revocation checking. 328 # This property enables the use of OCSP when set to the value "true". 329 # 330 # NOTE: SocketPermission is required to connect to an OCSP responder. 331 # 332 # Example, 333 # ocsp.enable=true 334 335 # 336 # Location of the OCSP responder 337 # 338 # By default, the location of the OCSP responder is determined implicitly 339 # from the certificate being validated. This property explicitly specifies 340 # the location of the OCSP responder. The property is used when the 341 # Authority Information Access extension (defined in RFC 3280) is absent 342 # from the certificate or when it requires overriding. 343 # 344 # Example, 345 # ocsp.responderURL=http://ocsp.example.net:80 346 347 # 348 # Subject name of the OCSP responder's certificate 349 # 350 # By default, the certificate of the OCSP responder is that of the issuer 351 # of the certificate being validated. This property identifies the certificate 352 # of the OCSP responder when the default does not apply. Its value is a string 353 # distinguished name (defined in RFC 2253) which identifies a certificate in 354 # the set of certificates supplied during cert path validation. In cases where 355 # the subject name alone is not sufficient to uniquely identify the certificate 356 # then both the "ocsp.responderCertIssuerName" and 357 # "ocsp.responderCertSerialNumber" properties must be used instead. When this 358 # property is set then those two properties are ignored. 359 # 360 # Example, 361 # ocsp.responderCertSubjectName="CN=OCSP Responder, O=XYZ Corp" 362 363 # 364 # Issuer name of the OCSP responder's certificate 365 # 366 # By default, the certificate of the OCSP responder is that of the issuer 367 # of the certificate being validated. This property identifies the certificate 368 # of the OCSP responder when the default does not apply. Its value is a string 369 # distinguished name (defined in RFC 2253) which identifies a certificate in 370 # the set of certificates supplied during cert path validation. When this 371 # property is set then the "ocsp.responderCertSerialNumber" property must also 372 # be set. When the "ocsp.responderCertSubjectName" property is set then this 373 # property is ignored. 374 # 375 # Example, 376 # ocsp.responderCertIssuerName="CN=Enterprise CA, O=XYZ Corp" 377 378 # 379 # Serial number of the OCSP responder's certificate 380 # 381 # By default, the certificate of the OCSP responder is that of the issuer 382 # of the certificate being validated. This property identifies the certificate 383 # of the OCSP responder when the default does not apply. Its value is a string 384 # of hexadecimal digits (colon or space separators may be present) which 385 # identifies a certificate in the set of certificates supplied during cert path 386 # validation. When this property is set then the "ocsp.responderCertIssuerName" 387 # property must also be set. When the "ocsp.responderCertSubjectName" property 388 # is set then this property is ignored. 389 # 390 # Example, 391 # ocsp.responderCertSerialNumber=2A:FF:00 392 393 # 394 # Policy for failed Kerberos KDC lookups: 395 # 396 # When a KDC is unavailable (network error, service failure, etc), it is 397 # put inside a blacklist and accessed less often for future requests. The 398 # value (case-insensitive) for this policy can be: 399 # 400 # tryLast 401 # KDCs in the blacklist are always tried after those not on the list. 402 # 403 # tryLess[:max_retries,timeout] 404 # KDCs in the blacklist are still tried by their order in the configuration, 405 # but with smaller max_retries and timeout values. max_retries and timeout 406 # are optional numerical parameters (default 1 and 5000, which means once 407 # and 5 seconds). Please notes that if any of the values defined here is 408 # more than what is defined in krb5.conf, it will be ignored. 409 # 410 # Whenever a KDC is detected as available, it is removed from the blacklist. 411 # The blacklist is reset when krb5.conf is reloaded. You can add 412 # refreshKrb5Config=true to a JAAS configuration file so that krb5.conf is 413 # reloaded whenever a JAAS authentication is attempted. 414 # 415 # Example, 416 # krb5.kdc.bad.policy = tryLast 417 # krb5.kdc.bad.policy = tryLess:2,2000 418 krb5.kdc.bad.policy = tryLast 419 420 # Algorithm restrictions for certification path (CertPath) processing 421 # 422 # In some environments, certain algorithms or key lengths may be undesirable 423 # for certification path building and validation. For example, "MD2" is 424 # generally no longer considered to be a secure hash algorithm. This section 425 # describes the mechanism for disabling algorithms based on algorithm name 426 # and/or key length. This includes algorithms used in certificates, as well 427 # as revocation information such as CRLs and signed OCSP Responses. 428 # 429 # The syntax of the disabled algorithm string is described as this Java 430 # BNF-style: 431 # DisabledAlgorithms: 432 # " DisabledAlgorithm { , DisabledAlgorithm } " 433 # 434 # DisabledAlgorithm: 435 # AlgorithmName [Constraint] 436 # 437 # AlgorithmName: 438 # (see below) 439 # 440 # Constraint: 441 # KeySizeConstraint 442 # 443 # KeySizeConstraint: 444 # keySize Operator DecimalInteger 445 # 446 # Operator: 447 # <= | < | == | != | >= | > 448 # 449 # DecimalInteger: 450 # DecimalDigits 451 # 452 # DecimalDigits: 453 # DecimalDigit {DecimalDigit} 454 # 455 # DecimalDigit: one of 456 # 1 2 3 4 5 6 7 8 9 0 457 # 458 # The "AlgorithmName" is the standard algorithm name of the disabled 459 # algorithm. See "Java Cryptography Architecture Standard Algorithm Name 460 # Documentation" for information about Standard Algorithm Names. Matching 461 # is performed using a case-insensitive sub-element matching rule. (For 462 # example, in "SHA1withECDSA" the sub-elements are "SHA1" for hashing and 463 # "ECDSA" for signatures.) If the assertion "AlgorithmName" is a 464 # sub-element of the certificate algorithm name, the algorithm will be 465 # rejected during certification path building and validation. For example, 466 # the assertion algorithm name "DSA" will disable all certificate algorithms 467 # that rely on DSA, such as NONEwithDSA, SHA1withDSA. However, the assertion 468 # will not disable algorithms related to "ECDSA". 469 # 470 # A "Constraint" provides further guidance for the algorithm being specified. 471 # The "KeySizeConstraint" requires a key of a valid size range if the 472 # "AlgorithmName" is of a key algorithm. The "DecimalInteger" indicates the 473 # key size specified in number of bits. For example, "RSA keySize <= 1024" 474 # indicates that any RSA key with key size less than or equal to 1024 bits 475 # should be disabled, and "RSA keySize < 1024, RSA keySize > 2048" indicates 476 # that any RSA key with key size less than 1024 or greater than 2048 should 477 # be disabled. Note that the "KeySizeConstraint" only makes sense to key 478 # algorithms. 479 # 480 # Note: This property is currently used by Oracle's PKIX implementation. It 481 # is not guaranteed to be examined and used by other implementations. 482 # 483 # Example: 484 # jdk.certpath.disabledAlgorithms=MD2, DSA, RSA keySize < 2048 485 # 486 # 487 jdk.certpath.disabledAlgorithms=MD2, MD5, RSA keySize < 1024 488 489 # Algorithm restrictions for signed JAR files 490 # 491 # In some environments, certain algorithms or key lengths may be undesirable 492 # for signed JAR validation. For example, "MD2" is generally no longer 493 # considered to be a secure hash algorithm. This section describes the 494 # mechanism for disabling algorithms based on algorithm name and/or key length. 495 # JARs signed with any of the disabled algorithms or key sizes will be treated 496 # as unsigned. 497 # 498 # The syntax of the disabled algorithm string is described as follows: 499 # DisabledAlgorithms: 500 # " DisabledAlgorithm { , DisabledAlgorithm } " 501 # 502 # DisabledAlgorithm: 503 # AlgorithmName [Constraint] 504 # 505 # AlgorithmName: 506 # (see below) 507 # 508 # Constraint: 509 # KeySizeConstraint 510 # 511 # KeySizeConstraint: 512 # keySize Operator KeyLength 513 # 514 # Operator: 515 # <= | < | == | != | >= | > 516 # 517 # KeyLength: 518 # Integer value of the algorithm's key length in bits 519 # 520 # Note: This property is currently used by the JDK Reference 521 # implementation. It is not guaranteed to be examined and used by other 522 # implementations. 523 # 524 jdk.jar.disabledAlgorithms=MD2, MD5, RSA keySize < 1024 525 526 # Algorithm restrictions for Secure Socket Layer/Transport Layer Security 527 # (SSL/TLS) processing 528 # 529 # In some environments, certain algorithms or key lengths may be undesirable 530 # when using SSL/TLS. This section describes the mechanism for disabling 531 # algorithms during SSL/TLS security parameters negotiation, including 532 # protocol version negotiation, cipher suites selection, peer authentication 533 # and key exchange mechanisms. 534 # 535 # Disabled algorithms will not be negotiated for SSL/TLS connections, even 536 # if they are enabled explicitly in an application. 537 # 538 # For PKI-based peer authentication and key exchange mechanisms, this list 539 # of disabled algorithms will also be checked during certification path 540 # building and validation, including algorithms used in certificates, as 541 # well as revocation information such as CRLs and signed OCSP Responses. 542 # This is in addition to the jdk.certpath.disabledAlgorithms property above. 543 # 544 # See the specification of "jdk.certpath.disabledAlgorithms" for the 545 # syntax of the disabled algorithm string. 546 # 547 # Note: This property is currently used by Oracle's JSSE implementation. 548 # It is not guaranteed to be examined and used by other implementations. 549 # 550 # Example: 551 # jdk.tls.disabledAlgorithms=MD5, SSLv3, DSA, RSA keySize < 2048 552 jdk.tls.disabledAlgorithms=SSLv3, RC4, MD5withRSA, DH keySize < 768 553 554 # Legacy algorithms for Secure Socket Layer/Transport Layer Security (SSL/TLS) 555 # processing in JSSE implementation. 556 # 557 # In some environments, a certain algorithm may be undesirable but it 558 # cannot be disabled because of its use in legacy applications. Legacy 559 # algorithms may still be supported, but applications should not use them 560 # as the security strength of legacy algorithms are usually not strong enough 561 # in practice. 562 # 563 # During SSL/TLS security parameters negotiation, legacy algorithms will 564 # not be negotiated unless there are no other candidates. 565 # 566 # The syntax of the disabled algorithm string is described as this Java 567 # BNF-style: 568 # LegacyAlgorithms: 569 # " LegacyAlgorithm { , LegacyAlgorithm } " 570 # 571 # LegacyAlgorithm: 572 # AlgorithmName (standard JSSE algorithm name) 573 # 574 # See the specification of security property "jdk.certpath.disabledAlgorithms" 575 # for the syntax and description of the "AlgorithmName" notation. 576 # 577 # Per SSL/TLS specifications, cipher suites have the form: 578 # SSL_KeyExchangeAlg_WITH_CipherAlg_MacAlg 579 # or 580 # TLS_KeyExchangeAlg_WITH_CipherAlg_MacAlg 581 # 582 # For example, the cipher suite TLS_RSA_WITH_AES_128_CBC_SHA uses RSA as the 583 # key exchange algorithm, AES_128_CBC (128 bits AES cipher algorithm in CBC 584 # mode) as the cipher (encryption) algorithm, and SHA-1 as the message digest 585 # algorithm for HMAC. 586 # 587 # The LegacyAlgorithm can be one of the following standard algorithm names: 588 # 1. JSSE cipher suite name, e.g., TLS_RSA_WITH_AES_128_CBC_SHA 589 # 2. JSSE key exchange algorithm name, e.g., RSA 590 # 3. JSSE cipher (encryption) algorithm name, e.g., AES_128_CBC 591 # 4. JSSE message digest algorithm name, e.g., SHA 592 # 593 # See SSL/TLS specifications and "Java Cryptography Architecture Standard 594 # Algorithm Name Documentation" for information about the algorithm names. 595 # 596 # Note: This property is currently used by Oracle's JSSE implementation. 597 # It is not guaranteed to be examined and used by other implementations. 598 # There is no guarantee the property will continue to exist or be of the 599 # same syntax in future releases. 600 # 601 # Example: 602 # jdk.tls.legacyAlgorithms=DH_anon, DES_CBC, SSL_RSA_WITH_RC4_128_MD5 603 # 604 jdk.tls.legacyAlgorithms= \ 605 K_NULL, C_NULL, M_NULL, \ 606 DHE_DSS_EXPORT, DHE_RSA_EXPORT, DH_anon_EXPORT, DH_DSS_EXPORT, \ 607 DH_RSA_EXPORT, RSA_EXPORT, \ 608 DH_anon, ECDH_anon, \ 609 RC4_128, RC4_40, DES_CBC, DES40_CBC 610 611 # The pre-defined default finite field Diffie-Hellman ephemeral (DHE) 612 # parameters for Transport Layer Security (SSL/TLS/DTLS) processing. 613 # 614 # In traditional SSL/TLS/DTLS connections where finite field DHE parameters 615 # negotiation mechanism is not used, the server offers the client group 616 # parameters, base generator g and prime modulus p, for DHE key exchange. 617 # It is recommended to use dynamic group parameters. This property defines 618 # a mechanism that allows you to specify custom group parameters. 619 # 620 # The syntax of this property string is described as this Java BNF-style: 621 # DefaultDHEParameters: 622 # DefinedDHEParameters { , DefinedDHEParameters } 623 # 624 # DefinedDHEParameters: 625 # "{" DHEPrimeModulus , DHEBaseGenerator "}" 626 # 627 # DHEPrimeModulus: 628 # HexadecimalDigits 629 # 630 # DHEBaseGenerator: 631 # HexadecimalDigits 632 # 633 # HexadecimalDigits: 634 # HexadecimalDigit { HexadecimalDigit } 635 # 636 # HexadecimalDigit: one of 637 # 0 1 2 3 4 5 6 7 8 9 A B C D E F a b c d e f 638 # 639 # Whitespace characters are ignored. 640 # 641 # The "DefinedDHEParameters" defines the custom group parameters, prime 642 # modulus p and base generator g, for a particular size of prime modulus p. 643 # The "DHEPrimeModulus" defines the hexadecimal prime modulus p, and the 644 # "DHEBaseGenerator" defines the hexadecimal base generator g of a group 645 # parameter. It is recommended to use safe primes for the custom group 646 # parameters. 647 # 648 # If this property is not defined or the value is empty, the underlying JSSE 649 # provider's default group parameter is used for each connection. 650 # 651 # If the property value does not follow the grammar, or a particular group 652 # parameter is not valid, the connection will fall back and use the 653 # underlying JSSE provider's default group parameter. 654 # 655 # Note: This property is currently used by OpenJDK's JSSE implementation. It 656 # is not guaranteed to be examined and used by other implementations. 657 # 658 # Example: 659 # jdk.tls.server.defaultDHEParameters= 660 # { \ 661 # FFFFFFFF FFFFFFFF C90FDAA2 2168C234 C4C6628B 80DC1CD1 \ 662 # 29024E08 8A67CC74 020BBEA6 3B139B22 514A0879 8E3404DD \ 663 # EF9519B3 CD3A431B 302B0A6D F25F1437 4FE1356D 6D51C245 \ 664 # E485B576 625E7EC6 F44C42E9 A637ED6B 0BFF5CB6 F406B7ED \ 665 # EE386BFB 5A899FA5 AE9F2411 7C4B1FE6 49286651 ECE65381 \ 666 # FFFFFFFF FFFFFFFF, 2}