quote:
Originally posted by can16358p
Uhm, I have an idea maybe it'll help.
Don't all chat logs start as:
.--------------------------------------------------------------------.
| Session Start: Datte of the conversation |
| Participants: |
If we then can learn the encryption algorithm (which, I assume, only Patchou knows), we may find some possible values for the domain of the function. I mean; the data decrypted is known, and the encrypted part is known. Can't we find something with it? I know there won't be one result for this. But I've been thinking of catching something with these.
Logs don't neccesairly begin with that though, normally they do... but you can't be 100% sure if you have a log in your hands from someone else. Logs are just a bunch of characters, it doesn't matter what they contain. So to base your reverse engeneering on that is applying guesswork...
Anyways...
The encryption/decryption method is known, it isn't a secret. But without the password (as the key) you can do absolutely nothing with encrypted text/logs.
Also, as you said so yourself: the encrypted text is different each time (because the password was different), so what or how are you going to "catch" anything? With extremly basic "encryptions" (mind the quotes) where the encryption key is always the same you _could_ find something out, but reverse engineering encryptions (even if the encryption itself is dead easy) which use keys is as good as impossible.
So, no it isn't possible.... Moreover, what would the purpose be to "catch" anything? To know how the encryption method works? As said, that isn't a secret and is already know. But even knowing the encryption method, you can not decrypt anything without the proper encryption key (which is what the password is used for).
---------------------------------------------
It is absolutely NOT possible to recover encrypted log files WITHOUT the exact correct password.
It is abdolutely NOT possible to strip/catch/extract anything from the encrypted logs files in a way you would get even the smallest hint of the password; the password is NOT even stored!
No matter what things or ideas people might come up with: it is NOT possible...
---------------------------------------------
quote:
Originally posted by raceprouk
quote:
Originally posted by CookieRevised
The password isn't stored at all.
But you don't have to keep re-entering the password when new logs are created. I did find a value called 'LogEncryptionDataEx', which may not strictly be the password, but would be used to not require re-entering the password? Much like DataP is used for the Preferences Lock.
That doesn't have anything to do with this (except for the fact that the password _may_ be stored there, but that will not help at all):
We are obviously talking about (not) stored stuff in the log files itself to "break" the encryption. The registry wont help you at all in this, even if the password was stored unencrypted!!
People wanting to "recover" an encrypted log obviously haven't the (old) password stored in the registry (anymore), otherwise they wouldn't have the problem in the first place as Plus! would be able to open the log.
/ 
