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=com.oracle.security.ucrypto.UcryptoProvider ${java.home}/lib/security/ucrypto-solaris.cfg
  69 security.provider.2=sun.security.pkcs11.SunPKCS11 ${java.home}/lib/security/sunpkcs11-solaris.cfg
  70 security.provider.3=sun.security.provider.Sun
  71 security.provider.4=sun.security.rsa.SunRsaSign
  72 security.provider.5=sun.security.ec.SunEC
  73 security.provider.6=com.sun.net.ssl.internal.ssl.Provider
  74 security.provider.7=com.sun.crypto.provider.SunJCE
  75 security.provider.8=sun.security.jgss.SunProvider
  76 security.provider.9=com.sun.security.sasl.Provider
  77 security.provider.10=org.jcp.xml.dsig.internal.dom.XMLDSigRI
  78 security.provider.11=sun.security.smartcardio.SunPCSC
  79 
  80 #
  81 # Sun Provider SecureRandom seed source.
  82 #
  83 # Select the primary source of seed data for the "SHA1PRNG" and
  84 # "NativePRNG" SecureRandom implementations in the "Sun" provider.
  85 # (Other SecureRandom implementations might also use this property.)
  86 #
  87 # On Unix-like systems (for example, Solaris/Linux/MacOS), the
  88 # "NativePRNG" and "SHA1PRNG" implementations obtains seed data from
  89 # special device files such as file:/dev/random.
  90 #
  91 # On Windows systems, specifying the URLs "file:/dev/random" or
  92 # "file:/dev/urandom" will enable the native Microsoft CryptoAPI seeding
  93 # mechanism for SHA1PRNG.
  94 #
  95 # By default, an attempt is made to use the entropy gathering device
  96 # specified by the "securerandom.source" Security property.  If an
  97 # exception occurs while accessing the specified URL:
  98 #
  99 #     SHA1PRNG:
 100 #         the traditional system/thread activity algorithm will be used.
 101 #
 102 #     NativePRNG:
 103 #         a default value of /dev/random will be used.  If neither
 104 #         are available, the implementation will be disabled.
 105 #         "file" is the only currently supported protocol type.
 106 #
 107 # The entropy gathering device can also be specified with the System
 108 # property "java.security.egd". For example:
 109 #
 110 #   % java -Djava.security.egd=file:/dev/random MainClass
 111 #
 112 # Specifying this System property will override the
 113 # "securerandom.source" Security property.
 114 #
 115 # In addition, if "file:/dev/random" or "file:/dev/urandom" is
 116 # specified, the "NativePRNG" implementation will be more preferred than
 117 # SHA1PRNG in the Sun provider.
 118 #
 119 securerandom.source=file:/dev/random
 120 
 121 #
 122 # A list of known strong SecureRandom implementations.
 123 #
 124 # To help guide applications in selecting a suitable strong
 125 # java.security.SecureRandom implementation, Java distributions should
 126 # indicate a list of known strong implementations using the property.
 127 #
 128 # This is a comma-separated list of algorithm and/or algorithm:provider
 129 # entries.
 130 #
 131 securerandom.strongAlgorithms=NativePRNGBlocking:SUN
 132 
 133 #
 134 # Class to instantiate as the javax.security.auth.login.Configuration
 135 # provider.
 136 #
 137 login.configuration.provider=sun.security.provider.ConfigFile
 138 
 139 #
 140 # Default login configuration file
 141 #
 142 #login.config.url.1=file:${user.home}/.java.login.config
 143 
 144 #
 145 # Class to instantiate as the system Policy. This is the name of the class
 146 # that will be used as the Policy object.
 147 #
 148 policy.provider=sun.security.provider.PolicyFile
 149 
 150 # The default is to have a single system-wide policy file,
 151 # and a policy file in the user's home directory.
 152 policy.url.1=file:${java.home}/lib/security/java.policy
 153 policy.url.2=file:${user.home}/.java.policy
 154 
 155 # whether or not we expand properties in the policy file
 156 # if this is set to false, properties (${...}) will not be expanded in policy
 157 # files.
 158 policy.expandProperties=true
 159 
 160 # whether or not we allow an extra policy to be passed on the command line
 161 # with -Djava.security.policy=somefile. Comment out this line to disable
 162 # this feature.
 163 policy.allowSystemProperty=true
 164 
 165 # whether or not we look into the IdentityScope for trusted Identities
 166 # when encountering a 1.1 signed JAR file. If the identity is found
 167 # and is trusted, we grant it AllPermission.
 168 policy.ignoreIdentityScope=false
 169 
 170 #
 171 # Default keystore type.
 172 #
 173 keystore.type=jks
 174 
 175 #
 176 # List of comma-separated packages that start with or equal this string
 177 # will cause a security exception to be thrown when
 178 # passed to checkPackageAccess unless the
 179 # corresponding RuntimePermission ("accessClassInPackage."+package) has
 180 # been granted.
 181 package.access=sun.,\
 182                com.sun.xml.internal.,\
 183                com.sun.imageio.,\
 184                com.sun.istack.internal.,\
 185                com.sun.jmx.,\
 186                com.sun.media.sound.,\
 187                com.sun.naming.internal.,\
 188                com.sun.proxy.,\
 189                com.sun.corba.se.,\
 190                com.sun.org.apache.bcel.internal.,\
 191                com.sun.org.apache.regexp.internal.,\
 192                com.sun.org.apache.xerces.internal.,\
 193                com.sun.org.apache.xpath.internal.,\
 194                com.sun.org.apache.xalan.internal.extensions.,\
 195                com.sun.org.apache.xalan.internal.lib.,\
 196                com.sun.org.apache.xalan.internal.res.,\
 197                com.sun.org.apache.xalan.internal.templates.,\
 198                com.sun.org.apache.xalan.internal.utils.,\
 199                com.sun.org.apache.xalan.internal.xslt.,\
 200                com.sun.org.apache.xalan.internal.xsltc.cmdline.,\
 201                com.sun.org.apache.xalan.internal.xsltc.compiler.,\
 202                com.sun.org.apache.xalan.internal.xsltc.trax.,\
 203                com.sun.org.apache.xalan.internal.xsltc.util.,\
 204                com.sun.org.apache.xml.internal.res.,\
 205                com.sun.org.apache.xml.internal.security.,\
 206                com.sun.org.apache.xml.internal.serializer.utils.,\
 207                com.sun.org.apache.xml.internal.utils.,\
 208                com.sun.org.glassfish.,\
 209                com.oracle.xmlns.internal.,\
 210                com.oracle.webservices.internal.,\
 211                oracle.jrockit.jfr.,\
 212                org.jcp.xml.dsig.internal.,\
 213                jdk.internal.,\
 214                jdk.nashorn.internal.,\
 215                jdk.nashorn.tools.,\
 216                com.sun.activation.registries.
 217 
 218 #
 219 # List of comma-separated packages that start with or equal this string
 220 # will cause a security exception to be thrown when
 221 # passed to checkPackageDefinition unless the
 222 # corresponding RuntimePermission ("defineClassInPackage."+package) has
 223 # been granted.
 224 #
 225 # by default, none of the class loaders supplied with the JDK call
 226 # checkPackageDefinition.
 227 #
 228 package.definition=sun.,\
 229                    com.sun.xml.internal.,\
 230                    com.sun.imageio.,\
 231                    com.sun.istack.internal.,\
 232                    com.sun.jmx.,\
 233                    com.sun.media.sound.,\
 234                    com.sun.naming.internal.,\
 235                    com.sun.proxy.,\
 236                    com.sun.corba.se.,\
 237                    com.sun.org.apache.bcel.internal.,\
 238                    com.sun.org.apache.regexp.internal.,\
 239                    com.sun.org.apache.xerces.internal.,\
 240                    com.sun.org.apache.xpath.internal.,\
 241                    com.sun.org.apache.xalan.internal.extensions.,\
 242                    com.sun.org.apache.xalan.internal.lib.,\
 243                    com.sun.org.apache.xalan.internal.res.,\
 244                    com.sun.org.apache.xalan.internal.templates.,\
 245                    com.sun.org.apache.xalan.internal.utils.,\
 246                    com.sun.org.apache.xalan.internal.xslt.,\
 247                    com.sun.org.apache.xalan.internal.xsltc.cmdline.,\
 248                    com.sun.org.apache.xalan.internal.xsltc.compiler.,\
 249                    com.sun.org.apache.xalan.internal.xsltc.trax.,\
 250                    com.sun.org.apache.xalan.internal.xsltc.util.,\
 251                    com.sun.org.apache.xml.internal.res.,\
 252                    com.sun.org.apache.xml.internal.security.,\
 253                    com.sun.org.apache.xml.internal.serializer.utils.,\
 254                    com.sun.org.apache.xml.internal.utils.,\
 255                    com.sun.org.glassfish.,\
 256                    com.oracle.xmlns.internal.,\
 257                    com.oracle.webservices.internal.,\
 258                    oracle.jrockit.jfr.,\
 259                    org.jcp.xml.dsig.internal.,\
 260                    jdk.internal.,\
 261                    jdk.nashorn.internal.,\
 262                    jdk.nashorn.tools.,\
 263                    com.sun.activation.registries.
 264 
 265 #
 266 # Determines whether this properties file can be appended to
 267 # or overridden on the command line via -Djava.security.properties
 268 #
 269 security.overridePropertiesFile=true
 270 
 271 #
 272 # Determines the default key and trust manager factory algorithms for
 273 # the javax.net.ssl package.
 274 #
 275 ssl.KeyManagerFactory.algorithm=SunX509
 276 ssl.TrustManagerFactory.algorithm=PKIX
 277 
 278 #
 279 # The Java-level namelookup cache policy for successful lookups:
 280 #
 281 # any negative value: caching forever
 282 # any positive value: the number of seconds to cache an address for
 283 # zero: do not cache
 284 #
 285 # default value is forever (FOREVER). For security reasons, this
 286 # caching is made forever when a security manager is set. When a security
 287 # manager is not set, the default behavior in this implementation
 288 # is to cache for 30 seconds.
 289 #
 290 # NOTE: setting this to anything other than the default value can have
 291 #       serious security implications. Do not set it unless
 292 #       you are sure you are not exposed to DNS spoofing attack.
 293 #
 294 #networkaddress.cache.ttl=-1
 295 
 296 # The Java-level namelookup cache policy for failed lookups:
 297 #
 298 # any negative value: cache forever
 299 # any positive value: the number of seconds to cache negative lookup results
 300 # zero: do not cache
 301 #
 302 # In some Microsoft Windows networking environments that employ
 303 # the WINS name service in addition to DNS, name service lookups
 304 # that fail may take a noticeably long time to return (approx. 5 seconds).
 305 # For this reason the default caching policy is to maintain these
 306 # results for 10 seconds.
 307 #
 308 #
 309 networkaddress.cache.negative.ttl=10
 310 
 311 #
 312 # Properties to configure OCSP for certificate revocation checking
 313 #
 314 
 315 # Enable OCSP
 316 #
 317 # By default, OCSP is not used for certificate revocation checking.
 318 # This property enables the use of OCSP when set to the value "true".
 319 #
 320 # NOTE: SocketPermission is required to connect to an OCSP responder.
 321 #
 322 # Example,
 323 #   ocsp.enable=true
 324 
 325 #
 326 # Location of the OCSP responder
 327 #
 328 # By default, the location of the OCSP responder is determined implicitly
 329 # from the certificate being validated. This property explicitly specifies
 330 # the location of the OCSP responder. The property is used when the
 331 # Authority Information Access extension (defined in RFC 3280) is absent
 332 # from the certificate or when it requires overriding.
 333 #
 334 # Example,
 335 #   ocsp.responderURL=http://ocsp.example.net:80
 336 
 337 #
 338 # Subject name of the OCSP responder's certificate
 339 #
 340 # By default, the certificate of the OCSP responder is that of the issuer
 341 # of the certificate being validated. This property identifies the certificate
 342 # of the OCSP responder when the default does not apply. Its value is a string
 343 # distinguished name (defined in RFC 2253) which identifies a certificate in
 344 # the set of certificates supplied during cert path validation. In cases where
 345 # the subject name alone is not sufficient to uniquely identify the certificate
 346 # then both the "ocsp.responderCertIssuerName" and
 347 # "ocsp.responderCertSerialNumber" properties must be used instead. When this
 348 # property is set then those two properties are ignored.
 349 #
 350 # Example,
 351 #   ocsp.responderCertSubjectName="CN=OCSP Responder, O=XYZ Corp"
 352 
 353 #
 354 # Issuer name of the OCSP responder's certificate
 355 #
 356 # By default, the certificate of the OCSP responder is that of the issuer
 357 # of the certificate being validated. This property identifies the certificate
 358 # of the OCSP responder when the default does not apply. Its value is a string
 359 # distinguished name (defined in RFC 2253) which identifies a certificate in
 360 # the set of certificates supplied during cert path validation. When this
 361 # property is set then the "ocsp.responderCertSerialNumber" property must also
 362 # be set. When the "ocsp.responderCertSubjectName" property is set then this
 363 # property is ignored.
 364 #
 365 # Example,
 366 #   ocsp.responderCertIssuerName="CN=Enterprise CA, O=XYZ Corp"
 367 
 368 #
 369 # Serial number of the OCSP responder's certificate
 370 #
 371 # By default, the certificate of the OCSP responder is that of the issuer
 372 # of the certificate being validated. This property identifies the certificate
 373 # of the OCSP responder when the default does not apply. Its value is a string
 374 # of hexadecimal digits (colon or space separators may be present) which
 375 # identifies a certificate in the set of certificates supplied during cert path
 376 # validation. When this property is set then the "ocsp.responderCertIssuerName"
 377 # property must also be set. When the "ocsp.responderCertSubjectName" property
 378 # is set then this property is ignored.
 379 #
 380 # Example,
 381 #   ocsp.responderCertSerialNumber=2A:FF:00
 382 
 383 #
 384 # Policy for failed Kerberos KDC lookups:
 385 #
 386 # When a KDC is unavailable (network error, service failure, etc), it is
 387 # put inside a blacklist and accessed less often for future requests. The
 388 # value (case-insensitive) for this policy can be:
 389 #
 390 # tryLast
 391 #    KDCs in the blacklist are always tried after those not on the list.
 392 #
 393 # tryLess[:max_retries,timeout]
 394 #    KDCs in the blacklist are still tried by their order in the configuration,
 395 #    but with smaller max_retries and timeout values. max_retries and timeout
 396 #    are optional numerical parameters (default 1 and 5000, which means once
 397 #    and 5 seconds). Please notes that if any of the values defined here is
 398 #    more than what is defined in krb5.conf, it will be ignored.
 399 #
 400 # Whenever a KDC is detected as available, it is removed from the blacklist.
 401 # The blacklist is reset when krb5.conf is reloaded. You can add
 402 # refreshKrb5Config=true to a JAAS configuration file so that krb5.conf is
 403 # reloaded whenever a JAAS authentication is attempted.
 404 #
 405 # Example,
 406 #   krb5.kdc.bad.policy = tryLast
 407 #   krb5.kdc.bad.policy = tryLess:2,2000
 408 krb5.kdc.bad.policy = tryLast
 409 
 410 # Algorithm restrictions for certification path (CertPath) processing
 411 #
 412 # In some environments, certain algorithms or key lengths may be undesirable
 413 # for certification path building and validation.  For example, "MD2" is
 414 # generally no longer considered to be a secure hash algorithm.  This section
 415 # describes the mechanism for disabling algorithms based on algorithm name
 416 # and/or key length.  This includes algorithms used in certificates, as well
 417 # as revocation information such as CRLs and signed OCSP Responses.
 418 #
 419 # The syntax of the disabled algorithm string is described as this Java
 420 # BNF-style:
 421 #   DisabledAlgorithms:
 422 #       " DisabledAlgorithm { , DisabledAlgorithm } "
 423 #
 424 #   DisabledAlgorithm:
 425 #       AlgorithmName [Constraint]
 426 #
 427 #   AlgorithmName:
 428 #       (see below)
 429 #
 430 #   Constraint:
 431 #       KeySizeConstraint
 432 #
 433 #   KeySizeConstraint:
 434 #       keySize Operator DecimalInteger
 435 #
 436 #   Operator:
 437 #       <= | < | == | != | >= | >
 438 #
 439 #   DecimalInteger:
 440 #       DecimalDigits
 441 #
 442 #   DecimalDigits:
 443 #       DecimalDigit {DecimalDigit}
 444 #
 445 #   DecimalDigit: one of
 446 #       1 2 3 4 5 6 7 8 9 0
 447 #
 448 # The "AlgorithmName" is the standard algorithm name of the disabled
 449 # algorithm. See "Java Cryptography Architecture Standard Algorithm Name
 450 # Documentation" for information about Standard Algorithm Names.  Matching
 451 # is performed using a case-insensitive sub-element matching rule.  (For
 452 # example, in "SHA1withECDSA" the sub-elements are "SHA1" for hashing and
 453 # "ECDSA" for signatures.)  If the assertion "AlgorithmName" is a
 454 # sub-element of the certificate algorithm name, the algorithm will be
 455 # rejected during certification path building and validation.  For example,
 456 # the assertion algorithm name "DSA" will disable all certificate algorithms
 457 # that rely on DSA, such as NONEwithDSA, SHA1withDSA.  However, the assertion
 458 # will not disable algorithms related to "ECDSA".
 459 #
 460 # A "Constraint" provides further guidance for the algorithm being specified.
 461 # The "KeySizeConstraint" requires a key of a valid size range if the
 462 # "AlgorithmName" is of a key algorithm.  The "DecimalInteger" indicates the
 463 # key size specified in number of bits.  For example, "RSA keySize <= 1024"
 464 # indicates that any RSA key with key size less than or equal to 1024 bits
 465 # should be disabled, and "RSA keySize < 1024, RSA keySize > 2048" indicates
 466 # that any RSA key with key size less than 1024 or greater than 2048 should
 467 # be disabled. Note that the "KeySizeConstraint" only makes sense to key
 468 # algorithms.
 469 #
 470 # Note: This property is currently used by Oracle's PKIX implementation. It
 471 # is not guaranteed to be examined and used by other implementations.
 472 #
 473 # Example:
 474 #   jdk.certpath.disabledAlgorithms=MD2, DSA, RSA keySize < 2048
 475 #
 476 #
 477 jdk.certpath.disabledAlgorithms=MD2, RSA keySize < 1024
 478 
 479 # Algorithm restrictions for Secure Socket Layer/Transport Layer Security
 480 # (SSL/TLS) processing
 481 #
 482 # In some environments, certain algorithms or key lengths may be undesirable
 483 # when using SSL/TLS.  This section describes the mechanism for disabling
 484 # algorithms during SSL/TLS security parameters negotiation, including
 485 # protocol version negotiation, cipher suites selection, peer authentication
 486 # and key exchange mechanisms.
 487 #
 488 # Disabled algorithms will not be negotiated for SSL/TLS connections, even
 489 # if they are enabled explicitly in an application.
 490 #
 491 # For PKI-based peer authentication and key exchange mechanisms, this list
 492 # of disabled algorithms will also be checked during certification path
 493 # building and validation, including algorithms used in certificates, as
 494 # well as revocation information such as CRLs and signed OCSP Responses.
 495 # This is in addition to the jdk.certpath.disabledAlgorithms property above.
 496 #
 497 # See the specification of "jdk.certpath.disabledAlgorithms" for the
 498 # syntax of the disabled algorithm string.
 499 #
 500 # Note: This property is currently used by Oracle's JSSE implementation.
 501 # It is not guaranteed to be examined and used by other implementations.
 502 #
 503 # Example:
 504 #   jdk.tls.disabledAlgorithms=MD5, SSLv3, DSA, RSA keySize < 2048
 505 jdk.tls.disabledAlgorithms=SSLv3