source: arduino-1-6-7/trunk/fuentes/arduino-ide-amd64/java/lib/security/java.security @ 4837

Last change on this file since 4837 was 4837, checked in by daduve, 2 years ago

Adding new version

File size: 26.7 KB
Line 
1#
2# This is the "master security properties file".
3#
4# 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
26# 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
70security.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
77
78#
79# Sun Provider SecureRandom seed source.
80#
81# 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.)
84#
85# 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.
88#
89# 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.
92#
93# 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
130
131#
132# Class to instantiate as the javax.security.auth.login.Configuration
133# provider.
134#
135login.configuration.provider=sun.security.provider.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#
174# Controls compatibility mode for the JKS keystore type.
175#
176# When set to 'true', the JKS keystore type supports loading
177# keystore files in either JKS or PKCS12 format. When set to 'false'
178# it supports loading only JKS keystore files.
179#
180keystore.type.compat=true
181
182#
183# List of comma-separated packages that start with or equal this string
184# will cause a security exception to be thrown when
185# passed to checkPackageAccess unless the
186# corresponding RuntimePermission ("accessClassInPackage."+package) has
187# been granted.
188package.access=sun.,\
189               com.sun.xml.internal.,\
190               com.sun.imageio.,\
191               com.sun.istack.internal.,\
192               com.sun.jmx.,\
193               com.sun.media.sound.,\
194               com.sun.naming.internal.,\
195               com.sun.proxy.,\
196               com.sun.corba.se.,\
197               com.sun.org.apache.bcel.internal.,\
198               com.sun.org.apache.regexp.internal.,\
199               com.sun.org.apache.xerces.internal.,\
200               com.sun.org.apache.xpath.internal.,\
201               com.sun.org.apache.xalan.internal.extensions.,\
202               com.sun.org.apache.xalan.internal.lib.,\
203               com.sun.org.apache.xalan.internal.res.,\
204               com.sun.org.apache.xalan.internal.templates.,\
205               com.sun.org.apache.xalan.internal.utils.,\
206               com.sun.org.apache.xalan.internal.xslt.,\
207               com.sun.org.apache.xalan.internal.xsltc.cmdline.,\
208               com.sun.org.apache.xalan.internal.xsltc.compiler.,\
209               com.sun.org.apache.xalan.internal.xsltc.trax.,\
210               com.sun.org.apache.xalan.internal.xsltc.util.,\
211               com.sun.org.apache.xml.internal.res.,\
212               com.sun.org.apache.xml.internal.security.,\
213               com.sun.org.apache.xml.internal.serializer.utils.,\
214               com.sun.org.apache.xml.internal.utils.,\
215               com.sun.org.glassfish.,\
216               com.oracle.xmlns.internal.,\
217               com.oracle.webservices.internal.,\
218               oracle.jrockit.jfr.,\
219               org.jcp.xml.dsig.internal.,\
220               jdk.internal.,\
221               jdk.nashorn.internal.,\
222               jdk.nashorn.tools.,\
223               com.sun.activation.registries.,\
224               com.sun.browser.,\
225               com.sun.glass.,\
226               com.sun.javafx.,\
227               com.sun.media.,\
228               com.sun.openpisces.,\
229               com.sun.prism.,\
230               com.sun.scenario.,\
231               com.sun.t2k.,\
232               com.sun.pisces.,\
233               com.sun.webkit.,\
234               jdk.management.resource.internal.
235
236#
237# List of comma-separated packages that start with or equal this string
238# will cause a security exception to be thrown when
239# passed to checkPackageDefinition unless the
240# corresponding RuntimePermission ("defineClassInPackage."+package) has
241# been granted.
242#
243# by default, none of the class loaders supplied with the JDK call
244# checkPackageDefinition.
245#
246package.definition=sun.,\
247                   com.sun.xml.internal.,\
248                   com.sun.imageio.,\
249                   com.sun.istack.internal.,\
250                   com.sun.jmx.,\
251                   com.sun.media.sound.,\
252                   com.sun.naming.internal.,\
253                   com.sun.proxy.,\
254                   com.sun.corba.se.,\
255                   com.sun.org.apache.bcel.internal.,\
256                   com.sun.org.apache.regexp.internal.,\
257                   com.sun.org.apache.xerces.internal.,\
258                   com.sun.org.apache.xpath.internal.,\
259                   com.sun.org.apache.xalan.internal.extensions.,\
260                   com.sun.org.apache.xalan.internal.lib.,\
261                   com.sun.org.apache.xalan.internal.res.,\
262                   com.sun.org.apache.xalan.internal.templates.,\
263                   com.sun.org.apache.xalan.internal.utils.,\
264                   com.sun.org.apache.xalan.internal.xslt.,\
265                   com.sun.org.apache.xalan.internal.xsltc.cmdline.,\
266                   com.sun.org.apache.xalan.internal.xsltc.compiler.,\
267                   com.sun.org.apache.xalan.internal.xsltc.trax.,\
268                   com.sun.org.apache.xalan.internal.xsltc.util.,\
269                   com.sun.org.apache.xml.internal.res.,\
270                   com.sun.org.apache.xml.internal.security.,\
271                   com.sun.org.apache.xml.internal.serializer.utils.,\
272                   com.sun.org.apache.xml.internal.utils.,\
273                   com.sun.org.glassfish.,\
274                   com.oracle.xmlns.internal.,\
275                   com.oracle.webservices.internal.,\
276                   oracle.jrockit.jfr.,\
277                   org.jcp.xml.dsig.internal.,\
278                   jdk.internal.,\
279                   jdk.nashorn.internal.,\
280                   jdk.nashorn.tools.,\
281                   com.sun.activation.registries.,\
282                   com.sun.browser.,\
283                   com.sun.glass.,\
284                   com.sun.javafx.,\
285                   com.sun.media.,\
286                   com.sun.openpisces.,\
287                   com.sun.prism.,\
288                   com.sun.scenario.,\
289                   com.sun.t2k.,\
290                   com.sun.pisces.,\
291                   com.sun.webkit.,\
292                   jdk.management.resource.internal.
293
294#
295# Determines whether this properties file can be appended to
296# or overridden on the command line via -Djava.security.properties
297#
298security.overridePropertiesFile=true
299
300#
301# Determines the default key and trust manager factory algorithms for
302# the javax.net.ssl package.
303#
304ssl.KeyManagerFactory.algorithm=SunX509
305ssl.TrustManagerFactory.algorithm=PKIX
306
307#
308# The Java-level namelookup cache policy for successful lookups:
309#
310# any negative value: caching forever
311# any positive value: the number of seconds to cache an address for
312# zero: do not cache
313#
314# default value is forever (FOREVER). For security reasons, this
315# caching is made forever when a security manager is set. When a security
316# manager is not set, the default behavior in this implementation
317# is to cache for 30 seconds.
318#
319# NOTE: setting this to anything other than the default value can have
320#       serious security implications. Do not set it unless
321#       you are sure you are not exposed to DNS spoofing attack.
322#
323#networkaddress.cache.ttl=-1
324
325# The Java-level namelookup cache policy for failed lookups:
326#
327# any negative value: cache forever
328# any positive value: the number of seconds to cache negative lookup results
329# zero: do not cache
330#
331# In some Microsoft Windows networking environments that employ
332# the WINS name service in addition to DNS, name service lookups
333# that fail may take a noticeably long time to return (approx. 5 seconds).
334# For this reason the default caching policy is to maintain these
335# results for 10 seconds.
336#
337#
338networkaddress.cache.negative.ttl=10
339
340#
341# Properties to configure OCSP for certificate revocation checking
342#
343
344# Enable OCSP
345#
346# By default, OCSP is not used for certificate revocation checking.
347# This property enables the use of OCSP when set to the value "true".
348#
349# NOTE: SocketPermission is required to connect to an OCSP responder.
350#
351# Example,
352#   ocsp.enable=true
353
354#
355# Location of the OCSP responder
356#
357# By default, the location of the OCSP responder is determined implicitly
358# from the certificate being validated. This property explicitly specifies
359# the location of the OCSP responder. The property is used when the
360# Authority Information Access extension (defined in RFC 3280) is absent
361# from the certificate or when it requires overriding.
362#
363# Example,
364#   ocsp.responderURL=http://ocsp.example.net:80
365
366#
367# Subject name of the OCSP responder's certificate
368#
369# By default, the certificate of the OCSP responder is that of the issuer
370# of the certificate being validated. This property identifies the certificate
371# of the OCSP responder when the default does not apply. Its value is a string
372# distinguished name (defined in RFC 2253) which identifies a certificate in
373# the set of certificates supplied during cert path validation. In cases where
374# the subject name alone is not sufficient to uniquely identify the certificate
375# then both the "ocsp.responderCertIssuerName" and
376# "ocsp.responderCertSerialNumber" properties must be used instead. When this
377# property is set then those two properties are ignored.
378#
379# Example,
380#   ocsp.responderCertSubjectName="CN=OCSP Responder, O=XYZ Corp"
381
382#
383# Issuer name of the OCSP responder's certificate
384#
385# By default, the certificate of the OCSP responder is that of the issuer
386# of the certificate being validated. This property identifies the certificate
387# of the OCSP responder when the default does not apply. Its value is a string
388# distinguished name (defined in RFC 2253) which identifies a certificate in
389# the set of certificates supplied during cert path validation. When this
390# property is set then the "ocsp.responderCertSerialNumber" property must also
391# be set. When the "ocsp.responderCertSubjectName" property is set then this
392# property is ignored.
393#
394# Example,
395#   ocsp.responderCertIssuerName="CN=Enterprise CA, O=XYZ Corp"
396
397#
398# Serial number of the OCSP responder's certificate
399#
400# By default, the certificate of the OCSP responder is that of the issuer
401# of the certificate being validated. This property identifies the certificate
402# of the OCSP responder when the default does not apply. Its value is a string
403# of hexadecimal digits (colon or space separators may be present) which
404# identifies a certificate in the set of certificates supplied during cert path
405# validation. When this property is set then the "ocsp.responderCertIssuerName"
406# property must also be set. When the "ocsp.responderCertSubjectName" property
407# is set then this property is ignored.
408#
409# Example,
410#   ocsp.responderCertSerialNumber=2A:FF:00
411
412#
413# Policy for failed Kerberos KDC lookups:
414#
415# When a KDC is unavailable (network error, service failure, etc), it is
416# put inside a blacklist and accessed less often for future requests. The
417# value (case-insensitive) for this policy can be:
418#
419# tryLast
420#    KDCs in the blacklist are always tried after those not on the list.
421#
422# tryLess[:max_retries,timeout]
423#    KDCs in the blacklist are still tried by their order in the configuration,
424#    but with smaller max_retries and timeout values. max_retries and timeout
425#    are optional numerical parameters (default 1 and 5000, which means once
426#    and 5 seconds). Please notes that if any of the values defined here is
427#    more than what is defined in krb5.conf, it will be ignored.
428#
429# Whenever a KDC is detected as available, it is removed from the blacklist.
430# The blacklist is reset when krb5.conf is reloaded. You can add
431# refreshKrb5Config=true to a JAAS configuration file so that krb5.conf is
432# reloaded whenever a JAAS authentication is attempted.
433#
434# Example,
435#   krb5.kdc.bad.policy = tryLast
436#   krb5.kdc.bad.policy = tryLess:2,2000
437krb5.kdc.bad.policy = tryLast
438
439# Algorithm restrictions for certification path (CertPath) processing
440#
441# In some environments, certain algorithms or key lengths may be undesirable
442# for certification path building and validation.  For example, "MD2" is
443# generally no longer considered to be a secure hash algorithm.  This section
444# describes the mechanism for disabling algorithms based on algorithm name
445# and/or key length.  This includes algorithms used in certificates, as well
446# as revocation information such as CRLs and signed OCSP Responses.
447#
448# The syntax of the disabled algorithm string is described as this Java
449# BNF-style:
450#   DisabledAlgorithms:
451#       " DisabledAlgorithm { , DisabledAlgorithm } "
452#
453#   DisabledAlgorithm:
454#       AlgorithmName [Constraint]
455#
456#   AlgorithmName:
457#       (see below)
458#
459#   Constraint:
460#       KeySizeConstraint
461#
462#   KeySizeConstraint:
463#       keySize Operator DecimalInteger
464#
465#   Operator:
466#       <= | < | == | != | >= | >
467#
468#   DecimalInteger:
469#       DecimalDigits
470#
471#   DecimalDigits:
472#       DecimalDigit {DecimalDigit}
473#
474#   DecimalDigit: one of
475#       1 2 3 4 5 6 7 8 9 0
476#
477# The "AlgorithmName" is the standard algorithm name of the disabled
478# algorithm. See "Java Cryptography Architecture Standard Algorithm Name
479# Documentation" for information about Standard Algorithm Names.  Matching
480# is performed using a case-insensitive sub-element matching rule.  (For
481# example, in "SHA1withECDSA" the sub-elements are "SHA1" for hashing and
482# "ECDSA" for signatures.)  If the assertion "AlgorithmName" is a
483# sub-element of the certificate algorithm name, the algorithm will be
484# rejected during certification path building and validation.  For example,
485# the assertion algorithm name "DSA" will disable all certificate algorithms
486# that rely on DSA, such as NONEwithDSA, SHA1withDSA.  However, the assertion
487# will not disable algorithms related to "ECDSA".
488#
489# A "Constraint" provides further guidance for the algorithm being specified.
490# The "KeySizeConstraint" requires a key of a valid size range if the
491# "AlgorithmName" is of a key algorithm.  The "DecimalInteger" indicates the
492# key size specified in number of bits.  For example, "RSA keySize <= 1024"
493# indicates that any RSA key with key size less than or equal to 1024 bits
494# should be disabled, and "RSA keySize < 1024, RSA keySize > 2048" indicates
495# that any RSA key with key size less than 1024 or greater than 2048 should
496# be disabled. Note that the "KeySizeConstraint" only makes sense to key
497# algorithms.
498#
499# Note: This property is currently used by Oracle's PKIX implementation. It
500# is not guaranteed to be examined and used by other implementations.
501#
502# Example:
503#   jdk.certpath.disabledAlgorithms=MD2, DSA, RSA keySize < 2048
504#
505#
506jdk.certpath.disabledAlgorithms=MD2, MD5, RSA keySize < 1024
507
508# Algorithm restrictions for Secure Socket Layer/Transport Layer Security
509# (SSL/TLS) processing
510#
511# In some environments, certain algorithms or key lengths may be undesirable
512# when using SSL/TLS.  This section describes the mechanism for disabling
513# algorithms during SSL/TLS security parameters negotiation, including
514# protocol version negotiation, cipher suites selection, peer authentication
515# and key exchange mechanisms.
516#
517# Disabled algorithms will not be negotiated for SSL/TLS connections, even
518# if they are enabled explicitly in an application.
519#
520# For PKI-based peer authentication and key exchange mechanisms, this list
521# of disabled algorithms will also be checked during certification path
522# building and validation, including algorithms used in certificates, as
523# well as revocation information such as CRLs and signed OCSP Responses.
524# This is in addition to the jdk.certpath.disabledAlgorithms property above.
525#
526# See the specification of "jdk.certpath.disabledAlgorithms" for the
527# syntax of the disabled algorithm string.
528#
529# Note: This property is currently used by Oracle's JSSE implementation.
530# It is not guaranteed to be examined and used by other implementations.
531#
532# Example:
533#   jdk.tls.disabledAlgorithms=MD5, SSLv3, DSA, RSA keySize < 2048
534jdk.tls.disabledAlgorithms=SSLv3, RC4, MD5withRSA, DH keySize < 768
535
536# Legacy algorithms for Secure Socket Layer/Transport Layer Security (SSL/TLS)
537# processing in JSSE implementation.
538#
539# In some environments, a certain algorithm may be undesirable but it
540# cannot be disabled because of its use in legacy applications.  Legacy
541# algorithms may still be supported, but applications should not use them
542# as the security strength of legacy algorithms are usually not strong enough
543# in practice.
544#
545# During SSL/TLS security parameters negotiation, legacy algorithms will
546# not be negotiated unless there are no other candidates.
547#
548# The syntax of the disabled algorithm string is described as this Java
549# BNF-style:
550#   LegacyAlgorithms:
551#       " LegacyAlgorithm { , LegacyAlgorithm } "
552#
553#   LegacyAlgorithm:
554#       AlgorithmName (standard JSSE algorithm name)
555#
556# See the specification of security property "jdk.certpath.disabledAlgorithms"
557# for the syntax and description of the "AlgorithmName" notation.
558#
559# Per SSL/TLS specifications, cipher suites have the form:
560#       SSL_KeyExchangeAlg_WITH_CipherAlg_MacAlg
561# or
562#       TLS_KeyExchangeAlg_WITH_CipherAlg_MacAlg
563#
564# For example, the cipher suite TLS_RSA_WITH_AES_128_CBC_SHA uses RSA as the
565# key exchange algorithm, AES_128_CBC (128 bits AES cipher algorithm in CBC
566# mode) as the cipher (encryption) algorithm, and SHA-1 as the message digest
567# algorithm for HMAC.
568#
569# The LegacyAlgorithm can be one of the following standard algorithm names:
570#     1. JSSE cipher suite name, e.g., TLS_RSA_WITH_AES_128_CBC_SHA
571#     2. JSSE key exchange algorithm name, e.g., RSA
572#     3. JSSE cipher (encryption) algorithm name, e.g., AES_128_CBC
573#     4. JSSE message digest algorithm name, e.g., SHA
574#
575# See SSL/TLS specifications and "Java Cryptography Architecture Standard
576# Algorithm Name Documentation" for information about the algorithm names.
577#
578# Note: This property is currently used by Oracle's JSSE implementation.
579# It is not guaranteed to be examined and used by other implementations.
580# There is no guarantee the property will continue to exist or be of the
581# same syntax in future releases.
582#
583# Example:
584#   jdk.tls.legacyAlgorithms=DH_anon, DES_CBC, SSL_RSA_WITH_RC4_128_MD5
585#
586jdk.tls.legacyAlgorithms= \
587        K_NULL, C_NULL, M_NULL, \
588        DHE_DSS_EXPORT, DHE_RSA_EXPORT, DH_anon_EXPORT, DH_DSS_EXPORT, \
589        DH_RSA_EXPORT, RSA_EXPORT, \
590        DH_anon, ECDH_anon, \
591        RC4_128, RC4_40, DES_CBC, DES40_CBC
592
593# The pre-defined default finite field Diffie-Hellman ephemeral (DHE)
594# parameters for Transport Layer Security (SSL/TLS/DTLS) processing.
595#
596# In traditional SSL/TLS/DTLS connections where finite field DHE parameters
597# negotiation mechanism is not used, the server offers the client group
598# parameters, base generator g and prime modulus p, for DHE key exchange.
599# It is recommended to use dynamic group parameters.  This property defines
600# a mechanism that allows you to specify custom group parameters.
601#
602# The syntax of this property string is described as this Java BNF-style:
603#   DefaultDHEParameters:
604#       DefinedDHEParameters { , DefinedDHEParameters }
605#
606#   DefinedDHEParameters:
607#       "{" DHEPrimeModulus , DHEBaseGenerator "}"
608#
609#   DHEPrimeModulus:
610#       HexadecimalDigits
611#
612#   DHEBaseGenerator:
613#       HexadecimalDigits
614#
615#   HexadecimalDigits:
616#       HexadecimalDigit { HexadecimalDigit }
617#
618#   HexadecimalDigit: one of
619#       0 1 2 3 4 5 6 7 8 9 A B C D E F a b c d e f
620#
621# Whitespace characters are ignored.
622#
623# The "DefinedDHEParameters" defines the custom group parameters, prime
624# modulus p and base generator g, for a particular size of prime modulus p.
625# The "DHEPrimeModulus" defines the hexadecimal prime modulus p, and the
626# "DHEBaseGenerator" defines the hexadecimal base generator g of a group
627# parameter.  It is recommended to use safe primes for the custom group
628# parameters.
629#
630# If this property is not defined or the value is empty, the underlying JSSE
631# provider's default group parameter is used for each connection.
632#
633# If the property value does not follow the grammar, or a particular group
634# parameter is not valid, the connection will fall back and use the
635# underlying JSSE provider's default group parameter.
636#
637# Note: This property is currently used by OpenJDK's JSSE implementation. It
638# is not guaranteed to be examined and used by other implementations.
639#
640# Example:
641#   jdk.tls.server.defaultDHEParameters=
642#       { \
643#       FFFFFFFF FFFFFFFF C90FDAA2 2168C234 C4C6628B 80DC1CD1 \
644#       29024E08 8A67CC74 020BBEA6 3B139B22 514A0879 8E3404DD \
645#       EF9519B3 CD3A431B 302B0A6D F25F1437 4FE1356D 6D51C245 \
646#       E485B576 625E7EC6 F44C42E9 A637ED6B 0BFF5CB6 F406B7ED \
647#       EE386BFB 5A899FA5 AE9F2411 7C4B1FE6 49286651 ECE65381 \
648#       FFFFFFFF FFFFFFFF, 2}
649
650# Algorithm restrictions for signed JAR files
651#
652# In some environments, certain algorithms or key lengths may be undesirable
653# for signed JAR validation.  For example, "MD2" is generally no longer
654# considered to be a secure hash algorithm.  This section describes the
655# mechanism for disabling algorithms based on algorithm name and/or key length.
656# JARs signed with any of the disabled algorithms or key sizes will be treated
657# as unsigned.
658#
659# The syntax of the disabled algorithm string is described as follows:
660#   DisabledAlgorithms:
661#       " DisabledAlgorithm { , DisabledAlgorithm } "
662#
663#   DisabledAlgorithm:
664#       AlgorithmName [Constraint]
665#
666#   AlgorithmName:
667#       (see below)
668#
669#   Constraint:
670#       KeySizeConstraint
671#
672#   KeySizeConstraint:
673#       keySize Operator KeyLength
674#
675#   Operator:
676#       <= | < | == | != | >= | >
677#
678#   KeyLength:
679#       Integer value of the algorithm's key length in bits
680#
681# Note: This property is currently used by the JDK Reference
682# implementation. It is not guaranteed to be examined and used by other
683# implementations.
684#
685jdk.jar.disabledAlgorithms=MD2, RSA keySize < 1024
Note: See TracBrowser for help on using the repository browser.