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