1 # 2 # This is the "master security properties file". 3 # 4 # In this file, various security properties are set for use by 5 # java.security classes. This is where users can statically register 6 # Cryptography Package Providers ("providers" for short). The term 7 # "provider" refers to a package or set of packages that supply a 8 # concrete implementation of a subset of the cryptography aspects of 9 # the Java Security API. A provider may, for example, implement one or 10 # more digital signature algorithms or message digest algorithms. 11 # 12 # Each provider must implement a subclass of the Provider class. 13 # To register a provider in this master security properties file, 14 # specify the Provider subclass name and priority in the format 15 # 16 # security.provider.<n>=<className> 17 # 18 # This declares a provider, and specifies its preference 19 # order n. The preference order is the order in which providers are 20 # searched for requested algorithms (when no specific provider is 21 # requested). The order is 1-based; 1 is the most preferred, followed 22 # by 2, and so on. 23 # 24 # <className> must specify the subclass of the Provider class whose 25 # constructor sets the values of various properties that are required 26 # for the Java Security API to look up the algorithms or other 27 # facilities implemented by the provider. 28 # 29 # There must be at least one provider specification in java.security. 30 # There is a default provider that comes standard with the JDK. It 31 # is called the "SUN" provider, and its Provider subclass 32 # named Sun appears in the sun.security.provider package. Thus, the 33 # "SUN" provider is registered via the following: 34 # 35 # security.provider.1=sun.security.provider.Sun 36 # 37 # (The number 1 is used for the default provider.) 38 # 39 # Note: Providers can be dynamically registered instead by calls to 40 # either the addProvider or insertProviderAt method in the Security 41 # class. 42 43 # 44 # List of providers and their preference orders (see above): 45 # 46 security.provider.1=sun.security.provider.Sun 47 security.provider.2=sun.security.rsa.SunRsaSign 48 security.provider.3=sun.security.ec.SunEC 49 security.provider.4=com.sun.net.ssl.internal.ssl.Provider 50 security.provider.5=com.sun.crypto.provider.SunJCE 51 security.provider.6=sun.security.jgss.SunProvider 52 security.provider.7=com.sun.security.sasl.Provider 53 security.provider.8=org.jcp.xml.dsig.internal.dom.XMLDSigRI 54 security.provider.9=sun.security.smartcardio.SunPCSC 55 security.provider.10=apple.security.AppleProvider 56 57 # 58 # Select the source of seed data for SecureRandom. By default an 59 # attempt is made to use the entropy gathering device specified by 60 # the securerandom.source property. If an exception occurs when 61 # accessing the URL then the traditional system/thread activity 62 # algorithm is used. 63 # 64 # On Solaris and Linux systems, if file:/dev/urandom is specified and it 65 # exists, a special SecureRandom implementation is activated by default. 66 # This "NativePRNG" reads random bytes directly from /dev/urandom. 67 # 68 # On Windows systems, the URLs file:/dev/random and file:/dev/urandom 69 # enables use of the Microsoft CryptoAPI seed functionality. 70 # 71 securerandom.source=file:/dev/urandom 72 # 73 # The entropy gathering device is described as a URL and can also 74 # be specified with the system property "java.security.egd". For example, 75 # -Djava.security.egd=file:/dev/urandom 76 # Specifying this system property will override the securerandom.source 77 # setting. 78 79 # 80 # Class to instantiate as the javax.security.auth.login.Configuration 81 # provider. 82 # 83 login.configuration.provider=com.sun.security.auth.login.ConfigFile 84 85 # 86 # Default login configuration file 87 # 88 #login.config.url.1=file:${user.home}/.java.login.config 89 90 # 91 # Class to instantiate as the system Policy. This is the name of the class 92 # that will be used as the Policy object. 93 # 94 policy.provider=sun.security.provider.PolicyFile 95 96 # The default is to have a single system-wide policy file, 97 # and a policy file in the user's home directory. 98 policy.url.1=file:${java.home}/lib/security/java.policy 99 policy.url.2=file:${user.home}/.java.policy 100 101 # whether or not we expand properties in the policy file 102 # if this is set to false, properties (${...}) will not be expanded in policy 103 # files. 104 policy.expandProperties=true 105 106 # whether or not we allow an extra policy to be passed on the command line 107 # with -Djava.security.policy=somefile. Comment out this line to disable 108 # this feature. 109 policy.allowSystemProperty=true 110 111 # whether or not we look into the IdentityScope for trusted Identities 112 # when encountering a 1.1 signed JAR file. If the identity is found 113 # and is trusted, we grant it AllPermission. 114 policy.ignoreIdentityScope=false 115 116 # 117 # Default keystore type. 118 # 119 keystore.type=jks 120 121 # 122 # List of comma-separated packages that start with or equal this string 123 # will cause a security exception to be thrown when 124 # passed to checkPackageAccess unless the 125 # corresponding RuntimePermission ("accessClassInPackage."+package) has 126 # been granted. 127 package.access=sun.,\ 128 com.sun.xml.internal.bind.,\ 129 com.sun.xml.internal.org.jvnet.staxex.,\ 130 com.sun.xml.internal.ws.,\ 131 com.sun.imageio.,\ 132 com.sun.istack.internal.,\ 133 com.sun.jmx.defaults.,\ 134 com.sun.jmx.remote.util.,\ 135 com.sun.org.apache.xerces.internal.utils.,\ 136 com.sun.org.apache.xalan.internal.utils.,\ 137 com.sun.org.glassfish.external.,\ 138 com.sun.org.glassfish.gmbal.,\ 139 oracle.jrockit.jfr.,\ 140 apple. 141 142 # 143 # List of comma-separated packages that start with or equal this string 144 # will cause a security exception to be thrown when 145 # passed to checkPackageDefinition unless the 146 # corresponding RuntimePermission ("defineClassInPackage."+package) has 147 # been granted. 148 # 149 # by default, none of the class loaders supplied with the JDK call 150 # checkPackageDefinition. 151 # 152 package.definition=sun.,\ 153 com.sun.xml.internal.bind.,\ 154 com.sun.xml.internal.org.jvnet.staxex.,\ 155 com.sun.xml.internal.ws.,\ 156 com.sun.imageio.,\ 157 com.sun.istack.internal.,\ 158 com.sun.jmx.defaults.,\ 159 com.sun.jmx.remote.util.,\ 160 com.sun.org.apache.xerces.internal.utils.,\ 161 com.sun.org.apache.xalan.internal.utils.,\ 162 com.sun.org.glassfish.external.,\ 163 com.sun.org.glassfish.gmbal.,\ 164 oracle.jrockit.jfr.,\ 165 apple. 166 167 # 168 # Determines whether this properties file can be appended to 169 # or overridden on the command line via -Djava.security.properties 170 # 171 security.overridePropertiesFile=true 172 173 # 174 # Determines the default key and trust manager factory algorithms for 175 # the javax.net.ssl package. 176 # 177 ssl.KeyManagerFactory.algorithm=SunX509 178 ssl.TrustManagerFactory.algorithm=PKIX 179 180 # 181 # The Java-level namelookup cache policy for successful lookups: 182 # 183 # any negative value: caching forever 184 # any positive value: the number of seconds to cache an address for 185 # zero: do not cache 186 # 187 # default value is forever (FOREVER). For security reasons, this 188 # caching is made forever when a security manager is set. When a security 189 # manager is not set, the default behavior in this implementation 190 # is to cache for 30 seconds. 191 # 192 # NOTE: setting this to anything other than the default value can have 193 # serious security implications. Do not set it unless 194 # you are sure you are not exposed to DNS spoofing attack. 195 # 196 #networkaddress.cache.ttl=-1 197 198 # The Java-level namelookup cache policy for failed lookups: 199 # 200 # any negative value: cache forever 201 # any positive value: the number of seconds to cache negative lookup results 202 # zero: do not cache 203 # 204 # In some Microsoft Windows networking environments that employ 205 # the WINS name service in addition to DNS, name service lookups 206 # that fail may take a noticeably long time to return (approx. 5 seconds). 207 # For this reason the default caching policy is to maintain these 208 # results for 10 seconds. 209 # 210 # 211 networkaddress.cache.negative.ttl=10 212 213 # 214 # Properties to configure OCSP for certificate revocation checking 215 # 216 217 # Enable OCSP 218 # 219 # By default, OCSP is not used for certificate revocation checking. 220 # This property enables the use of OCSP when set to the value "true". 221 # 222 # NOTE: SocketPermission is required to connect to an OCSP responder. 223 # 224 # Example, 225 # ocsp.enable=true 226 227 # 228 # Location of the OCSP responder 229 # 230 # By default, the location of the OCSP responder is determined implicitly 231 # from the certificate being validated. This property explicitly specifies 232 # the location of the OCSP responder. The property is used when the 233 # Authority Information Access extension (defined in RFC 3280) is absent 234 # from the certificate or when it requires overriding. 235 # 236 # Example, 237 # ocsp.responderURL=http://ocsp.example.net:80 238 239 # 240 # Subject name of the OCSP responder's certificate 241 # 242 # By default, the certificate of the OCSP responder is that of the issuer 243 # of the certificate being validated. This property identifies the certificate 244 # of the OCSP responder when the default does not apply. Its value is a string 245 # distinguished name (defined in RFC 2253) which identifies a certificate in 246 # the set of certificates supplied during cert path validation. In cases where 247 # the subject name alone is not sufficient to uniquely identify the certificate 248 # then both the "ocsp.responderCertIssuerName" and 249 # "ocsp.responderCertSerialNumber" properties must be used instead. When this 250 # property is set then those two properties are ignored. 251 # 252 # Example, 253 # ocsp.responderCertSubjectName="CN=OCSP Responder, O=XYZ Corp" 254 255 # 256 # Issuer name of the OCSP responder's certificate 257 # 258 # By default, the certificate of the OCSP responder is that of the issuer 259 # of the certificate being validated. This property identifies the certificate 260 # of the OCSP responder when the default does not apply. Its value is a string 261 # distinguished name (defined in RFC 2253) which identifies a certificate in 262 # the set of certificates supplied during cert path validation. When this 263 # property is set then the "ocsp.responderCertSerialNumber" property must also 264 # be set. When the "ocsp.responderCertSubjectName" property is set then this 265 # property is ignored. 266 # 267 # Example, 268 # ocsp.responderCertIssuerName="CN=Enterprise CA, O=XYZ Corp" 269 270 # 271 # Serial number of the OCSP responder's certificate 272 # 273 # By default, the certificate of the OCSP responder is that of the issuer 274 # of the certificate being validated. This property identifies the certificate 275 # of the OCSP responder when the default does not apply. Its value is a string 276 # of hexadecimal digits (colon or space separators may be present) which 277 # identifies a certificate in the set of certificates supplied during cert path 278 # validation. When this property is set then the "ocsp.responderCertIssuerName" 279 # property must also be set. When the "ocsp.responderCertSubjectName" property 280 # is set then this property is ignored. 281 # 282 # Example, 283 # ocsp.responderCertSerialNumber=2A:FF:00 284 285 # 286 # Policy for failed Kerberos KDC lookups: 287 # 288 # When a KDC is unavailable (network error, service failure, etc), it is 289 # put inside a blacklist and accessed less often for future requests. The 290 # value (case-insensitive) for this policy can be: 291 # 292 # tryLast 293 # KDCs in the blacklist are always tried after those not on the list. 294 # 295 # tryLess[:max_retries,timeout] 296 # KDCs in the blacklist are still tried by their order in the configuration, 297 # but with smaller max_retries and timeout values. max_retries and timeout 298 # are optional numerical parameters (default 1 and 5000, which means once 299 # and 5 seconds). Please notes that if any of the values defined here is 300 # more than what is defined in krb5.conf, it will be ignored. 301 # 302 # Whenever a KDC is detected as available, it is removed from the blacklist. 303 # The blacklist is reset when krb5.conf is reloaded. You can add 304 # refreshKrb5Config=true to a JAAS configuration file so that krb5.conf is 305 # reloaded whenever a JAAS authentication is attempted. 306 # 307 # Example, 308 # krb5.kdc.bad.policy = tryLast 309 # krb5.kdc.bad.policy = tryLess:2,2000 310 krb5.kdc.bad.policy = tryLast 311 312 # Algorithm restrictions for certification path (CertPath) processing 313 # 314 # In some environments, certain algorithms or key lengths may be undesirable 315 # for certification path building and validation. For example, "MD2" is 316 # generally no longer considered to be a secure hash algorithm. This section 317 # describes the mechanism for disabling algorithms based on algorithm name 318 # and/or key length. This includes algorithms used in certificates, as well 319 # as revocation information such as CRLs and signed OCSP Responses. 320 # 321 # The syntax of the disabled algorithm string is described as this Java 322 # BNF-style: 323 # DisabledAlgorithms: 324 # " DisabledAlgorithm { , DisabledAlgorithm } " 325 # 326 # DisabledAlgorithm: 327 # AlgorithmName [Constraint] 328 # 329 # AlgorithmName: 330 # (see below) 331 # 332 # Constraint: 333 # KeySizeConstraint 334 # 335 # KeySizeConstraint: 336 # keySize Operator DecimalInteger 337 # 338 # Operator: 339 # <= | < | == | != | >= | > 340 # 341 # DecimalInteger: 342 # DecimalDigits 343 # 344 # DecimalDigits: 345 # DecimalDigit {DecimalDigit} 346 # 347 # DecimalDigit: one of 348 # 1 2 3 4 5 6 7 8 9 0 349 # 350 # The "AlgorithmName" is the standard algorithm name of the disabled 351 # algorithm. See "Java Cryptography Architecture Standard Algorithm Name 352 # Documentation" for information about Standard Algorithm Names. Matching 353 # is performed using a case-insensitive sub-element matching rule. (For 354 # example, in "SHA1withECDSA" the sub-elements are "SHA1" for hashing and 355 # "ECDSA" for signatures.) If the assertion "AlgorithmName" is a 356 # sub-element of the certificate algorithm name, the algorithm will be 357 # rejected during certification path building and validation. For example, 358 # the assertion algorithm name "DSA" will disable all certificate algorithms 359 # that rely on DSA, such as NONEwithDSA, SHA1withDSA. However, the assertion 360 # will not disable algorithms related to "ECDSA". 361 # 362 # A "Constraint" provides further guidance for the algorithm being specified. 363 # The "KeySizeConstraint" requires a key of a valid size range if the 364 # "AlgorithmName" is of a key algorithm. The "DecimalInteger" indicates the 365 # key size specified in number of bits. For example, "RSA keySize <= 1024" 366 # indicates that any RSA key with key size less than or equal to 1024 bits 367 # should be disabled, and "RSA keySize < 1024, RSA keySize > 2048" indicates 368 # that any RSA key with key size less than 1024 or greater than 2048 should 369 # be disabled. Note that the "KeySizeConstraint" only makes sense to key 370 # algorithms. 371 # 372 # Note: This property is currently used by Oracle's PKIX implementation. It 373 # is not guaranteed to be examined and used by other implementations. 374 # 375 # Example: 376 # jdk.certpath.disabledAlgorithms=MD2, DSA, RSA keySize < 2048 377 # 378 # 379 jdk.certpath.disabledAlgorithms=MD2 380 381 # Algorithm restrictions for Secure Socket Layer/Transport Layer Security 382 # (SSL/TLS) processing 383 # 384 # In some environments, certain algorithms or key lengths may be undesirable 385 # when using SSL/TLS. This section describes the mechanism for disabling 386 # algorithms during SSL/TLS security parameters negotiation, including cipher 387 # suites selection, peer authentication and key exchange mechanisms. 388 # 389 # For PKI-based peer authentication and key exchange mechanisms, this list 390 # of disabled algorithms will also be checked during certification path 391 # building and validation, including algorithms used in certificates, as 392 # well as revocation information such as CRLs and signed OCSP Responses. 393 # This is in addition to the jdk.certpath.disabledAlgorithms property above. 394 # 395 # See the specification of "jdk.certpath.disabledAlgorithms" for the 396 # syntax of the disabled algorithm string. 397 # 398 # Note: This property is currently used by Oracle's JSSE implementation. 399 # It is not guaranteed to be examined and used by other implementations. 400 # 401 # Example: 402 # jdk.tls.disabledAlgorithms=MD5, SHA1, DSA, RSA keySize < 2048 403