There is no way to secure the password, here.
If i make an harder encryption, they will make an harder decryption, it would be a delay. That's it.
The password encryption is there mainly to prevent people from reading the password simply opening the text file.
A password saved on a computer has sense when people don't access your computer.
If other people has access to your computer, then the secure way to save a password is to save only an HASH of the password (i think linux does it).
This is sadly not suitable for our use. &RQ needs to send the entire password to the server. Otherwise the password saving would be useless.
If you need security for your password, simply don't save it.
And when &RQ will be opensource, the no-key encryption algorithm will be available to anyone. This is not security.
I thought a way to grant security with both
-saved password
-pc accessed by others
-sources open
The solution is to have a double password system.
The &RQ-password, any length, would be saved as an hash, and with this password we can crypt history and crypt the ICQ-password, that is weak, limited to 8 chars.
This is a secure way IMHO.
Here is 7AM and i didn't sleep yet |) i hope i said no nonsense
