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