Debian Codegraph @

src/test/resources/esapi/ESAPI-CommaValidatorFileChecker.properties

raw
1 # OWASP Enterprise Security API (ESAPI) Properties file -- TEST Version
2 #############################################################################
3 #
4 # WARNING WARNING WARNING WARNING WARNING WARNING
5 #
6 # ####### # #
7 # # ###### #### ##### # # ###### ##### ####
8 # # # # # # # # # # #
9 # # ##### #### # # # ##### # # ####
10 # # # # # # # # ##### #
11 # # # # # # # # # # # # #
12 # # ###### #### # # ###### # # ####
13 #
14 # This is NOT the version of ESAPI.properties that you are looking for.
15 # Do NOT use this for your production applications!!!!!
16 #
17 # That is over in the 'configuration/esapi/ESAPI.properties' file. You
18 # should retrieve THAT version from the official GitHub report from
19 # https://github.com/ESAPI/esapi-java-legacy/blob/develop/configuration/esapi/ESAPI.properties
20 # but make sure that you select it from the 'master' branch (which will
21 # correspond to the latest official ESAPI relase). Sorry for the
22 # inconvenience. We are trying to figure out how to get it to the official
23 # "esapi-<releaseVersion>-sources.jar fiel available from Maven Central, but
24 # in the meantime, you will have to get it from GitHub.
25 #
26 # PLEASE do not base your production use of ESAPI on this TEST version of
27 # ESAPI.properties as this test version has been dumbed down in several places
28 # for JUnit testing.
29 #
30 # You have been warned.
31 #
32 #############################################################################
33 #
34 # This file is part of the Open Web Application Security Project (OWASP)
35 # Enterprise Security API (ESAPI) project. For details, please see
36 # http://www.owasp.org/index.php/ESAPI.
37 #
38 # Copyright (c) 2008,2009 - The OWASP Foundation
39 #
40 # DISCUSS: This may cause a major backwards compatibility issue, etc. but
41 # from a name space perspective, we probably should have prefaced
42 # all the property names with ESAPI or at least OWASP. Otherwise
43 # there could be problems is someone loads this properties file into
44 # the System properties. We could also put this file into the
45 # esapi.jar file (perhaps as a ResourceBundle) and then allow an external
46 # ESAPI properties be defined that would overwrite these defaults.
47 # That keeps the application's properties relatively simple as usually
48 # they will only want to override a few properties. If looks like we
49 # already support multiple override levels of this in the
50 # DefaultSecurityConfiguration class, but I'm suggesting placing the
51 # defaults in the esapi.jar itself. That way, if the jar is signed,
52 # we could detect if those properties had been tampered with. (The
53 # code to check the jar signatures is pretty simple... maybe 70-90 LOC,
54 # but off course there is an execution penalty (similar to the way
55 # that the separate sunjce.jar used to be when a class from it was
56 # first loaded). Thoughts?
57 ###############################################################################
58 #
59 # WARNING: Operating system protection should be used to lock down the .esapi
60 # resources directory and all the files inside and all the directories all the
61 # way up to the root directory of the file system. Note that if you are using
62 # file-based implementations, that some files may need to be read-write as they
63 # get updated dynamically.
64 #
65 # Before using, be sure to update the MasterKey and MasterSalt as described below.
66 # N.B.: If you had stored data that you have previously encrypted with ESAPI 1.4,
67 # you *must* FIRST decrypt it using ESAPI 1.4 and then (if so desired)
68 # re-encrypt it with ESAPI 2.0. If you fail to do this, you will NOT be
69 # able to decrypt your data with ESAPI 2.0.
70 #
71 # YOU HAVE BEEN WARNED!!! More details are in the ESAPI 2.0 Release Notes.
72 #
73 #===========================================================================
74 # ESAPI Configuration
75 #
76 # If true, then print all the ESAPI properties set here when they are loaded.
77 # If false, they are not printed. Useful to reduce output when running JUnit tests.
78 # If you need to troubleshoot a properties related problem, turning this on may help,
79 # but we leave it off for running JUnit tests. (It will be 'true' in the one delivered
80 # as part of production ESAPI, mostly for backward compatibility.)
81 ESAPI.printProperties=false
82
83 # ESAPI is designed to be easily extensible. You can use the reference implementation
84 # or implement your own providers to take advantage of your enterprise's security
85 # infrastructure. The functions in ESAPI are referenced using the ESAPI locator, like:
86 #
87 # String ciphertext =
88 # ESAPI.encryptor().encrypt("Secret message"); // Deprecated in 2.0
89 # CipherText cipherText =
90 # ESAPI.encryptor().encrypt(new PlainText("Secret message")); // Preferred
91 #
92 # Below you can specify the classname for the provider that you wish to use in your
93 # application. The only requirement is that it implement the appropriate ESAPI interface.
94 # This allows you to switch security implementations in the future without rewriting the
95 # entire application.
96 #
97 # ExperimentalAccessController requires ESAPI-AccessControlPolicy.xml in .esapi directory
98 ESAPI.AccessControl=org.owasp.esapi.reference.DefaultAccessController
99 # FileBasedAuthenticator requires users.txt file in .esapi directory
100 ESAPI.Authenticator=org.owasp.esapi.reference.FileBasedAuthenticator
101 ESAPI.Encoder=org.owasp.esapi.reference.DefaultEncoder
102 ESAPI.Encryptor=org.owasp.esapi.reference.crypto.JavaEncryptor
103
104 ESAPI.Executor=org.owasp.esapi.reference.DefaultExecutor
105 ESAPI.HTTPUtilities=org.owasp.esapi.reference.DefaultHTTPUtilities
106 ESAPI.IntrusionDetector=org.owasp.esapi.reference.DefaultIntrusionDetector
107 # Log4JFactory Requires log4j.xml or log4j.properties in classpath - http://www.laliluna.de/log4j-tutorial.html
108 ESAPI.Logger=org.owasp.esapi.logging.log4j.Log4JLogFactory
109 #ESAPI.Logger=org.owasp.esapi.reference.JavaLogFactory
110 #ESAPI.Logger=org.owasp.esapi.reference.ExampleExtendedLog4JLogFactory
111 ESAPI.Randomizer=org.owasp.esapi.reference.DefaultRandomizer
112 ESAPI.Validator=org.owasp.esapi.reference.DefaultValidator
113
114 #===========================================================================
115 # ESAPI Authenticator
116 #
117 Authenticator.AllowedLoginAttempts=3
118 Authenticator.MaxOldPasswordHashes=13
119 Authenticator.UsernameParameterName=username
120 Authenticator.PasswordParameterName=password
121 # RememberTokenDuration (in days)
122 Authenticator.RememberTokenDuration=14
123 # Session Timeouts (in minutes)
124 Authenticator.IdleTimeoutDuration=20
125 Authenticator.AbsoluteTimeoutDuration=120
126
127 #===========================================================================
128 # ESAPI Encoder
129 #
130 # ESAPI canonicalizes input before validation to prevent bypassing filters with encoded attacks.
131 # Failure to canonicalize input is a very common mistake when implementing validation schemes.
132 # Canonicalization is automatic when using the ESAPI Validator, but you can also use the
133 # following code to canonicalize data.
134 #
135 # ESAPI.Encoder().canonicalize( "%22hello world&#x22;" );
136 #
137 # Multiple encoding is when a single encoding format is applied multiple times. Allowing
138 # multiple encoding is strongly discouraged.
139 Encoder.AllowMultipleEncoding=false
140
141 # Mixed encoding is when multiple different encoding formats are applied, or when
142 # multiple formats are nested. Allowing multiple encoding is strongly discouraged.
143 Encoder.AllowMixedEncoding=false
144
145 # The default list of codecs to apply when canonicalizing untrusted data. The list should include the codecs
146 # for all downstream interpreters or decoders. For example, if the data is likely to end up in a URL, HTML, or
147 # inside JavaScript, then the list of codecs below is appropriate. The order of the list is not terribly important.
148 Encoder.DefaultCodecList=HTMLEntityCodec,PercentCodec,JavaScriptCodec
149
150
151 #===========================================================================
152 # ESAPI Encryption
153 #
154 # The ESAPI Encryptor provides basic cryptographic functions with a simplified API.
155 # To get started, generate a new key using java -classpath esapi.jar org.owasp.esapi.reference.crypto.JavaEncryptor
156 # There is not currently any support for key rotation, so be careful when changing your key and salt as it
157 # will invalidate all signed, encrypted, and hashed data.
158 #
159 # WARNING: Not all combinations of algorithms and key lengths are supported.
160 # If you choose to use a key length greater than 128, you MUST download the
161 # unlimited strength policy files and install in the lib directory of your JRE/JDK.
162 # See http://java.sun.com/javase/downloads/index.jsp for more information.
163 #
164 # Backward compatibility with ESAPI Java 1.4 is supported by the two deprecated API
165 # methods, Encryptor.encrypt(String) and Encryptor.decrypt(String). However, whenever
166 # possible, these methods should be avoided as they use ECB cipher mode, which in almost
167 # all circumstances a poor choice because of it's weakness. CBC cipher mode is the default
168 # for the new Encryptor encrypt / decrypt methods for ESAPI Java 2.0. In general, you
169 # should only use this compatibility setting if you have persistent data encrypted with
170 # version 1.4 and even then, you should ONLY set this compatibility mode UNTIL
171 # you have decrypted all of your old encrypted data and then re-encrypted it with
172 # ESAPI 2.0 using CBC mode. If you have some reason to mix the deprecated 1.4 mode
173 # with the new 2.0 methods, make sure that you use the same cipher algorithm for both
174 # (256-bit AES was the default for 1.4; 128-bit is the default for 2.0; see below for
175 # more details.) Otherwise, you will have to use the new 2.0 encrypt / decrypt methods
176 # where you can specify a SecretKey. (Note that if you are using the 256-bit AES,
177 # that requires downloading the special jurisdiction policy files mentioned above.)
178 #
179 # ***** IMPORTANT: These are for JUnit testing. Test files may have been
180 # encrypted using these values so do not change these or
181 # those tests will fail. The version under
182 # src/main/resources/.esapi/ESAPI.properties
183 # will be delivered with Encryptor.MasterKey and
184 # Encryptor.MasterSalt set to the empty string.
185 #
186 # FINAL NOTE:
187 # If Maven changes these when run, that needs to be fixed.
188 # 256-bit key... requires unlimited strength jurisdiction policy files
189 ### Encryptor.MasterKey=pJhlri8JbuFYDgkqtHmm9s0Ziug2PE7ovZDyEPm4j14=
190 # 128-bit key
191 Encryptor.MasterKey=a6H9is3hEVGKB4Jut+lOVA==
192 Encryptor.MasterSalt=SbftnvmEWD5ZHHP+pX3fqugNysc=
193 # Encryptor.MasterSalt=
194
195 # Provides the default JCE provider that ESAPI will "prefer" for its symmetric
196 # encryption and hashing. (That is it will look to this provider first, but it
197 # will defer to other providers if the requested algorithm is not implemented
198 # by this provider.) If left unset, ESAPI will just use your Java VM's current
199 # preferred JCE provider, which is generally set in the file
200 # "$JAVA_HOME/jre/lib/security/java.security".
201 #
202 # The main intent of this is to allow ESAPI symmetric encryption to be
203 # used with a FIPS 140-2 compliant crypto-module. For details, see the section
204 # "Using ESAPI Symmetric Encryption with FIPS 140-2 Cryptographic Modules" in
205 # the ESAPI 2.0 Symmetric Encryption User Guide, at:
206 # http://owasp-esapi-java.googlecode.com/svn/trunk/documentation/esapi4java-core-2.0-symmetric-crypto-user-guide.html
207 # However, this property also allows you to easily use an alternate JCE provider
208 # such as "Bouncy Castle" without having to make changes to "java.security".
209 # See Javadoc for SecurityProviderLoader for further details. If you wish to use
210 # a provider that is not known to SecurityProviderLoader, you may specify the
211 # fully-qualified class name of the JCE provider class that implements
212 # java.security.Provider. If the name contains a '.', this is interpreted as
213 # a fully-qualified class name that implements java.security.Provider.
214 #
215 # NOTE: Setting this property has the side-effect of changing it in your application
216 # as well, so if you are using JCE in your application directly rather than
217 # through ESAPI (you wouldn't do that, would you? ;-), it will change the
218 # preferred JCE provider there as well.
219 #
220 # Default: Keeps the JCE provider set to whatever JVM sets it to.
221 Encryptor.PreferredJCEProvider=
222
223 # AES is the most widely used and strongest encryption algorithm. This
224 # should agree with your Encryptor.CipherTransformation property.
225 # By default, ESAPI Java 1.4 uses "PBEWithMD5AndDES" and which is
226 # very weak. It is essentially a password-based encryption key, hashed
227 # with MD5 around 1K times and then encrypted with the weak DES algorithm
228 # (56-bits) using ECB mode and an unspecified padding (it is
229 # JCE provider specific, but most likely "NoPadding"). However, 2.0 uses
230 # "AES/CBC/PKCSPadding". If you want to change these, change them here.
231 # Warning: This property does not control the default reference implementation for
232 # ESAPI 2.0 using JavaEncryptor. Also, this property will be dropped
233 # in the future.
234 # @deprecated
235 Encryptor.EncryptionAlgorithm=AES
236 # For ESAPI Java 2.0 - New encrypt / decrypt methods use this.
237 Encryptor.CipherTransformation=AES/CBC/PKCS5Padding
238
239 # Applies to ESAPI 2.0 and later only!
240 # Comma-separated list of cipher modes that provide *BOTH*
241 # confidentiality *AND* message authenticity. (NIST refers to such cipher
242 # modes as "combined modes" so that's what we shall call them.) If any of these
243 # cipher modes are used then no MAC is calculated and stored
244 # in the CipherText upon encryption. Likewise, if one of these
245 # cipher modes is used with decryption, no attempt will be made
246 # to validate the MAC contained in the CipherText object regardless
247 # of whether it contains one or not. Since the expectation is that
248 # these cipher modes support support message authenticity already,
249 # injecting a MAC in the CipherText object would be at best redundant.
250 #
251 # Note that as of JDK 1.5, the SunJCE provider does not support *any*
252 # of these cipher modes. Of these listed, only GCM and CCM are currently
253 # NIST approved. YMMV for other JCE providers. E.g., Bouncy Castle supports
254 # GCM and CCM with "NoPadding" mode, but not with "PKCS5Padding" or other
255 # padding modes.
256 Encryptor.cipher_modes.combined_modes=GCM,CCM,IAPM,EAX,OCB,CWC
257
258 # Applies to ESAPI 2.0 and later only!
259 # Additional cipher modes allowed for ESAPI 2.0 encryption. These
260 # cipher modes are in _addition_ to those specified by the property
261 # 'Encryptor.cipher_modes.combined_modes'.
262 #
263 # IMPORTANT NOTE: In the official ESAPI.properties we do *NOT* include ECB
264 # here as this is an extremely weak mode. However, we *must*
265 # allow it here so we can test ECB mode. That is important
266 # since the logic is somewhat different (i.e., ECB mode does
267 # not use an IV).
268 # DISCUSS: Better name?
269 # NOTE: ECB added only for testing purposes. Don't try this at home!
270 Encryptor.cipher_modes.additional_allowed=CBC,ECB
271
272 # 128-bit is almost always sufficient and appears to be more resistant to
273 # related key attacks than is 256-bit AES. Use '_' to use default key size
274 # for cipher algorithms (where it makes sense because the algorithm supports
275 # a variable key size). Key length must agree to what's provided as the
276 # cipher transformation, otherwise this will be ignored after logging a
277 # warning.
278 #
279 # NOTE: This is what applies BOTH ESAPI 1.4 and 2.0. See warning above about mixing!
280 Encryptor.EncryptionKeyLength=128
281 # Min key length - to support testing with 2TDEA
282 Encryptor.MinEncryptionKeyLength=112
283
284 # Because 2.x uses CBC mode by default, it requires an initialization vector (IV).
285 # (All cipher modes except ECB require an IV.) Previously there were two choices: we can either
286 # use a fixed IV known to both parties or allow ESAPI to choose a random IV. The
287 # former was deprecated in ESAPI 2.2 and removed in ESAPI 2.3. It was not secure
288 # because the Encryptor (as are all the other major ESAPI components) is a
289 # singleton and thus the same IV would get reused each time. It was not a
290 # well-thought out plan. (To do it correctly means we need to add a setIV() method
291 # and get rid of the Encryptor singleton, thus it will not happen until 3.0.)
292 # However, while the IV does not need to be hidden from adversaries, it is important that the
293 # adversary not be allowed to choose it. Thus for now, ESAPI just chooses a random IV.
294 # Originally there was plans to allow a developer to provide a class and method
295 # name to define a custom static method to generate an IV, but that is just
296 # trouble waiting to happen. Thus in effect, the ONLY acceptable property value
297 # for this property is "random". In the not too distant future (possibly the
298 # next release), I will be removing it, but for now I am leaving this and
299 # checking for it so a ConfigurationException can be thrown if anyone using
300 # ESAPI ignored the deprecation warning message and still has it set to "fixed".
301 #
302 # Valid values: random
303 Encryptor.ChooseIVMethod=random
304
305 # Whether or not CipherText should use a message authentication code (MAC) with it.
306 # This prevents an adversary from altering the IV as well as allowing a more
307 # fool-proof way of determining the decryption failed because of an incorrect
308 # key being supplied. This refers to the "separate" MAC calculated and stored
309 # in CipherText, not part of any MAC that is calculated as a result of a
310 # "combined mode" cipher mode.
311 #
312 # If you are using ESAPI with a FIPS 140-2 cryptographic module, you *must* also
313 # set this property to false.
314 Encryptor.CipherText.useMAC=true
315
316 # Whether or not the PlainText object may be overwritten and then marked
317 # eligible for garbage collection. If not set, this is still treated as 'true'.
318 Encryptor.PlainText.overwrite=true
319
320 # Do not use DES except in a legacy situations. 56-bit is way too small key size.
321 #Encryptor.EncryptionKeyLength=56
322 #Encryptor.MinEncryptionKeyLength=56
323 #Encryptor.EncryptionAlgorithm=DES
324
325 # TripleDES is considered strong enough for most purposes.
326 # Note: There is also a 112-bit version of DESede. Using the 168-bit version
327 # requires downloading the special jurisdiction policy from Sun.
328 #Encryptor.EncryptionKeyLength=168
329 #Encryptor.MinEncryptionKeyLength=112
330 #Encryptor.EncryptionAlgorithm=DESede
331
332 Encryptor.HashAlgorithm=SHA-512
333 Encryptor.HashIterations=1024
334 Encryptor.DigitalSignatureAlgorithm=SHA1withDSA
335 Encryptor.DigitalSignatureKeyLength=1024
336 Encryptor.RandomAlgorithm=SHA1PRNG
337 Encryptor.CharacterEncoding=UTF-8
338 # Currently supported choices for JDK 1.5 and 1.6 are:
339 # HmacSHA1 (160 bits), HmacSHA256 (256 bits), HmacSHA384 (384 bits), and
340 # HmacSHA512 (512 bits).
341 # Note that HmacMD5 is *not* supported for the PRF used by the KDF even though
342 # these JDKs support it.
343 Encryptor.KDF.PRF=HmacSHA256
344
345 #===========================================================================
346 # ESAPI HttpUtilties
347 #
348 # The HttpUtilities provide basic protections to HTTP requests and responses. Primarily these methods
349 # protect against malicious data from attackers, such as unprintable characters, escaped characters,
350 # and other simple attacks. The HttpUtilities also provides utility methods for dealing with cookies,
351 # headers, and CSRF tokens.
352 #
353 # Default file upload location (remember to escape backslashes with \\)
354 HttpUtilities.UploadDir=C:\\ESAPI\\testUpload
355 # let this default to java.io.tmpdir for testing
356 #HttpUtilities.UploadTempDir=C:\\temp
357 # Force flags on cookies, if you use HttpUtilities to set cookies
358 HttpUtilities.ForceHttpOnlySession=false
359 HttpUtilities.ForceSecureSession=false
360 HttpUtilities.ForceHttpOnlyCookies=true
361 HttpUtilities.ForceSecureCookies=true
362 # Maximum size of HTTP headers
363 HttpUtilities.MaxHeaderSize=4096
364 # File upload configuration
365 HttpUtilities.ApprovedUploadExtensions=.pdf,.doc,.docx,.ppt,.pptx,.xls,.xlsx,.rtf,.txt,.jpg,.png
366 HttpUtilities.MaxUploadFileBytes=500000000
367 # Using UTF-8 throughout your stack is highly recommended. That includes your database driver,
368 # container, and any other technologies you may be using. Failure to do this may expose you
369 # to Unicode transcoding injection attacks. Use of UTF-8 does not hinder internationalization.
370 HttpUtilities.ResponseContentType=text/html; charset=UTF-8
371 # This is the name of the cookie used to represent the HTTP session
372 # Typically this will be the default "JSESSIONID"
373 HttpUtilities.HttpSessionIdName=JSESSIONID
374
375
376
377 #===========================================================================
378 # ESAPI Executor
379 # CHECKME - Not sure what this is used for, but surely it should be made OS independent.
380 Executor.WorkingDirectory=C:\\Windows\\Temp
381 Executor.ApprovedExecutables=C:\\Windows\\System32\\cmd.exe,C:\\Windows\\System32\\runas.exe
382
383
384 #===========================================================================
385 # ESAPI Logging
386 # Set the application name if these logs are combined with other applications
387 Logger.ApplicationName=ExampleApplication
388 # If you use an HTML log viewer that does not properly HTML escape log data, you can set LogEncodingRequired to true
389 Logger.LogEncodingRequired=false
390 # Determines whether ESAPI should log the application name. This might be clutter in some single-server/single-app environments.
391 Logger.LogApplicationName=true
392 # Determines whether ESAPI should log the server IP and port. This might be clutter in some single-server environments.
393 Logger.LogServerIP=true
394
395 #===========================================================================
396 # ESAPI Intrusion Detection
397 #
398 # Each event has a base to which .count, .interval, and .action are added
399 # The IntrusionException will fire if we receive "count" events within "interval" seconds
400 # The IntrusionDetector is configurable to take the following actions: log, logout, and disable
401 # (multiple actions separated by commas are allowed e.g. event.test.actions=log,disable
402 #
403 # Custom Events
404 # Names must start with "event." as the base
405 # Use IntrusionDetector.addEvent( "test" ) in your code to trigger "event.test" here
406 # You can also disable intrusion detection completely by changing
407 # the following parameter to true
408 #
409 IntrusionDetector.Disable=false
410 #
411 IntrusionDetector.event.test.count=2
412 IntrusionDetector.event.test.interval=10
413 IntrusionDetector.event.test.actions=disable,log
414
415 # Exception Events
416 # All EnterpriseSecurityExceptions are registered automatically
417 # Call IntrusionDetector.getInstance().addException(e) for Exceptions that do not extend EnterpriseSecurityException
418 # Use the fully qualified classname of the exception as the base
419
420 # any intrusion is an attack
421 IntrusionDetector.org.owasp.esapi.errors.IntrusionException.count=1
422 IntrusionDetector.org.owasp.esapi.errors.IntrusionException.interval=1
423 IntrusionDetector.org.owasp.esapi.errors.IntrusionException.actions=log,disable,logout
424
425 # for test purposes
426 # CHECKME: Shouldn't there be something in the property name itself that designates
427 # that these are for testing???
428 IntrusionDetector.org.owasp.esapi.errors.IntegrityException.count=10
429 IntrusionDetector.org.owasp.esapi.errors.IntegrityException.interval=5
430 IntrusionDetector.org.owasp.esapi.errors.IntegrityException.actions=log,disable,logout
431
432 # rapid validation errors indicate scans or attacks in progress
433 # org.owasp.esapi.errors.ValidationException.count=10
434 # org.owasp.esapi.errors.ValidationException.interval=10
435 # org.owasp.esapi.errors.ValidationException.actions=log,logout
436
437 # sessions jumping between hosts indicates session hijacking
438 IntrusionDetector.org.owasp.esapi.errors.AuthenticationHostException.count=2
439 IntrusionDetector.org.owasp.esapi.errors.AuthenticationHostException.interval=10
440 IntrusionDetector.org.owasp.esapi.errors.AuthenticationHostException.actions=log,logout
441
442
443 #===========================================================================
444 # ESAPI Validation
445 #
446 # The ESAPI Validator works on regular expressions with defined names. You can define names
447 # either here, or you may define application specific patterns in a separate file defined below.
448 # This allows enterprises to specify both organizational standards as well as application specific
449 # validation rules.
450 #
451 #Validator.ConfigurationFile.MultiValued=false
452 Validator.ConfigurationFile=validation-test,comma.properties
453
454 # Validators used by ESAPI
455 Validator.AccountName=^[a-zA-Z0-9]{3,20}$
456 Validator.SystemCommand=^[a-zA-Z\\-\\/]{1,64}$
457 Validator.RoleName=^[a-z]{1,20}$
458 Validator.Redirect=^\\/test.*$
459
460 # Global HTTP Validation Rules
461 # Values with Base64 encoded data (e.g. encrypted state) will need at least [a-zA-Z0-9\/+=]
462 Validator.HTTPScheme=^(http|https)$
463 Validator.HTTPServerName=^[a-zA-Z0-9_.\\-]*$
464 Validator.HTTPCookieName=^[a-zA-Z0-9\\-_]{1,32}$
465 Validator.HTTPCookieValue=^[a-zA-Z0-9\\-\\/+=_ ]{0,1024}$
466 Validator.HTTPHeaderName=^[a-zA-Z0-9\\-_]{1,32}$
467 Validator.HTTPHeaderValue=^[a-zA-Z0-9()\\-=\\*\\.\\?;,+\\/:&_ ]*$
468 Validator.HTTPServletPath=^[a-zA-Z0-9.\\-\\/_]*$
469 Validator.HTTPPath=^[a-zA-Z0-9.\\-_]*$
470 Validator.HTTPURL=^.*$
471 Validator.HTTPJSESSIONID=^[A-Z0-9]{10,30}$
472
473 # Contributed by [email protected]
474 # Googlecode Issue 116 (http://code.google.com/p/owasp-esapi-java/issues/detail?id=116)
475 Validator.HTTPParameterName=^[a-zA-Z0-9_\\-]{1,32}$
476 Validator.HTTPParameterValue=^[-\\p{L}\\p{N}./+=_ !$*?@]{0,1000}$
477 Validator.HTTPContextPath=^/[a-zA-Z0-9.\\-_]*$
478 Validator.HTTPQueryString=^([a-zA-Z0-9_\\-]{1,32}=[\\p{L}\\p{N}.\\-/+=_ !$*?@%]*&?)*$
479 Validator.HTTPURI=^/([a-zA-Z0-9.\\-_]*/?)*$
480
481
482 # Validation of file related input
483 Validator.FileName=^[a-zA-Z0-9!@#$%^&{}\\[\\]()_+\\-=,.~'` ]{1,255}$
484 Validator.DirectoryName=^[a-zA-Z0-9:/\\\\!@#$%^&{}\\[\\]()_+\\-=,.~'` ]{1,255}$
485
486 # Validation of dates. Controls whether or not 'lenient' dates are accepted.
487 # See DataFormat.setLenient(boolean flag) for further details.
488 Validator.AcceptLenientDates=false