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