Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Development" <derby-dev@db.apache.org>
Received-SPF: neutral (hermes.apache.org: 32.97.110.130 is neither permitted
 nor denied by domain of suresh.thalamati@gmail.com)
Message-ID: <4283C08A.4090001@gmail.com>
Date: Thu, 12 May 2005 13:46:02 -0700
From: Suresh Thalamati <suresh.thalamati@gmail.com>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
MIME-Version: 1.0
To: Derby Development <derby-dev@db.apache.org>
Subject: Re: [PATCH] Derby 236 BootPassword gets written out in plain text
 in sane mode and in our test environment.
References: <428243AB.1040004@gmail.com> <4283A1A6.8030609@sbcglobal.net>
 <4283A6B6.2060602@gmail.com> <4283AA79.90205@gmail.com>
 <4283AB3E.6080805@gmail.com>
In-Reply-To: <4283AB3E.6080805@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Sunitha Kambhampati wrote:

> Sunitha Kambhampati wrote:
>
>> Suresh Thalamati wrote:
>>
>>> - Why is password hard coded in the test harness code, is it not 
>>> possible to specify it as test property ? for eg on the db URL itself.
>>> +               String encryptUrl = 
>>> "dataEncryption=true;bootPassword=Thursday";
>>>
>> Well, I didnt particularly like to hardcode it this way, but I looked 
>> at the rest of  the test harness ( see encryptionProtocol  in RunTest 
>> and the bootPassword is hardcoded to Thursday) and I followed the 
>> same approach for MultiTest.
>>
>> This issue about reading the bootPassword as a property  (ie 
>> testDataEncryption) seems to be an improvement to the test harness 
>> and I think it is not related to this fix in general which was why I 
>> chose not to make changes to the test harness.
>>
>> But if you feel strongly otherwise please let me know.
>>
>>
> If you agree, I will file a jira entry for this.
>
> Thanks,
> Sunitha.
>
>
Thanks for the explanation,  please file a jira entry. Hard coding 
passwords in the harness code will make it difficult  to
to add  a new test cases  with  different password lengths ..etc.

-suresh


-suresht