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