blob: 6908e831bfb97925fcf724d04c7c50bb5b34a675 [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.,\
mullanbd2ff8c2013-04-22 11:23:33 +0100206 org.jcp.xml.dsig.internal.,\
wetmore5f58e202013-04-11 21:03:24 -0700207 jdk.internal.,\
208 jdk.nashorn.internal.,\
209 jdk.nashorn.tools.
duke6e45e102007-12-01 00:00:00 +0000210
duke6e45e102007-12-01 00:00:00 +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#
mullanee9229d2012-02-22 15:38:24 -0500219# by default, none of the class loaders supplied with the JDK call
220# checkPackageDefinition.
duke6e45e102007-12-01 00:00:00 +0000221#
ewendeli69845692013-01-28 11:07:07 +0100222package.definition=sun.,\
mkosa265cf42013-03-07 07:19:35 -0500223 com.sun.xml.internal.,\
ewendeli69845692013-01-28 11:07:07 +0100224 com.sun.imageio.,\
225 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.,\
ewendeli69845692013-01-28 11:07:07 +0100236 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.,\
mullanbd2ff8c2013-04-22 11:23:33 +0100243 com.sun.org.apache.xml.internal.security.,\
joehwf5a92592013-02-18 13:02:09 -0800244 com.sun.org.apache.xml.internal.serializer.utils.,\
245 com.sun.org.apache.xml.internal.utils.,\
mullanf180f522013-03-27 10:37:46 +0000246 com.sun.org.glassfish.,\
alanba3151942013-04-09 15:51:50 +0100247 com.oracle.xmlns.internal.,\
248 com.oracle.webservices.internal.,\
mullanbd2ff8c2013-04-22 11:23:33 +0100249 org.jcp.xml.dsig.internal.,\
wetmore5f58e202013-04-11 21:03:24 -0700250 jdk.internal.,\
251 jdk.nashorn.internal.,\
252 jdk.nashorn.tools.
duke6e45e102007-12-01 00:00:00 +0000253
duke6e45e102007-12-01 00:00:00 +0000254
255#
256# Determines whether this properties file can be appended to
257# or overridden on the command line via -Djava.security.properties
258#
259security.overridePropertiesFile=true
260
261#
weijun0f0fb6a2009-12-24 13:56:19 +0800262# Determines the default key and trust manager factory algorithms for
duke6e45e102007-12-01 00:00:00 +0000263# the javax.net.ssl package.
264#
265ssl.KeyManagerFactory.algorithm=SunX509
266ssl.TrustManagerFactory.algorithm=PKIX
267
268#
269# The Java-level namelookup cache policy for successful lookups:
270#
271# any negative value: caching forever
272# any positive value: the number of seconds to cache an address for
273# zero: do not cache
274#
275# default value is forever (FOREVER). For security reasons, this
276# caching is made forever when a security manager is set. When a security
277# manager is not set, the default behavior in this implementation
278# is to cache for 30 seconds.
279#
280# NOTE: setting this to anything other than the default value can have
weijun0f0fb6a2009-12-24 13:56:19 +0800281# serious security implications. Do not set it unless
duke6e45e102007-12-01 00:00:00 +0000282# you are sure you are not exposed to DNS spoofing attack.
283#
weijun0f0fb6a2009-12-24 13:56:19 +0800284#networkaddress.cache.ttl=-1
duke6e45e102007-12-01 00:00:00 +0000285
286# The Java-level namelookup cache policy for failed lookups:
287#
288# any negative value: cache forever
289# any positive value: the number of seconds to cache negative lookup results
290# zero: do not cache
291#
292# In some Microsoft Windows networking environments that employ
293# the WINS name service in addition to DNS, name service lookups
294# that fail may take a noticeably long time to return (approx. 5 seconds).
295# For this reason the default caching policy is to maintain these
weijun0f0fb6a2009-12-24 13:56:19 +0800296# results for 10 seconds.
duke6e45e102007-12-01 00:00:00 +0000297#
298#
299networkaddress.cache.negative.ttl=10
300
301#
302# Properties to configure OCSP for certificate revocation checking
303#
304
weijun0f0fb6a2009-12-24 13:56:19 +0800305# Enable OCSP
duke6e45e102007-12-01 00:00:00 +0000306#
307# By default, OCSP is not used for certificate revocation checking.
308# This property enables the use of OCSP when set to the value "true".
309#
310# NOTE: SocketPermission is required to connect to an OCSP responder.
311#
312# Example,
313# ocsp.enable=true
weijun0f0fb6a2009-12-24 13:56:19 +0800314
duke6e45e102007-12-01 00:00:00 +0000315#
316# Location of the OCSP responder
317#
318# By default, the location of the OCSP responder is determined implicitly
319# from the certificate being validated. This property explicitly specifies
320# the location of the OCSP responder. The property is used when the
321# Authority Information Access extension (defined in RFC 3280) is absent
322# from the certificate or when it requires overriding.
323#
324# Example,
325# ocsp.responderURL=http://ocsp.example.net:80
weijun0f0fb6a2009-12-24 13:56:19 +0800326
duke6e45e102007-12-01 00:00:00 +0000327#
328# Subject name of the OCSP responder's certificate
329#
330# By default, the certificate of the OCSP responder is that of the issuer
331# of the certificate being validated. This property identifies the certificate
weijun0f0fb6a2009-12-24 13:56:19 +0800332# of the OCSP responder when the default does not apply. Its value is a string
333# distinguished name (defined in RFC 2253) which identifies a certificate in
334# the set of certificates supplied during cert path validation. In cases where
duke6e45e102007-12-01 00:00:00 +0000335# the subject name alone is not sufficient to uniquely identify the certificate
336# then both the "ocsp.responderCertIssuerName" and
337# "ocsp.responderCertSerialNumber" properties must be used instead. When this
338# property is set then those two properties are ignored.
339#
340# Example,
341# ocsp.responderCertSubjectName="CN=OCSP Responder, O=XYZ Corp"
342
343#
344# Issuer name of the OCSP responder's certificate
345#
346# By default, the certificate of the OCSP responder is that of the issuer
347# of the certificate being validated. This property identifies the certificate
348# of the OCSP responder when the default does not apply. Its value is a string
349# distinguished name (defined in RFC 2253) which identifies a certificate in
weijun0f0fb6a2009-12-24 13:56:19 +0800350# the set of certificates supplied during cert path validation. When this
351# property is set then the "ocsp.responderCertSerialNumber" property must also
352# be set. When the "ocsp.responderCertSubjectName" property is set then this
duke6e45e102007-12-01 00:00:00 +0000353# property is ignored.
354#
355# Example,
356# ocsp.responderCertIssuerName="CN=Enterprise CA, O=XYZ Corp"
weijun0f0fb6a2009-12-24 13:56:19 +0800357
duke6e45e102007-12-01 00:00:00 +0000358#
359# Serial number of the OCSP responder's certificate
360#
361# By default, the certificate of the OCSP responder is that of the issuer
362# of the certificate being validated. This property identifies the certificate
363# of the OCSP responder when the default does not apply. Its value is a string
364# of hexadecimal digits (colon or space separators may be present) which
365# identifies a certificate in the set of certificates supplied during cert path
366# validation. When this property is set then the "ocsp.responderCertIssuerName"
367# property must also be set. When the "ocsp.responderCertSubjectName" property
368# is set then this property is ignored.
369#
370# Example,
371# ocsp.responderCertSerialNumber=2A:FF:00
weijun0f0fb6a2009-12-24 13:56:19 +0800372
373#
374# Policy for failed Kerberos KDC lookups:
375#
376# When a KDC is unavailable (network error, service failure, etc), it is
377# put inside a blacklist and accessed less often for future requests. The
378# value (case-insensitive) for this policy can be:
379#
380# tryLast
381# KDCs in the blacklist are always tried after those not on the list.
382#
383# tryLess[:max_retries,timeout]
384# KDCs in the blacklist are still tried by their order in the configuration,
385# but with smaller max_retries and timeout values. max_retries and timeout
386# are optional numerical parameters (default 1 and 5000, which means once
387# and 5 seconds). Please notes that if any of the values defined here is
388# more than what is defined in krb5.conf, it will be ignored.
389#
390# Whenever a KDC is detected as available, it is removed from the blacklist.
391# The blacklist is reset when krb5.conf is reloaded. You can add
392# refreshKrb5Config=true to a JAAS configuration file so that krb5.conf is
393# reloaded whenever a JAAS authentication is attempted.
394#
395# Example,
396# krb5.kdc.bad.policy = tryLast
397# krb5.kdc.bad.policy = tryLess:2,2000
398krb5.kdc.bad.policy = tryLast
399
xuelei42dd6452010-11-01 07:57:46 -0700400# Algorithm restrictions for certification path (CertPath) processing
401#
402# In some environments, certain algorithms or key lengths may be undesirable
403# for certification path building and validation. For example, "MD2" is
404# generally no longer considered to be a secure hash algorithm. This section
405# describes the mechanism for disabling algorithms based on algorithm name
406# and/or key length. This includes algorithms used in certificates, as well
407# as revocation information such as CRLs and signed OCSP Responses.
408#
409# The syntax of the disabled algorithm string is described as this Java
410# BNF-style:
411# DisabledAlgorithms:
412# " DisabledAlgorithm { , DisabledAlgorithm } "
413#
414# DisabledAlgorithm:
415# AlgorithmName [Constraint]
416#
417# AlgorithmName:
418# (see below)
419#
420# Constraint:
421# KeySizeConstraint
422#
423# KeySizeConstraint:
424# keySize Operator DecimalInteger
425#
426# Operator:
427# <= | < | == | != | >= | >
428#
429# DecimalInteger:
430# DecimalDigits
431#
432# DecimalDigits:
433# DecimalDigit {DecimalDigit}
434#
435# DecimalDigit: one of
436# 1 2 3 4 5 6 7 8 9 0
437#
438# The "AlgorithmName" is the standard algorithm name of the disabled
439# algorithm. See "Java Cryptography Architecture Standard Algorithm Name
440# Documentation" for information about Standard Algorithm Names. Matching
441# is performed using a case-insensitive sub-element matching rule. (For
442# example, in "SHA1withECDSA" the sub-elements are "SHA1" for hashing and
443# "ECDSA" for signatures.) If the assertion "AlgorithmName" is a
444# sub-element of the certificate algorithm name, the algorithm will be
445# rejected during certification path building and validation. For example,
446# the assertion algorithm name "DSA" will disable all certificate algorithms
447# that rely on DSA, such as NONEwithDSA, SHA1withDSA. However, the assertion
448# will not disable algorithms related to "ECDSA".
449#
450# A "Constraint" provides further guidance for the algorithm being specified.
451# The "KeySizeConstraint" requires a key of a valid size range if the
452# "AlgorithmName" is of a key algorithm. The "DecimalInteger" indicates the
453# key size specified in number of bits. For example, "RSA keySize <= 1024"
454# indicates that any RSA key with key size less than or equal to 1024 bits
455# should be disabled, and "RSA keySize < 1024, RSA keySize > 2048" indicates
456# that any RSA key with key size less than 1024 or greater than 2048 should
457# be disabled. Note that the "KeySizeConstraint" only makes sense to key
458# algorithms.
459#
460# Note: This property is currently used by Oracle's PKIX implementation. It
461# is not guaranteed to be examined and used by other implementations.
462#
463# Example:
464# jdk.certpath.disabledAlgorithms=MD2, DSA, RSA keySize < 2048
465#
466#
xuelei7b2dfe72012-12-28 00:48:12 -0800467jdk.certpath.disabledAlgorithms=MD2, RSA keySize < 1024
xuelei42dd6452010-11-01 07:57:46 -0700468
469# Algorithm restrictions for Secure Socket Layer/Transport Layer Security
470# (SSL/TLS) processing
471#
472# In some environments, certain algorithms or key lengths may be undesirable
473# when using SSL/TLS. This section describes the mechanism for disabling
474# algorithms during SSL/TLS security parameters negotiation, including cipher
475# suites selection, peer authentication and key exchange mechanisms.
476#
477# For PKI-based peer authentication and key exchange mechanisms, this list
478# of disabled algorithms will also be checked during certification path
479# building and validation, including algorithms used in certificates, as
480# well as revocation information such as CRLs and signed OCSP Responses.
481# This is in addition to the jdk.certpath.disabledAlgorithms property above.
482#
483# See the specification of "jdk.certpath.disabledAlgorithms" for the
484# syntax of the disabled algorithm string.
485#
486# Note: This property is currently used by Oracle's JSSE implementation.
487# It is not guaranteed to be examined and used by other implementations.
488#
489# Example:
490# jdk.tls.disabledAlgorithms=MD5, SHA1, DSA, RSA keySize < 2048
491