[rfc][icedtea-web] remove redundnat declaration of changeit
jvanek at redhat.com
Thu Apr 2 12:16:58 UTC 2015
On 04/02/2015 10:25 AM, Jiri Vanek wrote:
> On 04/02/2015 03:04 AM, Jacob Wisor wrote:
>> Am 01.04.2015 um 17:40 schrieb Jiri Vanek:
>>> Today Ihad spotted quite serious bug, and I'm wondering no one ever compalined.
>> I have spotted it too but I did not complain because I have learned that IcedTea-Web is full of such
>>> ITW is not able to work with custom password on keystores.
>>> This patch is just small clean up before actual work.
>> Well, I have prepared a far more elaborate patch than this one. The problems here are far deeper
>> reaching than this patch addresses. I'd rather say we should not make any quick shots now and
> Still this is good thing to do....
>> postpone pushing it until after the release of 1.6.
> ..and even for 1.6
>> As you say, this is a preparatory patch, so you can keep on working based on this patch and then
> I'm already doing so. But it do not block to push it.
>> push a set of patches so that we will have a nice history of sequentially dependent patches
>> (changesets, speaking in Mercurial).
> And this is refactoring. So it is definitive worthy to push ahead.
> The patch I'm doing for this is not so complex.
> It wraps all various calls to keyStore.something(password) by utility method, which tries default
> password if it do not work and is not-headless then asks user. Even several times.
> Small question is, whether to save this password ( I'm +1 to save it as char) until java closes.
> Then those passwords will be tried before asking user again.
> Unless you see something wrong with this patch (" remove redundnat declaration of changeit") only,
> I really would like to push rather then keep it locally. Maybe for ever.
Well, maybe you are right :)
Here is second part. And yes.. it really maybe better to merge it with original patch.
The next step will be to move all real work methods to single one, which will attempt password,
and if invalid, then asl user, if again invalid then ask user untilhe gave up. If he put valid
password, thenthis apsword will be saved, and used in any other iteration above keystres - if all
stored passwords fails (including changeit) then user again will be prompted (will not beprompted in
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 8273 bytes
Desc: not available
More information about the distro-pkg-dev