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