Statistics
| Revision:

root / tmp / org.txm.setups / shared / win / jre / lib / security / java.security @ 2748

History | View | Annotate | Download (41.6 kB)

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
#
68
security.provider.1=sun.security.provider.Sun
69
security.provider.2=sun.security.rsa.SunRsaSign
70
security.provider.3=sun.security.ec.SunEC
71
security.provider.4=com.sun.net.ssl.internal.ssl.Provider
72
security.provider.5=com.sun.crypto.provider.SunJCE
73
security.provider.6=sun.security.jgss.SunProvider
74
security.provider.7=com.sun.security.sasl.Provider
75
security.provider.8=org.jcp.xml.dsig.internal.dom.XMLDSigRI
76
security.provider.9=sun.security.smartcardio.SunPCSC
77
security.provider.10=sun.security.mscapi.SunMSCAPI
78

    
79
#
80
# Sun Provider SecureRandom seed source.
81
#
82
# Select the primary source of seed data for the "SHA1PRNG" and
83
# "NativePRNG" SecureRandom implementations in the "Sun" provider.
84
# (Other SecureRandom implementations might also use this property.)
85
#
86
# On Unix-like systems (for example, Solaris/Linux/MacOS), the
87
# "NativePRNG" and "SHA1PRNG" implementations obtains seed data from
88
# special device files such as file:/dev/random.
89
#
90
# On Windows systems, specifying the URLs "file:/dev/random" or
91
# "file:/dev/urandom" will enable the native Microsoft CryptoAPI seeding
92
# mechanism for SHA1PRNG.
93
#
94
# By default, an attempt is made to use the entropy gathering device
95
# specified by the "securerandom.source" Security property.  If an
96
# exception occurs while accessing the specified URL:
97
#
98
#     SHA1PRNG:
99
#         the traditional system/thread activity algorithm will be used.
100
#
101
#     NativePRNG:
102
#         a default value of /dev/random will be used.  If neither
103
#         are available, the implementation will be disabled.
104
#         "file" is the only currently supported protocol type.
105
#
106
# The entropy gathering device can also be specified with the System
107
# property "java.security.egd". For example:
108
#
109
#   % java -Djava.security.egd=file:/dev/random MainClass
110
#
111
# Specifying this System property will override the
112
# "securerandom.source" Security property.
113
#
114
# In addition, if "file:/dev/random" or "file:/dev/urandom" is
115
# specified, the "NativePRNG" implementation will be more preferred than
116
# SHA1PRNG in the Sun provider.
117
#
118
securerandom.source=file:/dev/random
119

    
120
#
121
# A list of known strong SecureRandom implementations.
122
#
123
# To help guide applications in selecting a suitable strong
124
# java.security.SecureRandom implementation, Java distributions should
125
# indicate a list of known strong implementations using the property.
126
#
127
# This is a comma-separated list of algorithm and/or algorithm:provider
128
# entries.
129
#
130
securerandom.strongAlgorithms=Windows-PRNG:SunMSCAPI,SHA1PRNG:SUN
131

    
132
#
133
# Class to instantiate as the javax.security.auth.login.Configuration
134
# provider.
135
#
136
login.configuration.provider=sun.security.provider.ConfigFile
137

    
138
#
139
# Default login configuration file
140
#
141
#login.config.url.1=file:${user.home}/.java.login.config
142

    
143
#
144
# Class to instantiate as the system Policy. This is the name of the class
145
# that will be used as the Policy object.
146
#
147
policy.provider=sun.security.provider.PolicyFile
148

    
149
# The default is to have a single system-wide policy file,
150
# and a policy file in the user's home directory.
151
policy.url.1=file:${java.home}/lib/security/java.policy
152
policy.url.2=file:${user.home}/.java.policy
153

    
154
# whether or not we expand properties in the policy file
155
# if this is set to false, properties (${...}) will not be expanded in policy
156
# files.
157
policy.expandProperties=true
158

    
159
# whether or not we allow an extra policy to be passed on the command line
160
# with -Djava.security.policy=somefile. Comment out this line to disable
161
# this feature.
162
policy.allowSystemProperty=true
163

    
164
# whether or not we look into the IdentityScope for trusted Identities
165
# when encountering a 1.1 signed JAR file. If the identity is found
166
# and is trusted, we grant it AllPermission.
167
policy.ignoreIdentityScope=false
168

    
169
#
170
# Default keystore type.
171
#
172
keystore.type=jks
173

    
174
#
175
# Controls compatibility mode for the JKS keystore type.
176
#
177
# When set to 'true', the JKS keystore type supports loading
178
# keystore files in either JKS or PKCS12 format. When set to 'false'
179
# it supports loading only JKS keystore files.
180
#
181
keystore.type.compat=true
182

    
183
#
184
# List of comma-separated packages that start with or equal this string
185
# will cause a security exception to be thrown when
186
# passed to checkPackageAccess unless the
187
# corresponding RuntimePermission ("accessClassInPackage."+package) has
188
# been granted.
189
package.access=sun.,\
190
               com.sun.xml.internal.,\
191
               com.sun.imageio.,\
192
               com.sun.istack.internal.,\
193
               com.sun.jmx.,\
194
               com.sun.media.sound.,\
195
               com.sun.naming.internal.,\
196
               com.sun.proxy.,\
197
               com.sun.corba.se.,\
198
               com.sun.org.apache.bcel.internal.,\
199
               com.sun.org.apache.regexp.internal.,\
200
               com.sun.org.apache.xerces.internal.,\
201
               com.sun.org.apache.xpath.internal.,\
202
               com.sun.org.apache.xalan.internal.extensions.,\
203
               com.sun.org.apache.xalan.internal.lib.,\
204
               com.sun.org.apache.xalan.internal.res.,\
205
               com.sun.org.apache.xalan.internal.templates.,\
206
               com.sun.org.apache.xalan.internal.utils.,\
207
               com.sun.org.apache.xalan.internal.xslt.,\
208
               com.sun.org.apache.xalan.internal.xsltc.cmdline.,\
209
               com.sun.org.apache.xalan.internal.xsltc.compiler.,\
210
               com.sun.org.apache.xalan.internal.xsltc.trax.,\
211
               com.sun.org.apache.xalan.internal.xsltc.util.,\
212
               com.sun.org.apache.xml.internal.res.,\
213
               com.sun.org.apache.xml.internal.resolver.helpers.,\
214
               com.sun.org.apache.xml.internal.resolver.readers.,\
215
               com.sun.org.apache.xml.internal.security.,\
216
               com.sun.org.apache.xml.internal.serializer.utils.,\
217
               com.sun.org.apache.xml.internal.utils.,\
218
               com.sun.org.glassfish.,\
219
               com.oracle.xmlns.internal.,\
220
               com.oracle.webservices.internal.,\
221
               oracle.jrockit.jfr.,\
222
               org.jcp.xml.dsig.internal.,\
223
               jdk.internal.,\
224
               jdk.nashorn.internal.,\
225
               jdk.nashorn.tools.,\
226
               jdk.xml.internal.,\
227
               com.sun.activation.registries.,\
228
               com.sun.java.accessibility.,\
229
               com.sun.browser.,\
230
               com.sun.glass.,\
231
               com.sun.javafx.,\
232
               com.sun.media.,\
233
               com.sun.openpisces.,\
234
               com.sun.prism.,\
235
               com.sun.scenario.,\
236
               com.sun.t2k.,\
237
               com.sun.pisces.,\
238
               com.sun.webkit.,\
239
               jdk.management.resource.internal.
240

    
241
#
242
# List of comma-separated packages that start with or equal this string
243
# will cause a security exception to be thrown when
244
# passed to checkPackageDefinition unless the
245
# corresponding RuntimePermission ("defineClassInPackage."+package) has
246
# been granted.
247
#
248
# by default, none of the class loaders supplied with the JDK call
249
# checkPackageDefinition.
250
#
251
package.definition=sun.,\
252
                   com.sun.xml.internal.,\
253
                   com.sun.imageio.,\
254
                   com.sun.istack.internal.,\
255
                   com.sun.jmx.,\
256
                   com.sun.media.sound.,\
257
                   com.sun.naming.internal.,\
258
                   com.sun.proxy.,\
259
                   com.sun.corba.se.,\
260
                   com.sun.org.apache.bcel.internal.,\
261
                   com.sun.org.apache.regexp.internal.,\
262
                   com.sun.org.apache.xerces.internal.,\
263
                   com.sun.org.apache.xpath.internal.,\
264
                   com.sun.org.apache.xalan.internal.extensions.,\
265
                   com.sun.org.apache.xalan.internal.lib.,\
266
                   com.sun.org.apache.xalan.internal.res.,\
267
                   com.sun.org.apache.xalan.internal.templates.,\
268
                   com.sun.org.apache.xalan.internal.utils.,\
269
                   com.sun.org.apache.xalan.internal.xslt.,\
270
                   com.sun.org.apache.xalan.internal.xsltc.cmdline.,\
271
                   com.sun.org.apache.xalan.internal.xsltc.compiler.,\
272
                   com.sun.org.apache.xalan.internal.xsltc.trax.,\
273
                   com.sun.org.apache.xalan.internal.xsltc.util.,\
274
                   com.sun.org.apache.xml.internal.res.,\
275
                   com.sun.org.apache.xml.internal.resolver.helpers.,\
276
                   com.sun.org.apache.xml.internal.resolver.readers.,\
277
                   com.sun.org.apache.xml.internal.security.,\
278
                   com.sun.org.apache.xml.internal.serializer.utils.,\
279
                   com.sun.org.apache.xml.internal.utils.,\
280
                   com.sun.org.glassfish.,\
281
                   com.oracle.xmlns.internal.,\
282
                   com.oracle.webservices.internal.,\
283
                   oracle.jrockit.jfr.,\
284
                   org.jcp.xml.dsig.internal.,\
285
                   jdk.internal.,\
286
                   jdk.nashorn.internal.,\
287
                   jdk.nashorn.tools.,\
288
                   jdk.xml.internal.,\
289
                   com.sun.activation.registries.,\
290
                   com.sun.java.accessibility.,\
291
                   com.sun.browser.,\
292
                   com.sun.glass.,\
293
                   com.sun.javafx.,\
294
                   com.sun.media.,\
295
                   com.sun.openpisces.,\
296
                   com.sun.prism.,\
297
                   com.sun.scenario.,\
298
                   com.sun.t2k.,\
299
                   com.sun.pisces.,\
300
                   com.sun.webkit.,\
301
                   jdk.management.resource.internal.
302

    
303
#
304
# Determines whether this properties file can be appended to
305
# or overridden on the command line via -Djava.security.properties
306
#
307
security.overridePropertiesFile=true
308

    
309
#
310
# Determines the default key and trust manager factory algorithms for
311
# the javax.net.ssl package.
312
#
313
ssl.KeyManagerFactory.algorithm=SunX509
314
ssl.TrustManagerFactory.algorithm=PKIX
315

    
316
#
317
# The Java-level namelookup cache policy for successful lookups:
318
#
319
# any negative value: caching forever
320
# any positive value: the number of seconds to cache an address for
321
# zero: do not cache
322
#
323
# default value is forever (FOREVER). For security reasons, this
324
# caching is made forever when a security manager is set. When a security
325
# manager is not set, the default behavior in this implementation
326
# is to cache for 30 seconds.
327
#
328
# NOTE: setting this to anything other than the default value can have
329
#       serious security implications. Do not set it unless
330
#       you are sure you are not exposed to DNS spoofing attack.
331
#
332
#networkaddress.cache.ttl=-1
333

    
334
# The Java-level namelookup cache policy for failed lookups:
335
#
336
# any negative value: cache forever
337
# any positive value: the number of seconds to cache negative lookup results
338
# zero: do not cache
339
#
340
# In some Microsoft Windows networking environments that employ
341
# the WINS name service in addition to DNS, name service lookups
342
# that fail may take a noticeably long time to return (approx. 5 seconds).
343
# For this reason the default caching policy is to maintain these
344
# results for 10 seconds.
345
#
346
#
347
networkaddress.cache.negative.ttl=10
348

    
349
#
350
# Properties to configure OCSP for certificate revocation checking
351
#
352

    
353
# Enable OCSP
354
#
355
# By default, OCSP is not used for certificate revocation checking.
356
# This property enables the use of OCSP when set to the value "true".
357
#
358
# NOTE: SocketPermission is required to connect to an OCSP responder.
359
#
360
# Example,
361
#   ocsp.enable=true
362

    
363
#
364
# Location of the OCSP responder
365
#
366
# By default, the location of the OCSP responder is determined implicitly
367
# from the certificate being validated. This property explicitly specifies
368
# the location of the OCSP responder. The property is used when the
369
# Authority Information Access extension (defined in RFC 3280) is absent
370
# from the certificate or when it requires overriding.
371
#
372
# Example,
373
#   ocsp.responderURL=http://ocsp.example.net:80
374

    
375
#
376
# Subject name of the OCSP responder's certificate
377
#
378
# By default, the certificate of the OCSP responder is that of the issuer
379
# of the certificate being validated. This property identifies the certificate
380
# of the OCSP responder when the default does not apply. Its value is a string
381
# distinguished name (defined in RFC 2253) which identifies a certificate in
382
# the set of certificates supplied during cert path validation. In cases where
383
# the subject name alone is not sufficient to uniquely identify the certificate
384
# then both the "ocsp.responderCertIssuerName" and
385
# "ocsp.responderCertSerialNumber" properties must be used instead. When this
386
# property is set then those two properties are ignored.
387
#
388
# Example,
389
#   ocsp.responderCertSubjectName="CN=OCSP Responder, O=XYZ Corp"
390

    
391
#
392
# Issuer name of the OCSP responder's certificate
393
#
394
# By default, the certificate of the OCSP responder is that of the issuer
395
# of the certificate being validated. This property identifies the certificate
396
# of the OCSP responder when the default does not apply. Its value is a string
397
# distinguished name (defined in RFC 2253) which identifies a certificate in
398
# the set of certificates supplied during cert path validation. When this
399
# property is set then the "ocsp.responderCertSerialNumber" property must also
400
# be set. When the "ocsp.responderCertSubjectName" property is set then this
401
# property is ignored.
402
#
403
# Example,
404
#   ocsp.responderCertIssuerName="CN=Enterprise CA, O=XYZ Corp"
405

    
406
#
407
# Serial number of the OCSP responder's certificate
408
#
409
# By default, the certificate of the OCSP responder is that of the issuer
410
# of the certificate being validated. This property identifies the certificate
411
# of the OCSP responder when the default does not apply. Its value is a string
412
# of hexadecimal digits (colon or space separators may be present) which
413
# identifies a certificate in the set of certificates supplied during cert path
414
# validation. When this property is set then the "ocsp.responderCertIssuerName"
415
# property must also be set. When the "ocsp.responderCertSubjectName" property
416
# is set then this property is ignored.
417
#
418
# Example,
419
#   ocsp.responderCertSerialNumber=2A:FF:00
420

    
421
#
422
# Policy for failed Kerberos KDC lookups:
423
#
424
# When a KDC is unavailable (network error, service failure, etc), it is
425
# put inside a blacklist and accessed less often for future requests. The
426
# value (case-insensitive) for this policy can be:
427
#
428
# tryLast
429
#    KDCs in the blacklist are always tried after those not on the list.
430
#
431
# tryLess[:max_retries,timeout]
432
#    KDCs in the blacklist are still tried by their order in the configuration,
433
#    but with smaller max_retries and timeout values. max_retries and timeout
434
#    are optional numerical parameters (default 1 and 5000, which means once
435
#    and 5 seconds). Please notes that if any of the values defined here is
436
#    more than what is defined in krb5.conf, it will be ignored.
437
#
438
# Whenever a KDC is detected as available, it is removed from the blacklist.
439
# The blacklist is reset when krb5.conf is reloaded. You can add
440
# refreshKrb5Config=true to a JAAS configuration file so that krb5.conf is
441
# reloaded whenever a JAAS authentication is attempted.
442
#
443
# Example,
444
#   krb5.kdc.bad.policy = tryLast
445
#   krb5.kdc.bad.policy = tryLess:2,2000
446
krb5.kdc.bad.policy = tryLast
447

    
448
# Algorithm restrictions for certification path (CertPath) processing
449
#
450
# In some environments, certain algorithms or key lengths may be undesirable
451
# for certification path building and validation.  For example, "MD2" is
452
# generally no longer considered to be a secure hash algorithm.  This section
453
# describes the mechanism for disabling algorithms based on algorithm name
454
# and/or key length.  This includes algorithms used in certificates, as well
455
# as revocation information such as CRLs and signed OCSP Responses.
456
# The syntax of the disabled algorithm string is described as follows:
457
#   DisabledAlgorithms:
458
#       " DisabledAlgorithm { , DisabledAlgorithm } "
459
#
460
#   DisabledAlgorithm:
461
#       AlgorithmName [Constraint] { '&' Constraint }
462
#
463
#   AlgorithmName:
464
#       (see below)
465
#
466
#   Constraint:
467
#       KeySizeConstraint | CAConstraint | DenyAfterConstraint |
468
#       UsageConstraint
469
#
470
#   KeySizeConstraint:
471
#       keySize Operator KeyLength
472
#
473
#   Operator:
474
#       <= | < | == | != | >= | >
475
#
476
#   KeyLength:
477
#       Integer value of the algorithm's key length in bits
478
#
479
#   CAConstraint:
480
#       jdkCA
481
#
482
#   DenyAfterConstraint:
483
#       denyAfter YYYY-MM-DD
484
#
485
#   UsageConstraint:
486
#       usage [TLSServer] [TLSClient] [SignedJAR]
487
#
488
# The "AlgorithmName" is the standard algorithm name of the disabled
489
# algorithm. See "Java Cryptography Architecture Standard Algorithm Name
490
# Documentation" for information about Standard Algorithm Names.  Matching
491
# is performed using a case-insensitive sub-element matching rule.  (For
492
# example, in "SHA1withECDSA" the sub-elements are "SHA1" for hashing and
493
# "ECDSA" for signatures.)  If the assertion "AlgorithmName" is a
494
# sub-element of the certificate algorithm name, the algorithm will be
495
# rejected during certification path building and validation.  For example,
496
# the assertion algorithm name "DSA" will disable all certificate algorithms
497
# that rely on DSA, such as NONEwithDSA, SHA1withDSA.  However, the assertion
498
# will not disable algorithms related to "ECDSA".
499
#
500
# A "Constraint" defines restrictions on the keys and/or certificates for
501
# a specified AlgorithmName:
502
#
503
#   KeySizeConstraint:
504
#     keySize Operator KeyLength
505
#       The constraint requires a key of a valid size range if the
506
#       "AlgorithmName" is of a key algorithm.  The "KeyLength" indicates
507
#       the key size specified in number of bits.  For example,
508
#       "RSA keySize <= 1024" indicates that any RSA key with key size less
509
#       than or equal to 1024 bits should be disabled, and
510
#       "RSA keySize < 1024, RSA keySize > 2048" indicates that any RSA key
511
#       with key size less than 1024 or greater than 2048 should be disabled.
512
#       This constraint is only used on algorithms that have a key size.
513
#
514
#   CAConstraint:
515
#     jdkCA
516
#       This constraint prohibits the specified algorithm only if the
517
#       algorithm is used in a certificate chain that terminates at a marked
518
#       trust anchor in the lib/security/cacerts keystore.  If the jdkCA
519
#       constraint is not set, then all chains using the specified algorithm
520
#       are restricted.  jdkCA may only be used once in a DisabledAlgorithm
521
#       expression.
522
#       Example:  To apply this constraint to SHA-1 certificates, include
523
#       the following:  "SHA1 jdkCA"
524
#
525
#   DenyAfterConstraint:
526
#     denyAfter YYYY-MM-DD
527
#       This constraint prohibits a certificate with the specified algorithm
528
#       from being used after the date regardless of the certificate's
529
#       validity.  JAR files that are signed and timestamped before the
530
#       constraint date with certificates containing the disabled algorithm
531
#       will not be restricted.  The date is processed in the UTC timezone.
532
#       This constraint can only be used once in a DisabledAlgorithm
533
#       expression.
534
#       Example:  To deny usage of RSA 2048 bit certificates after Feb 3 2020,
535
#       use the following:  "RSA keySize == 2048 & denyAfter 2020-02-03"
536
#
537
#   UsageConstraint:
538
#     usage [TLSServer] [TLSClient] [SignedJAR]
539
#       This constraint prohibits the specified algorithm for
540
#       a specified usage.  This should be used when disabling an algorithm
541
#       for all usages is not practical. 'TLSServer' restricts the algorithm
542
#       in TLS server certificate chains when server authentication is
543
#       performed. 'TLSClient' restricts the algorithm in TLS client
544
#       certificate chains when client authentication is performed.
545
#       'SignedJAR' constrains use of certificates in signed jar files.
546
#       The usage type follows the keyword and more than one usage type can
547
#       be specified with a whitespace delimiter.
548
#       Example:  "SHA1 usage TLSServer TLSClient"
549
#
550
# When an algorithm must satisfy more than one constraint, it must be
551
# delimited by an ampersand '&'.  For example, to restrict certificates in a
552
# chain that terminate at a distribution provided trust anchor and contain
553
# RSA keys that are less than or equal to 1024 bits, add the following
554
# constraint:  "RSA keySize <= 1024 & jdkCA".
555
#
556
# All DisabledAlgorithms expressions are processed in the order defined in the
557
# property.  This requires lower keysize constraints to be specified
558
# before larger keysize constraints of the same algorithm.  For example:
559
# "RSA keySize < 1024 & jdkCA, RSA keySize < 2048".
560
#
561
# Note: The algorithm restrictions do not apply to trust anchors or
562
# self-signed certificates.
563
#
564
# Note: This property is currently used by Oracle's PKIX implementation. It
565
# is not guaranteed to be examined and used by other implementations.
566
#
567
# Example:
568
#   jdk.certpath.disabledAlgorithms=MD2, DSA, RSA keySize < 2048
569
#
570
#
571
jdk.certpath.disabledAlgorithms=MD2, MD5, SHA1 jdkCA & usage TLSServer, \
572
    RSA keySize < 1024, DSA keySize < 1024, EC keySize < 224
573

    
574
#
575
# Algorithm restrictions for signed JAR files
576
#
577
# In some environments, certain algorithms or key lengths may be undesirable
578
# for signed JAR validation.  For example, "MD2" is generally no longer
579
# considered to be a secure hash algorithm.  This section describes the
580
# mechanism for disabling algorithms based on algorithm name and/or key length.
581
# JARs signed with any of the disabled algorithms or key sizes will be treated
582
# as unsigned.
583
#
584
# The syntax of the disabled algorithm string is described as follows:
585
#   DisabledAlgorithms:
586
#       " DisabledAlgorithm { , DisabledAlgorithm } "
587
#
588
#   DisabledAlgorithm:
589
#       AlgorithmName [Constraint] { '&' Constraint }
590
#
591
#   AlgorithmName:
592
#       (see below)
593
#
594
#   Constraint:
595
#       KeySizeConstraint | DenyAfterConstraint
596
#
597
#   KeySizeConstraint:
598
#       keySize Operator KeyLength
599
#
600
#   DenyAfterConstraint:
601
#       denyAfter YYYY-MM-DD
602
#
603
#   Operator:
604
#       <= | < | == | != | >= | >
605
#
606
#   KeyLength:
607
#       Integer value of the algorithm's key length in bits
608
#
609
# Note: This property is currently used by the JDK Reference
610
# implementation. It is not guaranteed to be examined and used by other
611
# implementations.
612
#
613
# See "jdk.certpath.disabledAlgorithms" for syntax descriptions.
614
#
615
jdk.jar.disabledAlgorithms=MD2, MD5, RSA keySize < 1024, DSA keySize < 1024
616

    
617
#
618
# Algorithm restrictions for Secure Socket Layer/Transport Layer Security
619
# (SSL/TLS) processing
620
#
621
# In some environments, certain algorithms or key lengths may be undesirable
622
# when using SSL/TLS.  This section describes the mechanism for disabling
623
# algorithms during SSL/TLS security parameters negotiation, including
624
# protocol version negotiation, cipher suites selection, peer authentication
625
# and key exchange mechanisms.
626
#
627
# Disabled algorithms will not be negotiated for SSL/TLS connections, even
628
# if they are enabled explicitly in an application.
629
#
630
# For PKI-based peer authentication and key exchange mechanisms, this list
631
# of disabled algorithms will also be checked during certification path
632
# building and validation, including algorithms used in certificates, as
633
# well as revocation information such as CRLs and signed OCSP Responses.
634
# This is in addition to the jdk.certpath.disabledAlgorithms property above.
635
#
636
# See the specification of "jdk.certpath.disabledAlgorithms" for the
637
# syntax of the disabled algorithm string.
638
#
639
# Note: The algorithm restrictions do not apply to trust anchors or
640
# self-signed certificates.
641
#
642
# Note: This property is currently used by the JDK Reference implementation.
643
# It is not guaranteed to be examined and used by other implementations.
644
#
645
# Example:
646
#   jdk.tls.disabledAlgorithms=MD5, SSLv3, DSA, RSA keySize < 2048
647
jdk.tls.disabledAlgorithms=SSLv3, RC4, MD5withRSA, DH keySize < 1024, \
648
    EC keySize < 224, DES40_CBC, RC4_40, 3DES_EDE_CBC
649

    
650
# Legacy algorithms for Secure Socket Layer/Transport Layer Security (SSL/TLS)
651
# processing in JSSE implementation.
652
#
653
# In some environments, a certain algorithm may be undesirable but it
654
# cannot be disabled because of its use in legacy applications.  Legacy
655
# algorithms may still be supported, but applications should not use them
656
# as the security strength of legacy algorithms are usually not strong enough
657
# in practice.
658
#
659
# During SSL/TLS security parameters negotiation, legacy algorithms will
660
# not be negotiated unless there are no other candidates.
661
#
662
# The syntax of the legacy algorithms string is described as this Java
663
# BNF-style:
664
#   LegacyAlgorithms:
665
#       " LegacyAlgorithm { , LegacyAlgorithm } "
666
#
667
#   LegacyAlgorithm:
668
#       AlgorithmName (standard JSSE algorithm name)
669
#
670
# See the specification of security property "jdk.certpath.disabledAlgorithms"
671
# for the syntax and description of the "AlgorithmName" notation.
672
#
673
# Per SSL/TLS specifications, cipher suites have the form:
674
#       SSL_KeyExchangeAlg_WITH_CipherAlg_MacAlg
675
# or
676
#       TLS_KeyExchangeAlg_WITH_CipherAlg_MacAlg
677
#
678
# For example, the cipher suite TLS_RSA_WITH_AES_128_CBC_SHA uses RSA as the
679
# key exchange algorithm, AES_128_CBC (128 bits AES cipher algorithm in CBC
680
# mode) as the cipher (encryption) algorithm, and SHA-1 as the message digest
681
# algorithm for HMAC.
682
#
683
# The LegacyAlgorithm can be one of the following standard algorithm names:
684
#     1. JSSE cipher suite name, e.g., TLS_RSA_WITH_AES_128_CBC_SHA
685
#     2. JSSE key exchange algorithm name, e.g., RSA
686
#     3. JSSE cipher (encryption) algorithm name, e.g., AES_128_CBC
687
#     4. JSSE message digest algorithm name, e.g., SHA
688
#
689
# See SSL/TLS specifications and "Java Cryptography Architecture Standard
690
# Algorithm Name Documentation" for information about the algorithm names.
691
#
692
# Note: This property is currently used by the JDK Reference implementation.
693
# It is not guaranteed to be examined and used by other implementations.
694
# There is no guarantee the property will continue to exist or be of the
695
# same syntax in future releases.
696
#
697
# Example:
698
#   jdk.tls.legacyAlgorithms=DH_anon, DES_CBC, SSL_RSA_WITH_RC4_128_MD5
699
#
700
jdk.tls.legacyAlgorithms= \
701
        K_NULL, C_NULL, M_NULL, \
702
        DH_anon, ECDH_anon, \
703
        RC4_128, RC4_40, DES_CBC, DES40_CBC, \
704
        3DES_EDE_CBC
705

    
706
# The pre-defined default finite field Diffie-Hellman ephemeral (DHE)
707
# parameters for Transport Layer Security (SSL/TLS/DTLS) processing.
708
#
709
# In traditional SSL/TLS/DTLS connections where finite field DHE parameters
710
# negotiation mechanism is not used, the server offers the client group
711
# parameters, base generator g and prime modulus p, for DHE key exchange.
712
# It is recommended to use dynamic group parameters.  This property defines
713
# a mechanism that allows you to specify custom group parameters.
714
#
715
# The syntax of this property string is described as this Java BNF-style:
716
#   DefaultDHEParameters:
717
#       DefinedDHEParameters { , DefinedDHEParameters }
718
#
719
#   DefinedDHEParameters:
720
#       "{" DHEPrimeModulus , DHEBaseGenerator "}"
721
#
722
#   DHEPrimeModulus:
723
#       HexadecimalDigits
724
#
725
#   DHEBaseGenerator:
726
#       HexadecimalDigits
727
#
728
#   HexadecimalDigits:
729
#       HexadecimalDigit { HexadecimalDigit }
730
#
731
#   HexadecimalDigit: one of
732
#       0 1 2 3 4 5 6 7 8 9 A B C D E F a b c d e f
733
#
734
# Whitespace characters are ignored.
735
#
736
# The "DefinedDHEParameters" defines the custom group parameters, prime
737
# modulus p and base generator g, for a particular size of prime modulus p.
738
# The "DHEPrimeModulus" defines the hexadecimal prime modulus p, and the
739
# "DHEBaseGenerator" defines the hexadecimal base generator g of a group
740
# parameter.  It is recommended to use safe primes for the custom group
741
# parameters.
742
#
743
# If this property is not defined or the value is empty, the underlying JSSE
744
# provider's default group parameter is used for each connection.
745
#
746
# If the property value does not follow the grammar, or a particular group
747
# parameter is not valid, the connection will fall back and use the
748
# underlying JSSE provider's default group parameter.
749
#
750
# Note: This property is currently used by OpenJDK's JSSE implementation. It
751
# is not guaranteed to be examined and used by other implementations.
752
#
753
# Example:
754
#   jdk.tls.server.defaultDHEParameters=
755
#       { \
756
#       FFFFFFFF FFFFFFFF C90FDAA2 2168C234 C4C6628B 80DC1CD1 \
757
#       29024E08 8A67CC74 020BBEA6 3B139B22 514A0879 8E3404DD \
758
#       EF9519B3 CD3A431B 302B0A6D F25F1437 4FE1356D 6D51C245 \
759
#       E485B576 625E7EC6 F44C42E9 A637ED6B 0BFF5CB6 F406B7ED \
760
#       EE386BFB 5A899FA5 AE9F2411 7C4B1FE6 49286651 ECE65381 \
761
#       FFFFFFFF FFFFFFFF, 2}
762

    
763
# Cryptographic Jurisdiction Policy defaults
764
#
765
# Import and export control rules on cryptographic software vary from
766
# country to country.  By default, the JDK provides two different sets of
767
# cryptographic policy files:
768
#
769
#     unlimited:  These policy files contain no restrictions on cryptographic
770
#                 strengths or algorithms.
771
#
772
#     limited:    These policy files contain more restricted cryptographic
773
#                 strengths, and are still available if your country or
774
#                 usage requires the traditional restrictive policy.
775
#
776
# The JDK JCE framework uses the unlimited policy files by default.
777
# However the user may explicitly choose a set either by defining the
778
# "crypto.policy" Security property or by installing valid JCE policy
779
# jar files into the traditional JDK installation location.  To better
780
# support older JDK Update releases, the "crypto.policy" property is not
781
# defined by default.  See below for more information.
782
#
783
# The following logic determines which policy files are used:
784
#
785
#         <java-home> refers to the directory where the JRE was
786
#         installed and may be determined using the "java.home"
787
#         System property.
788
#
789
# 1.  If the Security property "crypto.policy" has been defined,
790
#     then the following mechanism is used:
791
#
792
#     The policy files are stored as jar files in subdirectories of
793
# <java-home>/lib/security/policy.  Each directory contains a complete
794
# set of policy files.
795
#
796
#     The "crypto.policy" Security property controls the directory
797
#     selection, and thus the effective cryptographic policy.
798
#
799
# The default set of directories is:
800
#
801
#     limited | unlimited
802
#
803
# 2.  If the "crypto.policy" property is not set and the traditional
804
#     US_export_policy.jar and local_policy.jar files
805
#     (e.g. limited/unlimited) are found in the legacy
806
#     <java-home>/lib/security directory, then the rules embedded within
807
#     those jar files will be used. This helps preserve compatibility
808
# for users upgrading from an older installation.
809
#
810
# 3.  If the jar files are not present in the legacy location
811
#     and the "crypto.policy" Security property is not defined,
812
#     then the JDK will use the unlimited settings (equivalent to
813
#     crypto.policy=unlimited)
814
#
815
# Please see the JCA documentation for additional information on these
816
# files and formats.
817
#
818
# YOU ARE ADVISED TO CONSULT YOUR EXPORT/IMPORT CONTROL COUNSEL OR ATTORNEY
819
# TO DETERMINE THE EXACT REQUIREMENTS.
820
#
821
# Please note that the JCE for Java SE, including the JCE framework,
822
# cryptographic policy files, and standard JCE providers provided with
823
# the Java SE, have been reviewed and approved for export as mass market
824
# encryption item by the US Bureau of Industry and Security.
825
#
826
# Note: This property is currently used by the JDK Reference implementation.
827
# It is not guaranteed to be examined and used by other implementations.
828
#
829
#crypto.policy=unlimited
830

    
831
#
832
# The policy for the XML Signature secure validation mode. The mode is
833
# enabled by setting the property "org.jcp.xml.dsig.secureValidation" to
834
# true with the javax.xml.crypto.XMLCryptoContext.setProperty() method,
835
# or by running the code with a SecurityManager.
836
#
837
#   Policy:
838
#       Constraint {"," Constraint }
839
#   Constraint:
840
#       AlgConstraint | MaxTransformsConstraint | MaxReferencesConstraint |
841
#       ReferenceUriSchemeConstraint | KeySizeConstraint | OtherConstraint
842
#   AlgConstraint
843
#       "disallowAlg" Uri
844
#   MaxTransformsConstraint:
845
#       "maxTransforms" Integer
846
#   MaxReferencesConstraint:
847
#       "maxReferences" Integer
848
#   ReferenceUriSchemeConstraint:
849
#       "disallowReferenceUriSchemes" String { String }
850
#   KeySizeConstraint:
851
#       "minKeySize" KeyAlg Integer
852
#   OtherConstraint:
853
#       "noDuplicateIds" | "noRetrievalMethodLoops"
854
#
855
# For AlgConstraint, Uri is the algorithm URI String that is not allowed.
856
# See the XML Signature Recommendation for more information on algorithm
857
# URI Identifiers. For KeySizeConstraint, KeyAlg is the standard algorithm
858
# name of the key type (ex: "RSA"). If the MaxTransformsConstraint,
859
# MaxReferencesConstraint or KeySizeConstraint (for the same key type) is
860
# specified more than once, only the last entry is enforced.
861
#
862
# Note: This property is currently used by the JDK Reference implementation. It
863
# is not guaranteed to be examined and used by other implementations.
864
#
865
jdk.xml.dsig.secureValidationPolicy=\
866
    disallowAlg http://www.w3.org/TR/1999/REC-xslt-19991116,\
867
    disallowAlg http://www.w3.org/2001/04/xmldsig-more#rsa-md5,\
868
    disallowAlg http://www.w3.org/2001/04/xmldsig-more#hmac-md5,\
869
    disallowAlg http://www.w3.org/2001/04/xmldsig-more#md5,\
870
    maxTransforms 5,\
871
    maxReferences 30,\
872
    disallowReferenceUriSchemes file http https,\
873
    minKeySize RSA 1024,\
874
    minKeySize DSA 1024,\
875
    minKeySize EC 224,\
876
    noDuplicateIds,\
877
    noRetrievalMethodLoops
878

    
879
#
880
# Serialization process-wide filter
881
#
882
# A filter, if configured, is used by java.io.ObjectInputStream during
883
# deserialization to check the contents of the stream.
884
# A filter is configured as a sequence of patterns, each pattern is either
885
# matched against the name of a class in the stream or defines a limit.
886
# Patterns are separated by ";" (semicolon).
887
# Whitespace is significant and is considered part of the pattern.
888
#
889
# If the system property jdk.serialFilter is also specified, it supersedes
890
# the security property value defined here.
891
#
892
# If a pattern includes a "=", it sets a limit.
893
# If a limit appears more than once the last value is used.
894
# Limits are checked before classes regardless of the order in the sequence of patterns.
895
# If any of the limits are exceeded, the filter status is REJECTED.
896
#
897
#   maxdepth=value - the maximum depth of a graph
898
#   maxrefs=value  - the maximum number of internal references
899
#   maxbytes=value - the maximum number of bytes in the input stream
900
#   maxarray=value - the maximum array length allowed
901
#
902
# Other patterns, from left to right, match the class or package name as
903
# returned from Class.getName.
904
# If the class is an array type, the class or package to be matched is the element type.
905
# Arrays of any number of dimensions are treated the same as the element type.
906
# For example, a pattern of "!example.Foo", rejects creation of any instance or
907
# array of example.Foo.
908
#
909
# If the pattern starts with "!", the status is REJECTED if the remaining pattern
910
#   is matched; otherwise the status is ALLOWED if the pattern matches.
911
# If the pattern ends with ".**" it matches any class in the package and all subpackages.
912
# If the pattern ends with ".*" it matches any class in the package.
913
# If the pattern ends with "*", it matches any class with the pattern as a prefix.
914
# If the pattern is equal to the class name, it matches.
915
# Otherwise, the status is UNDECIDED.
916
#
917
#jdk.serialFilter=pattern;pattern
918

    
919
#
920
# RMI Registry Serial Filter
921
#
922
# The filter pattern uses the same format as jdk.serialFilter.
923
# This filter can override the builtin filter if additional types need to be
924
# allowed or rejected from the RMI Registry or to decrease limits but not
925
# to increase limits.
926
# If the limits (maxdepth, maxrefs, or maxbytes) are exceeded, the object is rejected.
927
#
928
# Each non-array type is allowed or rejected if it matches one of the patterns,
929
# evaluated from left to right, and is otherwise allowed. Arrays of any
930
# component type, including subarrays and arrays of primitives, are allowed.
931
#
932
# Array construction of any component type, including subarrays and arrays of
933
# primitives, are allowed unless the length is greater than the maxarray limit.
934
# The filter is applied to each array element.
935
#
936
# The built-in filter allows subclasses of allowed classes and
937
# can approximately be represented as the pattern:
938
#
939
#sun.rmi.registry.registryFilter=\
940
#    maxarray=1000000;\
941
#    maxdepth=20;\
942
#    java.lang.String;\
943
#    java.lang.Number;\
944
#    java.lang.reflect.Proxy;\
945
#    java.rmi.Remote;\
946
#    sun.rmi.server.UnicastRef;\
947
#    sun.rmi.server.RMIClientSocketFactory;\
948
#    sun.rmi.server.RMIServerSocketFactory;\
949
#    java.rmi.activation.ActivationID;\
950
#    java.rmi.server.UID
951
#
952
# RMI Distributed Garbage Collector (DGC) Serial Filter
953
#
954
# The filter pattern uses the same format as jdk.serialFilter.
955
# This filter can override the builtin filter if additional types need to be
956
# allowed or rejected from the RMI DGC.
957
#
958
# The builtin DGC filter can approximately be represented as the filter pattern:
959
#
960
#sun.rmi.transport.dgcFilter=\
961
#    java.rmi.server.ObjID;\
962
#    java.rmi.server.UID;\
963
#    java.rmi.dgc.VMID;\
964
#    java.rmi.dgc.Lease;\
965
#    maxdepth=5;maxarray=10000
966

    
967
# CORBA ORBIorTypeCheckRegistryFilter
968
# Type check enhancement for ORB::string_to_object processing
969
#
970
# An IOR type check filter, if configured, is used by an ORB during
971
# an ORB::string_to_object invocation to check the veracity of the type encoded
972
# in the ior string.
973
#
974
# The filter pattern consists of a semi-colon separated list of class names.
975
# The configured list contains the binary class names of the IDL interface types
976
# corresponding to the IDL stub class to be instantiated.
977
# As such, a filter specifies a list of IDL stub classes that will be
978
# allowed by an ORB when an ORB::string_to_object is invoked.
979
# It is used to specify a white list configuration of acceptable
980
# IDL stub types which may be contained in a stringified IOR
981
# parameter passed as input to an ORB::string_to_object method.
982
#
983
# Note: This property is currently used by the JDK Reference implementation.
984
# It is not guaranteed to be examined and used by other implementations.
985
#
986
#com.sun.CORBA.ORBIorTypeCheckRegistryFilter=binary_class_name;binary_class_name
987

    
988
#
989
# JCEKS Encrypted Key Serial Filter
990
#
991
# This filter, if configured, is used by the JCEKS KeyStore during the
992
# deserialization of the encrypted Key object stored inside a key entry.
993
# If not configured or the filter result is UNDECIDED (i.e. none of the patterns
994
# matches), the filter configured by jdk.serialFilter will be consulted.
995
#
996
# If the system property jceks.key.serialFilter is also specified, it supersedes
997
# the security property value defined here.
998
#
999
# The filter pattern uses the same format as jdk.serialFilter. The default
1000
# pattern allows java.lang.Enum, java.security.KeyRep, java.security.KeyRep$Type,
1001
# and javax.crypto.spec.SecretKeySpec and rejects all the others.
1002
jceks.key.serialFilter = java.lang.Enum;java.security.KeyRep;\
1003
  java.security.KeyRep$Type;javax.crypto.spec.SecretKeySpec;!*