Thanks for the explanation, although it's bad news
.
I'm totally not into encrypting. My idea/hope came from the 'analogy' of the key and the keyhole. The password is used to 'unlock(decipher)' the file like a key is used to unlock the lock. Looking at the keyhole gives some idea about the key as well.
Then, another strategy.
If I limited the amount of characters for the password to let's say 10, and taking into account 2*26 + 10 possible characters, I end up with 8.53E+17 possible combinations. Take that in combination with a tool like:
Indicates whether the password is valid for specified encrypted file in archive.
[C#]
public bool IsFilePasswordValid(string fileName, string password);
[VB.NET]
Public Function IsFilePasswordValid(ByVal fileName As String, ByVal password As String) As Boolean
Description
Use IsFilePasswordValid to determine whether the password is valid for specified file in archive.
The fileName parameter specifies file name being tested.
The password parameter is a password to check.
(found on
http://www.componentace.com/help/fxc_guide/isfilepasswordvalid.htm)
Would a modern pc be up to that job, taking into account the password is only verified in that mini-log, as you described it?
quote:
Originally posted by CookieRevised
I think you're confusing things though.
What is being compared is a special string, not a password! The string is like an encrypted mini-log and is decrypted using the password you provide to check if the password is correct. This is done so the entire, often very big, real log doesn't need to be decrypted in order to see if the password is correct or not.
Only if this mini-log is properly decrypted Plus! will start to decrypt the real log. If that mini-log isn't properly decrypted you get the error that the password was incorrect.
The 'length' talked about in that thread is the length of this mini-log, not the length of the password. In that thread this "mini-log" is called "encrypted password check string".
The password, nor any clues about it, aren't stored anywhere.
Moreover, another thought. Any new chat log is encrypted using the same password, without having to provide that password every time. That means Plus! is keeping it somewhere?
