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