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