On October 21st, 2010, 3:39 p.m., Marco Martin wrote:

for me is okay, even if an obscured password directly in the config file isn't great...
some time ago it did already this thing, why was it removed?

On October 25th, 2010, 5:45 p.m., Chani Armitage wrote:

good question. Mohit, you should look in the svn log and see if there was a reason it was removed...
but since it was still *writing* it and just not reading it, my guess would be that someone wasn't paying attention and removed it accidentally.

On October 26th, 2010, 8:22 a.m., Mohit Kothari wrote:

I went through the log, and it seems that although password was being written to config file but *never* ever read from it.

The functionality was *never* implemented nor removed accidentally.

On October 26th, 2010, 8:36 a.m., Mohit Kothari wrote:

Sorry, i published the last comment instead of discarding it.... the thing is that in configChanged() the password is stored in temporary variable while to check whether to read or write the password its checked on global variable m_password which is empty. hence we get the empty password string whenever we deny the wallet.

ok, i've committed the patch
you can close the request ;)

- Marco

On October 21st, 2010, 6:19 p.m., Mohit Kothari wrote:

It was a bug posted on bugs.kde.org,
Here is the link: https://bugs.kde.org/show_bug.cgi?id=242377
Well it did stored the password in config file but never read it.
So i just added the reading feature and reloaded the history.

I tested it on kdeplasma-addons revision 1187571