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