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