java.security-windows revision 1545
0N/A#
0N/A# This is the "master security properties file".
0N/A#
0N/A# In this file, various security properties are set for use by
0N/A# java.security classes. This is where users can statically register
0N/A# Cryptography Package Providers ("providers" for short). The term
0N/A# "provider" refers to a package or set of packages that supply a
0N/A# concrete implementation of a subset of the cryptography aspects of
0N/A# the Java Security API. A provider may, for example, implement one or
0N/A# more digital signature algorithms or message digest algorithms.
0N/A#
0N/A# Each provider must implement a subclass of the Provider class.
0N/A# To register a provider in this master security properties file,
0N/A# specify the Provider subclass name and priority in the format
0N/A#
0N/A# security.provider.<n>=<className>
0N/A#
0N/A# This declares a provider, and specifies its preference
0N/A# order n. The preference order is the order in which providers are
0N/A# searched for requested algorithms (when no specific provider is
0N/A# requested). The order is 1-based; 1 is the most preferred, followed
0N/A# by 2, and so on.
0N/A#
0N/A# <className> must specify the subclass of the Provider class whose
0N/A# constructor sets the values of various properties that are required
0N/A# for the Java Security API to look up the algorithms or other
0N/A# facilities implemented by the provider.
0N/A#
0N/A# There must be at least one provider specification in java.security.
0N/A# There is a default provider that comes standard with the JDK. It
0N/A# is called the "SUN" provider, and its Provider subclass
0N/A# named Sun appears in the sun.security.provider package. Thus, the
0N/A# "SUN" provider is registered via the following:
0N/A#
0N/A# security.provider.1=sun.security.provider.Sun
0N/A#
0N/A# (The number 1 is used for the default provider.)
0N/A#
0N/A# Note: Providers can be dynamically registered instead by calls to
0N/A# either the addProvider or insertProviderAt method in the Security
0N/A# class.
0N/A
0N/A#
0N/A# List of providers and their preference orders (see above):
0N/A#
0N/Asecurity.provider.1=sun.security.provider.Sun
0N/Asecurity.provider.2=sun.security.rsa.SunRsaSign
1545N/Asecurity.provider.3=sun.security.ec.SunEC
1545N/Asecurity.provider.4=com.sun.net.ssl.internal.ssl.Provider
1545N/Asecurity.provider.5=com.sun.crypto.provider.SunJCE
1545N/Asecurity.provider.6=sun.security.jgss.SunProvider
1545N/Asecurity.provider.7=com.sun.security.sasl.Provider
1545N/Asecurity.provider.8=org.jcp.xml.dsig.internal.dom.XMLDSigRI
1545N/Asecurity.provider.9=sun.security.smartcardio.SunPCSC
1545N/Asecurity.provider.10=sun.security.mscapi.SunMSCAPI
0N/A
0N/A#
0N/A# Select the source of seed data for SecureRandom. By default an
0N/A# attempt is made to use the entropy gathering device specified by
0N/A# the securerandom.source property. If an exception occurs when
0N/A# accessing the URL then the traditional system/thread activity
0N/A# algorithm is used.
0N/A#
0N/A# On Solaris and Linux systems, if file:/dev/urandom is specified and it
0N/A# exists, a special SecureRandom implementation is activated by default.
0N/A# This "NativePRNG" reads random bytes directly from /dev/urandom.
0N/A#
0N/A# On Windows systems, the URLs file:/dev/random and file:/dev/urandom
0N/A# enables use of the Microsoft CryptoAPI seed functionality.
0N/A#
0N/Asecurerandom.source=file:/dev/urandom
0N/A#
0N/A# The entropy gathering device is described as a URL and can also
0N/A# be specified with the system property "java.security.egd". For example,
0N/A# -Djava.security.egd=file:/dev/urandom
0N/A# Specifying this system property will override the securerandom.source
0N/A# setting.
0N/A
0N/A#
0N/A# Class to instantiate as the javax.security.auth.login.Configuration
0N/A# provider.
0N/A#
0N/Alogin.configuration.provider=com.sun.security.auth.login.ConfigFile
0N/A
0N/A#
0N/A# Default login configuration file
0N/A#
0N/A#login.config.url.1=file:${user.home}/.java.login.config
0N/A
0N/A#
0N/A# Class to instantiate as the system Policy. This is the name of the class
0N/A# that will be used as the Policy object.
0N/A#
0N/Apolicy.provider=sun.security.provider.PolicyFile
0N/A
0N/A# The default is to have a single system-wide policy file,
0N/A# and a policy file in the user's home directory.
0N/Apolicy.url.1=file:${java.home}/lib/security/java.policy
0N/Apolicy.url.2=file:${user.home}/.java.policy
0N/A
0N/A# whether or not we expand properties in the policy file
0N/A# if this is set to false, properties (${...}) will not be expanded in policy
0N/A# files.
0N/Apolicy.expandProperties=true
0N/A
0N/A# whether or not we allow an extra policy to be passed on the command line
0N/A# with -Djava.security.policy=somefile. Comment out this line to disable
0N/A# this feature.
0N/Apolicy.allowSystemProperty=true
0N/A
0N/A# whether or not we look into the IdentityScope for trusted Identities
0N/A# when encountering a 1.1 signed JAR file. If the identity is found
0N/A# and is trusted, we grant it AllPermission.
0N/Apolicy.ignoreIdentityScope=false
0N/A
0N/A#
0N/A# Default keystore type.
0N/A#
0N/Akeystore.type=jks
0N/A
0N/A#
0N/A# Class to instantiate as the system scope:
0N/A#
0N/Asystem.scope=sun.security.provider.IdentityDatabase
0N/A
0N/A#
0N/A# List of comma-separated packages that start with or equal this string
0N/A# will cause a security exception to be thrown when
0N/A# passed to checkPackageAccess unless the
0N/A# corresponding RuntimePermission ("accessClassInPackage."+package) has
0N/A# been granted.
1501N/Apackage.access=sun.,com.sun.imageio.
0N/A
0N/A#
0N/A# List of comma-separated packages that start with or equal this string
0N/A# will cause a security exception to be thrown when
0N/A# passed to checkPackageDefinition unless the
0N/A# corresponding RuntimePermission ("defineClassInPackage."+package) has
0N/A# been granted.
0N/A#
0N/A# by default, no packages are restricted for definition, and none of
0N/A# the class loaders supplied with the JDK call checkPackageDefinition.
0N/A#
0N/A#package.definition=
0N/A
0N/A#
0N/A# Determines whether this properties file can be appended to
0N/A# or overridden on the command line via -Djava.security.properties
0N/A#
0N/Asecurity.overridePropertiesFile=true
0N/A
0N/A#
0N/A# Determines the default key and trust manager factory algorithms for
0N/A# the javax.net.ssl package.
0N/A#
0N/Assl.KeyManagerFactory.algorithm=SunX509
0N/Assl.TrustManagerFactory.algorithm=PKIX
0N/A
0N/A#
0N/A# The Java-level namelookup cache policy for successful lookups:
0N/A#
0N/A# any negative value: caching forever
0N/A# any positive value: the number of seconds to cache an address for
0N/A# zero: do not cache
0N/A#
0N/A# default value is forever (FOREVER). For security reasons, this
0N/A# caching is made forever when a security manager is set. When a security
0N/A# manager is not set, the default behavior is to cache for 30 seconds.
0N/A#
0N/A# NOTE: setting this to anything other than the default value can have
0N/A# serious security implications. Do not set it unless
0N/A# you are sure you are not exposed to DNS spoofing attack.
0N/A#
0N/A#networkaddress.cache.ttl=-1
0N/A
0N/A# The Java-level namelookup cache policy for failed lookups:
0N/A#
0N/A# any negative value: cache forever
0N/A# any positive value: the number of seconds to cache negative lookup results
0N/A# zero: do not cache
0N/A#
0N/A# In some Microsoft Windows networking environments that employ
0N/A# the WINS name service in addition to DNS, name service lookups
0N/A# that fail may take a noticeably long time to return (approx. 5 seconds).
0N/A# For this reason the default caching policy is to maintain these
0N/A# results for 10 seconds.
0N/A#
0N/A#
0N/Anetworkaddress.cache.negative.ttl=10
0N/A
0N/A#
0N/A# Properties to configure OCSP for certificate revocation checking
0N/A#
0N/A
0N/A# Enable OCSP
0N/A#
0N/A# By default, OCSP is not used for certificate revocation checking.
0N/A# This property enables the use of OCSP when set to the value "true".
0N/A#
0N/A# NOTE: SocketPermission is required to connect to an OCSP responder.
0N/A#
0N/A# Example,
0N/A# ocsp.enable=true
0N/A
0N/A#
0N/A# Location of the OCSP responder
0N/A#
0N/A# By default, the location of the OCSP responder is determined implicitly
0N/A# from the certificate being validated. This property explicitly specifies
0N/A# the location of the OCSP responder. The property is used when the
0N/A# Authority Information Access extension (defined in RFC 3280) is absent
0N/A# from the certificate or when it requires overriding.
0N/A#
0N/A# Example,
0N/A# ocsp.responderURL=http://ocsp.example.net:80
0N/A
0N/A#
0N/A# Subject name of the OCSP responder's certificate
0N/A#
0N/A# By default, the certificate of the OCSP responder is that of the issuer
0N/A# of the certificate being validated. This property identifies the certificate
0N/A# of the OCSP responder when the default does not apply. Its value is a string
0N/A# distinguished name (defined in RFC 2253) which identifies a certificate in
0N/A# the set of certificates supplied during cert path validation. In cases where
0N/A# the subject name alone is not sufficient to uniquely identify the certificate
0N/A# then both the "ocsp.responderCertIssuerName" and
0N/A# "ocsp.responderCertSerialNumber" properties must be used instead. When this
0N/A# property is set then those two properties are ignored.
0N/A#
0N/A# Example,
0N/A# ocsp.responderCertSubjectName="CN=OCSP Responder, O=XYZ Corp"
0N/A
0N/A#
0N/A# Issuer name of the OCSP responder's certificate
0N/A#
0N/A# By default, the certificate of the OCSP responder is that of the issuer
0N/A# of the certificate being validated. This property identifies the certificate
0N/A# of the OCSP responder when the default does not apply. Its value is a string
0N/A# distinguished name (defined in RFC 2253) which identifies a certificate in
0N/A# the set of certificates supplied during cert path validation. When this
0N/A# property is set then the "ocsp.responderCertSerialNumber" property must also
0N/A# be set. When the "ocsp.responderCertSubjectName" property is set then this
0N/A# property is ignored.
0N/A#
0N/A# Example,
0N/A# ocsp.responderCertIssuerName="CN=Enterprise CA, O=XYZ Corp"
0N/A
0N/A#
0N/A# Serial number of the OCSP responder's certificate
0N/A#
0N/A# By default, the certificate of the OCSP responder is that of the issuer
0N/A# of the certificate being validated. This property identifies the certificate
0N/A# of the OCSP responder when the default does not apply. Its value is a string
0N/A# of hexadecimal digits (colon or space separators may be present) which
0N/A# identifies a certificate in the set of certificates supplied during cert path
0N/A# validation. When this property is set then the "ocsp.responderCertIssuerName"
0N/A# property must also be set. When the "ocsp.responderCertSubjectName" property
0N/A# is set then this property is ignored.
0N/A#
0N/A# Example,
0N/A# ocsp.responderCertSerialNumber=2A:FF:00
0N/A