problem update 1.0.3 to 1.0.4

[kilburn]

Quote:Not worries about that. I'll do the necessary.
You talk about what passwords exactly ? Sql customers passwords ?

Mail passwords. When the keys change, they can't be read anymore because they're encrypted using the original keys. When ispcp tries to decrypt them with new keys, it gets random garbage (without noticing). Therefore, when the mail accounts are regenerated, they end up with random garbage passwords...

I can not think of a way to overcome this limitation. If the keys change, we are screwed in this front. It would be much better to fail fast and sound on this situation to prevent any future damage, asking the user to restore the keys files (all 3 of them) from any backup. In fact, I would check that all key files are correct before updating anything else (engine/ispcp-db-keys.pl, engine/messenger/ispcp-db-keys.pl and gui/include/ispcp-db-keys.php) if I remember correctly.