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