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