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