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