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