Seems you haven't got the right parts then. Normal UTF8 would just crash becuase of terminating %00 byte.Originally Posted by Squard
And to set a hardcoded SSO isn't bypassing it :=)
Seems you haven't got the right parts then. Normal UTF8 would just crash becuase of terminating %00 byte.
And to set a hardcoded SSO isn't bypassing it :=)
We did, :)
Then you just created an awesome move with normal utf8 that could never work D: Your better then sulake then D:
Im just using the BitConvertor & Some bypassing way to authenticate.
Has anyone attempted to convert this into Java, C++, or any other language?
Posted via Mobile Device
Who are they, and are they the same people from here aswell?Thanks to Privilege for the finds
-Tweeney
Sorry for encouraging the week-old bump, but this isn't crypto, this is encoding. Nobody has the new RC4 class afaik.
How sure are you? Even capostrikes emulator features RSA/RC4 (the RC4 never changed since me and Mike released it)
Does this actually means whe will have Horses etc soon??
Meh, I hope they will crack it soon.. really want something else as this old crypto to code (I know you can bypass blahblah, don't want it like that way ^^)
Really? I didn't figure anyone would figure out the functions for the new RSA handshakes. I'm not too up on the newest builds, I've got my head stuck in the Shockwave clients lately. Building up a really well-featured v13 atm.
Quick question. Would you consider this harder to understand over the old VL64 stuff?
I might have a go porting this over to C++. (I'm currently working on a VL64 encoder/decoder in native C++)
Posted via Mobile Device
This is easier, and faster than the B64/VL64 encoding.
Noticed that the equal function for writeUTF missed :)
