I used a few "password recovery" software to test security weaknesses of my software. Almost all of pass recovery programs showed me my email passwords on the Bat.
|
I used a few "password recovery" software to test security weaknesses of my software. Almost all of pass recovery programs showed me my email passwords on the Bat.
|
|
|
|
|
|
No I dont mention only showing asresiks. You can do that of course but you can also see mail passwords on bat without opening the bat.
|
|
|
|
|
|
If you dont believe me, i can tell you which programs I used. Test it yourself.
|
|
|
|
|
|
account setting is stored in binary file ACCOUNT.CFN and both login and passw are encrypted and not stored in plaintext.
|
|
|
|
|
|
Thank you for pointing that out! In earlier versions of The Bat!, e.g. 1.62, account passwords were encoded in a form of Base64-encoding in the account configuration file. This encoding is not an encryption, it is simply means of avoiding storing them in plaintext easily readable form. In later versions, the passwords were not encoded in the configuration file, because we’ve implemented the OTFE encryption to protect the configuration data. Encoding the passwords may give the false sense of security, thus we didn’t encode them. However, we may encode them in future versions using the same algorithm as in earlier versions of The Bat!
OTFE does only protect the data on the disk, not in the computer’s memory. For example, if somebody physically steals the storage media while the computer is turned off, it would not be reasonable to get the original data, e.g. account password, due to computational difficulties of decrypting an RC2 128-bit chipher without knowing the key. However, when the legitimate user have started The Bat! With OTFE encryption, the “asterisk” issue would not help anyway, since the configuration data has been loaded into the computer memory and can be read by a malicious software. To resolve the issue of POP3/SMTP password leaks, we recommend using hardware CRAM-MD5 authentication. You can read more about hardware authentication at |
|
|
|
|
|
I would advise [if your SMTP server permits] to use the passwords on a token along with the RFC2095 (MD-5 CRAM-HMAC) authentication.
winXP-SP3 Pro, the Bat! v4.0.38
|
||||
|
|
|
|||