I know that
![Tongue :P](https://forum.miranda-ng.org/Smileys/kolobok/tongue.gif)
Since I've talked to him as soon as he changed it...
But it's still better to do it that way.. most "security" works this way... so there's no problem with that. And it's more secure than it is currently anyway.
Like I said before, it can be easily extended to provide real security. Eg. use public key to encrypt new stuff to history, and private key
(encrypted with non stored password) to read back other stuff from history....
(just keep a copy of X messages of history unencrypted to allow message windows to show said X messages)I knew from the beginning that it wasn't bullet proof against developers since TabSRMM was able to read the history anyway... but it still helps against "normal" people and even I wouldn't know how to circumvent it without trying and searching first. I might use Database Editor++ as first try... but if that one would be protected as well, I might just disable History++
At least it requires more work... and History++ could be made to not dynamically load/unload and thus requires Miranda to restart and eventually asks for password on startup.
There's no argument for not supporting it. It did work, it does work and it's more than we have now.
(and quite painless to implement)addition:Further more, I said ghazan that I also liked the old Database Editor++ behavior with "encrypted" passwords.. as password were not visible without clicking them first and thus it's way easier to show others some settings in a safe manner... for example to take a screen of some "hidden" settings or showing someone with teamviewer some settings etc...
Compared it's definitely a step back.
Miranda always needs to focus normal people, simplify as much as possible even when it means to use pseudo security as used everywhere.