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,SHA1PRNG:SUN 131 132 # 133 # Class to instantiate as the javax.security.auth.login.Configuration 134 # provider. 135 # 136 login.configuration.provider=sun.security.provider.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.media.sound.,\ 186 com.sun.naming.internal.,\ 187 com.sun.proxy.,\ 188 com.sun.corba.se.,\ 189 com.sun.org.apache.bcel.internal.,\ 190 com.sun.org.apache.regexp.internal.,\ 191 com.sun.org.apache.xerces.internal.,\ 192 com.sun.org.apache.xpath.internal.,\ 193 com.sun.org.apache.xalan.internal.extensions.,\ 194 com.sun.org.apache.xalan.internal.lib.,\ 195 com.sun.org.apache.xalan.internal.res.,\ 196 com.sun.org.apache.xalan.internal.templates.,\ 197 com.sun.org.apache.xalan.internal.utils.,\ 198 com.sun.org.apache.xalan.internal.xslt.,\ 199 com.sun.org.apache.xalan.internal.xsltc.cmdline.,\ 200 com.sun.org.apache.xalan.internal.xsltc.compiler.,\ 201 com.sun.org.apache.xalan.internal.xsltc.trax.,\ 202 com.sun.org.apache.xalan.internal.xsltc.util.,\ 203 com.sun.org.apache.xml.internal.res.,\ 204 com.sun.org.apache.xml.internal.security.,\ 205 com.sun.org.apache.xml.internal.serializer.utils.,\ 206 com.sun.org.apache.xml.internal.utils.,\ 207 com.sun.org.glassfish.,\ 208 com.oracle.xmlns.internal.,\ 209 com.oracle.webservices.internal.,\ 210 oracle.jrockit.jfr.,\ 211 org.jcp.xml.dsig.internal.,\ 212 jdk.internal.,\ 213 jdk.nashorn.internal.,\ 214 jdk.nashorn.tools.,\ 215 com.sun.java.accessibility. 216 217 # 218 # List of comma-separated packages that start with or equal this string 219 # will cause a security exception to be thrown when 220 # passed to checkPackageDefinition unless the 221 # corresponding RuntimePermission ("defineClassInPackage."+package) has 222 # been granted. 223 # 224 # by default, none of the class loaders supplied with the JDK call 225 # checkPackageDefinition. 226 # 227 package.definition=sun.,\ 228 com.sun.xml.internal.,\ 229 com.sun.imageio.,\ 230 com.sun.istack.internal.,\ 231 com.sun.jmx.,\ 232 com.sun.media.sound.,\ 233 com.sun.naming.internal.,\ 234 com.sun.proxy.,\ 235 com.sun.corba.se.,\ 236 com.sun.org.apache.bcel.internal.,\ 237 com.sun.org.apache.regexp.internal.,\ 238 com.sun.org.apache.xerces.internal.,\ 239 com.sun.org.apache.xpath.internal.,\ 240 com.sun.org.apache.xalan.internal.extensions.,\ 241 com.sun.org.apache.xalan.internal.lib.,\ 242 com.sun.org.apache.xalan.internal.res.,\ 243 com.sun.org.apache.xalan.internal.templates.,\ 244 com.sun.org.apache.xalan.internal.utils.,\ 245 com.sun.org.apache.xalan.internal.xslt.,\ 246 com.sun.org.apache.xalan.internal.xsltc.cmdline.,\ 247 com.sun.org.apache.xalan.internal.xsltc.compiler.,\ 248 com.sun.org.apache.xalan.internal.xsltc.trax.,\ 249 com.sun.org.apache.xalan.internal.xsltc.util.,\ 250 com.sun.org.apache.xml.internal.res.,\ 251 com.sun.org.apache.xml.internal.security.,\ 252 com.sun.org.apache.xml.internal.serializer.utils.,\ 253 com.sun.org.apache.xml.internal.utils.,\ 254 com.sun.org.glassfish.,\ 255 com.oracle.xmlns.internal.,\ 256 com.oracle.webservices.internal.,\ 257 oracle.jrockit.jfr.,\ 258 org.jcp.xml.dsig.internal.,\ 259 jdk.internal.,\ 260 jdk.nashorn.internal.,\ 261 jdk.nashorn.tools.,\ 262 com.sun.java.accessibility. 263 264 # 265 # Determines whether this properties file can be appended to 266 # or overridden on the command line via -Djava.security.properties 267 # 268 security.overridePropertiesFile=true 269 270 # 271 # Determines the default key and trust manager factory algorithms for 272 # the javax.net.ssl package. 273 # 274 ssl.KeyManagerFactory.algorithm=SunX509 275 ssl.TrustManagerFactory.algorithm=PKIX 276 277 # 278 # The Java-level namelookup cache policy for successful lookups: 279 # 280 # any negative value: caching forever 281 # any positive value: the number of seconds to cache an address for 282 # zero: do not cache 283 # 284 # default value is forever (FOREVER). For security reasons, this 285 # caching is made forever when a security manager is set. When a security 286 # manager is not set, the default behavior in this implementation 287 # is to cache for 30 seconds. 288 # 289 # NOTE: setting this to anything other than the default value can have 290 # serious security implications. Do not set it unless 291 # you are sure you are not exposed to DNS spoofing attack. 292 # 293 #networkaddress.cache.ttl=-1 294 295 # The Java-level namelookup cache policy for failed lookups: 296 # 297 # any negative value: cache forever 298 # any positive value: the number of seconds to cache negative lookup results 299 # zero: do not cache 300 # 301 # In some Microsoft Windows networking environments that employ 302 # the WINS name service in addition to DNS, name service lookups 303 # that fail may take a noticeably long time to return (approx. 5 seconds). 304 # For this reason the default caching policy is to maintain these 305 # results for 10 seconds. 306 # 307 # 308 networkaddress.cache.negative.ttl=10 309 310 # 311 # Properties to configure OCSP for certificate revocation checking 312 # 313 314 # Enable OCSP 315 # 316 # By default, OCSP is not used for certificate revocation checking. 317 # This property enables the use of OCSP when set to the value "true". 318 # 319 # NOTE: SocketPermission is required to connect to an OCSP responder. 320 # 321 # Example, 322 # ocsp.enable=true 323 324 # 325 # Location of the OCSP responder 326 # 327 # By default, the location of the OCSP responder is determined implicitly 328 # from the certificate being validated. This property explicitly specifies 329 # the location of the OCSP responder. The property is used when the 330 # Authority Information Access extension (defined in RFC 3280) is absent 331 # from the certificate or when it requires overriding. 332 # 333 # Example, 334 # ocsp.responderURL=http://ocsp.example.net:80 335 336 # 337 # Subject name of the OCSP responder's certificate 338 # 339 # By default, the certificate of the OCSP responder is that of the issuer 340 # of the certificate being validated. This property identifies the certificate 341 # of the OCSP responder when the default does not apply. Its value is a string 342 # distinguished name (defined in RFC 2253) which identifies a certificate in 343 # the set of certificates supplied during cert path validation. In cases where 344 # the subject name alone is not sufficient to uniquely identify the certificate 345 # then both the "ocsp.responderCertIssuerName" and 346 # "ocsp.responderCertSerialNumber" properties must be used instead. When this 347 # property is set then those two properties are ignored. 348 # 349 # Example, 350 # ocsp.responderCertSubjectName="CN=OCSP Responder, O=XYZ Corp" 351 352 # 353 # Issuer name of the OCSP responder's certificate 354 # 355 # By default, the certificate of the OCSP responder is that of the issuer 356 # of the certificate being validated. This property identifies the certificate 357 # of the OCSP responder when the default does not apply. Its value is a string 358 # distinguished name (defined in RFC 2253) which identifies a certificate in 359 # the set of certificates supplied during cert path validation. When this 360 # property is set then the "ocsp.responderCertSerialNumber" property must also 361 # be set. When the "ocsp.responderCertSubjectName" property is set then this 362 # property is ignored. 363 # 364 # Example, 365 # ocsp.responderCertIssuerName="CN=Enterprise CA, O=XYZ Corp" 366 367 # 368 # Serial number of the OCSP responder's certificate 369 # 370 # By default, the certificate of the OCSP responder is that of the issuer 371 # of the certificate being validated. This property identifies the certificate 372 # of the OCSP responder when the default does not apply. Its value is a string 373 # of hexadecimal digits (colon or space separators may be present) which 374 # identifies a certificate in the set of certificates supplied during cert path 375 # validation. When this property is set then the "ocsp.responderCertIssuerName" 376 # property must also be set. When the "ocsp.responderCertSubjectName" property 377 # is set then this property is ignored. 378 # 379 # Example, 380 # ocsp.responderCertSerialNumber=2A:FF:00 381 382 # Algorithm restrictions for certification path (CertPath) processing 383 # 384 # In some environments, certain algorithms or key lengths may be undesirable 385 # for certification path building and validation. For example, "MD2" is 386 # generally no longer considered to be a secure hash algorithm. This section 387 # describes the mechanism for disabling algorithms based on algorithm name 388 # and/or key length. This includes algorithms used in certificates, as well 389 # as revocation information such as CRLs and signed OCSP Responses. 390 # 391 # The syntax of the disabled algorithm string is described as this Java 392 # BNF-style: 393 # DisabledAlgorithms: 394 # " DisabledAlgorithm { , DisabledAlgorithm } " 395 # 396 # DisabledAlgorithm: 397 # AlgorithmName [Constraint] 398 # 399 # AlgorithmName: 400 # (see below) 401 # 402 # Constraint: 403 # KeySizeConstraint 404 # 405 # KeySizeConstraint: 406 # keySize Operator DecimalInteger 407 # 408 # Operator: 409 # <= | < | == | != | >= | > 410 # 411 # DecimalInteger: 412 # DecimalDigits 413 # 414 # DecimalDigits: 415 # DecimalDigit {DecimalDigit} 416 # 417 # DecimalDigit: one of 418 # 1 2 3 4 5 6 7 8 9 0 419 # 420 # The "AlgorithmName" is the standard algorithm name of the disabled 421 # algorithm. See "Java Cryptography Architecture Standard Algorithm Name 422 # Documentation" for information about Standard Algorithm Names. Matching 423 # is performed using a case-insensitive sub-element matching rule. (For 424 # example, in "SHA1withECDSA" the sub-elements are "SHA1" for hashing and 425 # "ECDSA" for signatures.) If the assertion "AlgorithmName" is a 426 # sub-element of the certificate algorithm name, the algorithm will be 427 # rejected during certification path building and validation. For example, 428 # the assertion algorithm name "DSA" will disable all certificate algorithms 429 # that rely on DSA, such as NONEwithDSA, SHA1withDSA. However, the assertion 430 # will not disable algorithms related to "ECDSA". 431 # 432 # A "Constraint" provides further guidance for the algorithm being specified. 433 # The "KeySizeConstraint" requires a key of a valid size range if the 434 # "AlgorithmName" is of a key algorithm. The "DecimalInteger" indicates the 435 # key size specified in number of bits. For example, "RSA keySize <= 1024" 436 # indicates that any RSA key with key size less than or equal to 1024 bits 437 # should be disabled, and "RSA keySize < 1024, RSA keySize > 2048" indicates 438 # that any RSA key with key size less than 1024 or greater than 2048 should 439 # be disabled. Note that the "KeySizeConstraint" only makes sense to key 440 # algorithms. 441 # 442 # Note: This property is currently used by Oracle's PKIX implementation. It 443 # is not guaranteed to be examined and used by other implementations. 444 # 445 # Example: 446 # jdk.certpath.disabledAlgorithms=MD2, DSA, RSA keySize < 2048 447 # 448 # 449 jdk.certpath.disabledAlgorithms=MD2, MD5, RSA keySize < 1024 450 451 # Algorithm restrictions for Secure Socket Layer/Transport Layer Security 452 # (SSL/TLS) processing 453 # 454 # In some environments, certain algorithms or key lengths may be undesirable 455 # when using SSL/TLS. This section describes the mechanism for disabling 456 # algorithms during SSL/TLS security parameters negotiation, including cipher 457 # suites selection, peer authentication and key exchange mechanisms. 458 # 459 # For PKI-based peer authentication and key exchange mechanisms, this list 460 # of disabled algorithms will also be checked during certification path 461 # building and validation, including algorithms used in certificates, as 462 # well as revocation information such as CRLs and signed OCSP Responses. 463 # This is in addition to the jdk.certpath.disabledAlgorithms property above. 464 # 465 # See the specification of "jdk.certpath.disabledAlgorithms" for the 466 # syntax of the disabled algorithm string. 467 # 468 # Note: This property is currently used by Oracle's JSSE implementation. 469 # It is not guaranteed to be examined and used by other implementations. 470 # 471 # Example: 472 # jdk.tls.disabledAlgorithms=MD5, SHA1, DSA, RSA keySize < 2048