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.,com.sun.imageio.
127
128 #
129 # List of comma-separated packages that start with or equal this string
130 # will cause a security exception to be thrown when
131 # passed to checkPackageDefinition unless the
132 # corresponding RuntimePermission ("defineClassInPackage."+package) has
133 # been granted.
134 #
135 # by default, no packages are restricted for definition, and none of
136 # the class loaders supplied with the JDK call checkPackageDefinition.
137 #
138 #package.definition=
139
140 #
141 # Determines whether this properties file can be appended to
142 # or overridden on the command line via -Djava.security.properties
143 #
144 security.overridePropertiesFile=true
145
146 #
147 # Determines the default key and trust manager factory algorithms for
148 # the javax.net.ssl package.
149 #
150 ssl.KeyManagerFactory.algorithm=SunX509
151 ssl.TrustManagerFactory.algorithm=PKIX
152
153 #
154 # The Java-level namelookup cache policy for successful lookups:
155 #
156 # any negative value: caching forever
157 # any positive value: the number of seconds to cache an address for
158 # zero: do not cache
159 #
160 # default value is forever (FOREVER). For security reasons, this
161 # caching is made forever when a security manager is set. When a security
162 # manager is not set, the default behavior in this implementation
163 # is to cache for 30 seconds.
164 #
165 # NOTE: setting this to anything other than the default value can have
166 # serious security implications. Do not set it unless
167 # you are sure you are not exposed to DNS spoofing attack.
168 #
169 #networkaddress.cache.ttl=-1
170
171 # The Java-level namelookup cache policy for failed lookups:
172 #
173 # any negative value: cache forever
174 # any positive value: the number of seconds to cache negative lookup results
175 # zero: do not cache
176 #
177 # In some Microsoft Windows networking environments that employ
178 # the WINS name service in addition to DNS, name service lookups
179 # that fail may take a noticeably long time to return (approx. 5 seconds).
180 # For this reason the default caching policy is to maintain these
181 # results for 10 seconds.
182 #
183 #
184 networkaddress.cache.negative.ttl=10
185
186 #
187 # Properties to configure OCSP for certificate revocation checking
188 #
189
190 # Enable OCSP
191 #
192 # By default, OCSP is not used for certificate revocation checking.
193 # This property enables the use of OCSP when set to the value "true".
194 #
195 # NOTE: SocketPermission is required to connect to an OCSP responder.
196 #
197 # Example,
198 # ocsp.enable=true
199
200 #
201 # Location of the OCSP responder
202 #
203 # By default, the location of the OCSP responder is determined implicitly
204 # from the certificate being validated. This property explicitly specifies
205 # the location of the OCSP responder. The property is used when the
206 # Authority Information Access extension (defined in RFC 3280) is absent
207 # from the certificate or when it requires overriding.
208 #
209 # Example,
210 # ocsp.responderURL=http://ocsp.example.net:80
211
212 #
213 # Subject name of the OCSP responder's certificate
214 #
215 # By default, the certificate of the OCSP responder is that of the issuer
216 # of the certificate being validated. This property identifies the certificate
217 # of the OCSP responder when the default does not apply. Its value is a string
218 # distinguished name (defined in RFC 2253) which identifies a certificate in
219 # the set of certificates supplied during cert path validation. In cases where
220 # the subject name alone is not sufficient to uniquely identify the certificate
221 # then both the "ocsp.responderCertIssuerName" and
222 # "ocsp.responderCertSerialNumber" properties must be used instead. When this
223 # property is set then those two properties are ignored.
224 #
225 # Example,
226 # ocsp.responderCertSubjectName="CN=OCSP Responder, O=XYZ Corp"
227
228 #
229 # Issuer name of the OCSP responder's certificate
230 #
231 # By default, the certificate of the OCSP responder is that of the issuer
232 # of the certificate being validated. This property identifies the certificate
233 # of the OCSP responder when the default does not apply. Its value is a string
234 # distinguished name (defined in RFC 2253) which identifies a certificate in
235 # the set of certificates supplied during cert path validation. When this
236 # property is set then the "ocsp.responderCertSerialNumber" property must also
237 # be set. When the "ocsp.responderCertSubjectName" property is set then this
238 # property is ignored.
239 #
240 # Example,
241 # ocsp.responderCertIssuerName="CN=Enterprise CA, O=XYZ Corp"
242
243 #
244 # Serial number of the OCSP responder's certificate
245 #
246 # By default, the certificate of the OCSP responder is that of the issuer
247 # of the certificate being validated. This property identifies the certificate
248 # of the OCSP responder when the default does not apply. Its value is a string
249 # of hexadecimal digits (colon or space separators may be present) which
250 # identifies a certificate in the set of certificates supplied during cert path
251 # validation. When this property is set then the "ocsp.responderCertIssuerName"
252 # property must also be set. When the "ocsp.responderCertSubjectName" property
253 # is set then this property is ignored.
254 #
255 # Example,
256 # ocsp.responderCertSerialNumber=2A:FF:00
257
258 #
259 # Policy for failed Kerberos KDC lookups:
260 #
261 # When a KDC is unavailable (network error, service failure, etc), it is
262 # put inside a blacklist and accessed less often for future requests. The
263 # value (case-insensitive) for this policy can be:
264 #
265 # tryLast
266 # KDCs in the blacklist are always tried after those not on the list.
267 #
268 # tryLess[:max_retries,timeout]
269 # KDCs in the blacklist are still tried by their order in the configuration,
270 # but with smaller max_retries and timeout values. max_retries and timeout
271 # are optional numerical parameters (default 1 and 5000, which means once
272 # and 5 seconds). Please notes that if any of the values defined here is
273 # more than what is defined in krb5.conf, it will be ignored.
274 #
275 # Whenever a KDC is detected as available, it is removed from the blacklist.
276 # The blacklist is reset when krb5.conf is reloaded. You can add
277 # refreshKrb5Config=true to a JAAS configuration file so that krb5.conf is
278 # reloaded whenever a JAAS authentication is attempted.
279 #
280 # Example,
281 # krb5.kdc.bad.policy = tryLast
282 # krb5.kdc.bad.policy = tryLess:2,2000
283 krb5.kdc.bad.policy = tryLast
284
285 # Algorithm restrictions for certification path (CertPath) processing
286 #
287 # In some environments, certain algorithms or key lengths may be undesirable
288 # for certification path building and validation. For example, "MD2" is
289 # generally no longer considered to be a secure hash algorithm. This section
290 # describes the mechanism for disabling algorithms based on algorithm name
291 # and/or key length. This includes algorithms used in certificates, as well
292 # as revocation information such as CRLs and signed OCSP Responses.
293 #
294 # The syntax of the disabled algorithm string is described as this Java
295 # BNF-style:
296 # DisabledAlgorithms:
297 # " DisabledAlgorithm { , DisabledAlgorithm } "
298 #
299 # DisabledAlgorithm:
300 # AlgorithmName [Constraint]
301 #
302 # AlgorithmName:
303 # (see below)
304 #
305 # Constraint:
306 # KeySizeConstraint
307 #
308 # KeySizeConstraint:
309 # keySize Operator DecimalInteger
310 #
311 # Operator:
312 # <= | < | == | != | >= | >
313 #
314 # DecimalInteger:
315 # DecimalDigits
316 #
317 # DecimalDigits:
318 # DecimalDigit {DecimalDigit}
319 #
320 # DecimalDigit: one of
321 # 1 2 3 4 5 6 7 8 9 0
322 #
323 # The "AlgorithmName" is the standard algorithm name of the disabled
324 # algorithm. See "Java Cryptography Architecture Standard Algorithm Name
325 # Documentation" for information about Standard Algorithm Names. Matching
326 # is performed using a case-insensitive sub-element matching rule. (For
327 # example, in "SHA1withECDSA" the sub-elements are "SHA1" for hashing and
328 # "ECDSA" for signatures.) If the assertion "AlgorithmName" is a
329 # sub-element of the certificate algorithm name, the algorithm will be
330 # rejected during certification path building and validation. For example,
331 # the assertion algorithm name "DSA" will disable all certificate algorithms
332 # that rely on DSA, such as NONEwithDSA, SHA1withDSA. However, the assertion
333 # will not disable algorithms related to "ECDSA".
334 #
335 # A "Constraint" provides further guidance for the algorithm being specified.
336 # The "KeySizeConstraint" requires a key of a valid size range if the
337 # "AlgorithmName" is of a key algorithm. The "DecimalInteger" indicates the
338 # key size specified in number of bits. For example, "RSA keySize <= 1024"
339 # indicates that any RSA key with key size less than or equal to 1024 bits
340 # should be disabled, and "RSA keySize < 1024, RSA keySize > 2048" indicates
341 # that any RSA key with key size less than 1024 or greater than 2048 should
342 # be disabled. Note that the "KeySizeConstraint" only makes sense to key
343 # algorithms.
344 #
345 # Note: This property is currently used by Oracle's PKIX implementation. It
346 # is not guaranteed to be examined and used by other implementations.
347 #
348 # Example:
349 # jdk.certpath.disabledAlgorithms=MD2, DSA, RSA keySize < 2048
350 #
351 #
352 jdk.certpath.disabledAlgorithms=MD2
353
354 # Algorithm restrictions for Secure Socket Layer/Transport Layer Security
355 # (SSL/TLS) processing
356 #
357 # In some environments, certain algorithms or key lengths may be undesirable
358 # when using SSL/TLS. This section describes the mechanism for disabling
359 # algorithms during SSL/TLS security parameters negotiation, including cipher
360 # suites selection, peer authentication and key exchange mechanisms.
361 #
362 # For PKI-based peer authentication and key exchange mechanisms, this list
363 # of disabled algorithms will also be checked during certification path
364 # building and validation, including algorithms used in certificates, as
365 # well as revocation information such as CRLs and signed OCSP Responses.
366 # This is in addition to the jdk.certpath.disabledAlgorithms property above.
367 #
368 # See the specification of "jdk.certpath.disabledAlgorithms" for the
369 # syntax of the disabled algorithm string.
370 #
371 # Note: This property is currently used by Oracle's JSSE implementation.
372 # It is not guaranteed to be examined and used by other implementations.
373 #
374 # Example:
375 # jdk.tls.disabledAlgorithms=MD5, SHA1, DSA, RSA keySize < 2048
376