quote:
Originally posted by WDZ
he doesn't seem to have a problem with this thread
TBH, I was extremely surprised reading that...
quote:
Originally posted by solus
Attached is a tool to encrypt or decrypt log files
Your tool does not work!; it doesn't start...
--------
PS: The explanations are indeed a bit confussing, but I'm not going to explain it in a better way to keep this somewhat away from "script kiddies" though
Though:
quote:
Originally posted by solus
This is usually 13
It is always 13. Though, nothing says this could be changed in the futur. Although I doubt it for backward compatibility reasons.
quote:
Originally posted by solus
I discovered that for some reason, the password is scrambled, and that the password is unicode (2 bytes).
The password is "scrambled" for better security (so the API isn't called with the text password in plain sight). Although that didn't kept you from discovering it though, hehehe
But more importantly, the password is unicode because you can enter unicode characters. Remember that this also has implications of how the password is scrambled. Your pseudo-code is correct
(appart from "0 to length" which should be "length-1") although lacks the big notice that all characters must be interpreted as unicode characters, as that is what they are, not as ascii characters.
(and this is also where one of those bugs were in old Plus! versions in regards to the "changing password")
PS2: And don't forget to destroy the handles of the key, hash and crypto provider.