[Esapi-dev] Changing ESAPI.properties

[Rob Spremulli]

actually, one note here:  on windows XP, the same error is thrown, but
only from explorer.  there's no problem creating such a directory with
mkdir on the command line.  I've never tried on windows 7, but I doubt
they removed that functionality

On 11/22/10, augustd <augustd at codemagi.com> wrote:
> One more reason to remove the dot from the .esapi folder name:
>
> When you try to create a folder whose name starts with a '.' in Windows
> Explorer in Windows 7, it reports "You must type a file name." and will not
> let you change the name.
>
> -August
>
>
> On Tue, Nov 2, 2010 at 7:46 PM, augustd <augustd at codemagi.com> wrote:
>
>> I added the new/changed properties I introduced over my last few checkins
>> to the TEST version of ESAPI.properties and retested:
>>
>> Tests run: 512, Failures: 0, Errors: 0, Skipped: 0
>>
>> I have checked in the modified ESAPI.properties as revision #1637.
>>
>> BTW: If you are using NetBeans, you can get it to display the .esapi
>> directory by changing your preferences:
>>
>> Go to: Preferences -> Miscellaneous -> Files
>>
>> Change the Ignored Files Pattern to exclude .esapi:
>>
>> ^(CVS|SCCS|vssver.?\.scc|#.*#|%.*%|_svn)$|~$|^\.(?!htaccess$)(?!esapi$).*$
>>
>> Regards,
>> August
>>
>>
>> On Sun, Oct 31, 2010 at 1:19 PM, augustd <augustd at codemagi.com> wrote:
>>
>>> Thanks Kevin, I will definitely retest my checkins.
>>>
>>> Some OS's and IDE's treat a directory name starting with "." as hidden.
>>> Thus when you do a general search for all files named ESAPI.properties
>>> you
>>> won't find these additional instances. I know I missed this file.
>>>
>>> Certainly in a development environment at least, we should move
>>> ESAPI.properties into an accessible directory? It could still be
>>> obfuscated
>>> by a build script if desired...
>>>
>>> -August
>>>
>>>
>>>
>>> On Sun, Oct 31, 2010 at 6:56 AM, Kevin W. Wall
>>> <kevin.w.wall at gmail.com>wrote:
>>>
>>>> I would like to remind all ESAPI developers that there are *TWO*
>>>> versions
>>>> of ESAPI.properties that need to be modified when you made changes. One
>>>> is
>>>> the one that will be deployed with ESAPI, which is in
>>>>
>>>>        configuration/.esapi/ESAPI.properties
>>>>
>>>> and the other is the one that the JUnit tests use when they execute,
>>>> which
>>>> is in
>>>>
>>>>        src/test/resources/.esapi/ESAPI.properties
>>>>
>>>> I realize that this is somewhat of a pain, but it is somewhat
>>>> necessitated by the requirement that we do not wish to provide
>>>> default values for Encryptor.MasterKey and Encryptor.MasterSalt
>>>> in the version that we deploy with ESAPI.
>>>>
>>>> Anyway, this is just a reminder that when you change something in one of
>>>> these, please make sure that you make the corresponding change (if
>>>> needed)
>>>> in the other one.
>>>>
>>>> Recently, a few of you have updated
>>>> 'configuration/.esapi/ESAPI.properties'
>>>> to add new properties or change existing ones, but have not updated
>>>> 'src/test/resources/.esapi/ESAPI.properties' with similar changes. That
>>>> means that your JUnit tests would not really be testing your change.
>>>>
>>>> If you are one of the contributors who have recently made such changes
>>>> in
>>>> the past month or two, please go back and double-check to ensure that
>>>> you
>>>> have changed both versions of ESAPI.properties files as appropriate.
>>>>
>>>> Thanks,
>>>> -kevin
>>>> --
>>>> Kevin W. Wall
>>>> "The most likely way for the world to be destroyed, most experts agree,
>>>> is by accident. That's where we come in; we're computer professionals.
>>>> We cause accidents."        -- Nathaniel Borenstein, co-creator of MIME
>>>>
>>>> _______________________________________________
>>>> Esapi-dev mailing list
>>>> Esapi-dev at lists.owasp.org
>>>> https://lists.owasp.org/mailman/listinfo/esapi-dev
>>>>
>>>
>>>
>>
>