1121N/A# This is the "master security properties file".
1121N/A# In this file, various security properties are set for use by
1121N/A# Cryptography Package Providers ("providers" for short). The term
1121N/A# "provider" refers to a package or set of packages that supply a
1121N/A# concrete implementation of a subset of the cryptography aspects of
1121N/A# the Java Security API. A provider may, for example, implement one or
1121N/A# more digital signature algorithms or message digest algorithms.
1121N/A# Each provider must implement a subclass of the Provider class.
1121N/A# To register a provider in this master security properties file,
1121N/A# specify the Provider subclass name and priority in the format
2362N/A# This declares a provider, and specifies its preference
2362N/A# order n. The preference order is the order in which providers are
2362N/A# searched for requested algorithms (when no specific provider is
1121N/A# requested). The order is 1-based; 1 is the most preferred, followed
1121N/A# <className> must specify the subclass of the Provider class whose
1121N/A# constructor sets the values of various properties that are required
1121N/A# for the Java Security API to look up the algorithms or other
1121N/A# facilities implemented by the provider.
1121N/A# There is a default provider that comes standard with the JDK. It
1121N/A# is called the "SUN" provider, and its Provider subclass
1121N/A# "SUN" provider is registered via the following:
1121N/A# (The number 1 is used for the default provider.)
1121N/A# Note: Providers can be dynamically registered instead by calls to
1121N/A# either the addProvider or insertProviderAt method in the Security
1121N/A# List of providers and their preference orders (see above):
1121N/A# Select the source of seed data for SecureRandom. By default an
1121N/A# attempt is made to use the entropy gathering device specified by
1121N/A# exists, a special SecureRandom implementation is activated by default.
# enables use of the Microsoft CryptoAPI seed functionality.
# The entropy gathering device is described as a URL and can also
# Default login configuration file
# Class to instantiate as the system Policy. This is the name of the class
# that will be used as the Policy object.
# The default is to have a single system-wide policy file,
# and a policy file in the user's home directory.
# whether or not we expand properties in the policy file
# if this is set to false, properties (${...}) will not be expanded in policy
# whether or not we allow an extra policy to be passed on the command line
# whether or not we look into the IdentityScope for trusted Identities
# when encountering a 1.1 signed JAR file. If the identity is found
# and is trusted, we grant it AllPermission.
# List of comma-separated packages that start with or equal this string
# will cause a security exception to be thrown when
# passed to checkPackageAccess unless the
# corresponding RuntimePermission ("accessClassInPackage."+package) has
# List of comma-separated packages that start with or equal this string
# will cause a security exception to be thrown when
# passed to checkPackageDefinition unless the
# corresponding RuntimePermission ("defineClassInPackage."+package) has
# by default, none of the class loaders supplied with the JDK call
# checkPackageDefinition.
# Determines whether this properties file can be appended to
# Determines the default key and trust manager factory algorithms for
# The Java-level namelookup cache policy for successful lookups:
# any negative value: caching forever
# any positive value: the number of seconds to cache an address for
# default value is forever (FOREVER). For security reasons, this
# caching is made forever when a security manager is set. When a security
# manager is not set, the default behavior in this implementation
# is to cache for 30 seconds.
# NOTE: setting this to anything other than the default value can have
# serious security implications. Do not set it unless
# you are sure you are not exposed to DNS spoofing attack.
# The Java-level namelookup cache policy for failed lookups:
# any negative value: cache forever
# any positive value: the number of seconds to cache negative lookup results
# In some Microsoft Windows networking environments that employ
# the WINS name service in addition to DNS, name service lookups
# that fail may take a noticeably long time to return (approx. 5 seconds).
# For this reason the default caching policy is to maintain these
# results for 10 seconds.
# Properties to configure OCSP for certificate revocation checking
# By default, OCSP is not used for certificate revocation checking.
# This property enables the use of OCSP when set to the value "true".
# NOTE: SocketPermission is required to connect to an OCSP responder.
# Location of the OCSP responder
# By default, the location of the OCSP responder is determined implicitly
# from the certificate being validated. This property explicitly specifies
# the location of the OCSP responder. The property is used when the
# Authority Information Access extension (defined in RFC 3280) is absent
# from the certificate or when it requires overriding.
# Subject name of the OCSP responder's certificate
# By default, the certificate of the OCSP responder is that of the issuer
# of the certificate being validated. This property identifies the certificate
# of the OCSP responder when the default does not apply. Its value is a string
# distinguished name (defined in RFC 2253) which identifies a certificate in
# the set of certificates supplied during cert path validation. In cases where
# the subject name alone is not sufficient to uniquely identify the certificate
# property is set then those two properties are ignored.
# Issuer name of the OCSP responder's certificate
# By default, the certificate of the OCSP responder is that of the issuer
# of the certificate being validated. This property identifies the certificate
# of the OCSP responder when the default does not apply. Its value is a string
# distinguished name (defined in RFC 2253) which identifies a certificate in
# the set of certificates supplied during cert path validation. When this
# Serial number of the OCSP responder's certificate
# By default, the certificate of the OCSP responder is that of the issuer
# of the certificate being validated. This property identifies the certificate
# of the OCSP responder when the default does not apply. Its value is a string
# of hexadecimal digits (colon or space separators may be present) which
# identifies a certificate in the set of certificates supplied during cert path
# is set then this property is ignored.
# Policy for failed Kerberos KDC lookups:
# When a KDC is unavailable (network error, service failure, etc), it is
# put inside a blacklist and accessed less often for future requests. The
# value (case-insensitive) for this policy can be:
# KDCs in the blacklist are always tried after those not on the list.
# tryLess[:max_retries,timeout]
# KDCs in the blacklist are still tried by their order in the configuration,
# but with smaller max_retries and timeout values. max_retries and timeout
# are optional numerical parameters (default 1 and 5000, which means once
# and 5 seconds). Please notes that if any of the values defined here is
# more than what is defined in
krb5.conf, it will be ignored.
# Whenever a KDC is detected as available, it is removed from the blacklist.
# The blacklist is reset when
krb5.conf is reloaded. You can add
# refreshKrb5Config=true to a JAAS configuration file so that
krb5.conf is
# reloaded whenever a JAAS authentication is attempted.
# Algorithm restrictions for certification path (CertPath) processing
# In some environments, certain algorithms or key lengths may be undesirable
# for certification path building and validation. For example, "MD2" is
# generally no longer considered to be a secure hash algorithm. This section
# describes the mechanism for disabling algorithms based on algorithm name
#
and/or key length. This includes algorithms used in certificates, as well
# as revocation information such as CRLs and signed OCSP Responses.
# The syntax of the disabled algorithm string is described as this Java
# " DisabledAlgorithm { , DisabledAlgorithm } "
# AlgorithmName [Constraint]
# keySize Operator DecimalInteger
# <= | < | == | != | >= | >
# DecimalDigit {DecimalDigit}
# The "AlgorithmName" is the standard algorithm name of the disabled
# algorithm. See "Java Cryptography Architecture Standard Algorithm Name
# Documentation" for information about Standard Algorithm Names. Matching
# is performed using a case-insensitive sub-element matching rule. (For
# example, in "SHA1withECDSA" the sub-elements are "SHA1" for hashing and
# "ECDSA" for signatures.) If the assertion "AlgorithmName" is a
# sub-element of the certificate algorithm name, the algorithm will be
# rejected during certification path building and validation. For example,
# the assertion algorithm name "DSA" will disable all certificate algorithms
# that rely on DSA, such as NONEwithDSA, SHA1withDSA. However, the assertion
# will not disable algorithms related to "ECDSA".
# A "Constraint" provides further guidance for the algorithm being specified.
# The "KeySizeConstraint" requires a key of a valid size range if the
# "AlgorithmName" is of a key algorithm. The "DecimalInteger" indicates the
# key size specified in number of bits. For example, "RSA keySize <= 1024"
# indicates that any RSA key with key size less than or equal to 1024 bits
# should be disabled, and "RSA keySize < 1024, RSA keySize > 2048" indicates
# that any RSA key with key size less than 1024 or greater than 2048 should
# be disabled. Note that the "KeySizeConstraint" only makes sense to key
# Note: This property is currently used by Oracle's PKIX implementation. It
# is not guaranteed to be examined and used by other implementations.
# In some environments, certain algorithms or key lengths may be undesirable
# when using
SSL/TLS. This section describes the mechanism for disabling
# algorithms during
SSL/TLS security parameters negotiation, including cipher
# suites selection, peer authentication and key exchange mechanisms.
# For PKI-based peer authentication and key exchange mechanisms, this list
# of disabled algorithms will also be checked during certification path
# building and validation, including algorithms used in certificates, as
# well as revocation information such as CRLs and signed OCSP Responses.
# syntax of the disabled algorithm string.
# Note: This property is currently used by Oracle's JSSE implementation.
# It is not guaranteed to be examined and used by other implementations.