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