Such updates do happen on their own as well, even without any client updates.kLabMouse wrote:Deprecated packets cause DC
a few questions for Fr3DBr & kLabMouse
Moderator: Moderators
-
- Developers
- Posts: 1798
- Joined: 05 Dec 2008, 05:42
- Noob?: Yes
Re: a few questions for Fr3DBr & kLabMouse
Re: a few questions for Fr3DBr & kLabMouse
It's because of The Server nature. Looks like from the last time, they started to add handlers for old and new packets.EternalHarvest wrote:Such updates do happen on their own as well, even without any client updates.kLabMouse wrote:Deprecated packets cause DC
Old Packets Mark user as "Bot". so they can ban him without any visual Reason.
bRO at this point is more aggressive! They just kick and ban!
Re: a few questions for Fr3DBr & kLabMouse
Yeah and they guarantee no possible old versions of client gonna work, by changing the encryption keys every update.
So if something, uses a 'deprecated' packet, it is detected.
So if something, uses a 'deprecated' packet, it is detected.
-
- Super Moderators
- Posts: 801
- Joined: 06 May 2008, 12:47
- Noob?: No
Re: a few questions for Fr3DBr & kLabMouse
Cool, tbh, I've always wanted to learn how to do such things but never really knew where to start.kLabMouse wrote:OK. Well this was something like this:
1) Client.exe -> Dump memory
2) Locate Networking Functions
3) Locate Encryption
4) Reverse it, see where it innit's and how it works
5) Make a little .asm file that output's key's to check against perl implementation that FR3DbR made
6) Fail again Because of Numeric Int overload
7) Make a solution using BigInt
8) Fail Again because of Deprecated packets and Packet ID randomizations
9) Diff RecvPackets to get the Randomization, Like I did back in old times, when I was working with our old Developer: heero.
10) Bingo, now it's more stable
11) Find out, that Deprecated packets cause DC and possible Ban. Damn
12) FR3DbR Implements new functions and changed packet ID's. Good to go, wait for next version
13) Make some HEX patterns to locate functions more easy.
14) On new .exe -> Goto Step (1), Repeat only necessary steps.
Implementation itself is no problem, the hard part is finding out what the client does, so you can mimic it.
If only some kind of indepth walktrough explained this process (as an example) with every step in detail, used tools, rationale etc...
That would be awesome because it would provide some kind of "entry point" into the world of cracking the RO client's network handling.
One ST0 to rule them all? One PE viewer to find them!
One ST_kRO to bring them all and in the darkness bind them...
Mount Doom awaits us, fellowship of OpenKore!
One ST_kRO to bring them all and in the darkness bind them...
Mount Doom awaits us, fellowship of OpenKore!
Re: a few questions for Fr3DBr & kLabMouse
Oh. IC. Well I did this long time ago. Remember? thus Packets that we tried to gather their internal structures?Technology wrote: Cool, tbh, I've always wanted to learn how to do such things but never really knew where to start.
Implementation itself is no problem, the hard part is finding out what the client does, so you can mimic it.
If only some kind of indepth walktrough explained this process (as an example) with every step explained in used tools etc...
That would be awesome because it would provide some kind of "entry point" into the world of cracking the RO client's network handling.
And used tools are simple: IDA + PE Editor (to just Dump the process) + MS Network Monitor
-
- Super Moderators
- Posts: 801
- Joined: 06 May 2008, 12:47
- Noob?: No
Re: a few questions for Fr3DBr & kLabMouse
Maybe a program can be made that extracts the encryption keys?Fr3DBr wrote:Yeah and they guarantee no possible old versions of client gonna work, by changing the encryption keys every update.
So if something, uses a 'deprecated' packet, it is detected.
And also a plugin for kore that detects that there is a new client available? (warning kore that it is unsafe to log in)
One ST0 to rule them all? One PE viewer to find them!
One ST_kRO to bring them all and in the darkness bind them...
Mount Doom awaits us, fellowship of OpenKore!
One ST_kRO to bring them all and in the darkness bind them...
Mount Doom awaits us, fellowship of OpenKore!
-
- Super Moderators
- Posts: 801
- Joined: 06 May 2008, 12:47
- Noob?: No
Re: a few questions for Fr3DBr & kLabMouse
Hmm, yes I remember you were doing that.kLabMouse wrote:Oh. IC. Well I did this long time ago. Remember? thus Packets that we tried to gather their internal structures?Technology wrote: Cool, tbh, I've always wanted to learn how to do such things but never really knew where to start.
Implementation itself is no problem, the hard part is finding out what the client does, so you can mimic it.
If only some kind of indepth walktrough explained this process (as an example) with every step explained in used tools etc...
That would be awesome because it would provide some kind of "entry point" into the world of cracking the RO client's network handling.
And used tools are simple: IDA + PE Editor (to just Dump the process) + MS Network Monitor
However, I've never used any RE technique, was just reading the eA code and using wireshark when trying to understand a packet's structure.
One ST0 to rule them all? One PE viewer to find them!
One ST_kRO to bring them all and in the darkness bind them...
Mount Doom awaits us, fellowship of OpenKore!
One ST_kRO to bring them all and in the darkness bind them...
Mount Doom awaits us, fellowship of OpenKore!
Re: a few questions for Fr3DBr & kLabMouse
This is not too hard =P, but i do work like kLab, so my time is the main problem .Technology wrote:Maybe a program can be made that extracts the encryption keys?Fr3DBr wrote:Yeah and they guarantee no possible old versions of client gonna work, by changing the encryption keys every update.
So if something, uses a 'deprecated' packet, it is detected.
And also a plugin for kore that detects that there is a new client available? (warning kore that it is unsafe to log in)
I know i am not doing 1% of all what you did here, but i try to do what i can in my spare time =).
-
- Super Moderators
- Posts: 801
- Joined: 06 May 2008, 12:47
- Noob?: No
Re: a few questions for Fr3DBr & kLabMouse
Hey, every contribution kore can get is awesome.Fr3DBr wrote:This is not too hard =P, but i do work like kLab, so my time is the main problem .Technology wrote:Maybe a program can be made that extracts the encryption keys?Fr3DBr wrote:Yeah and they guarantee no possible old versions of client gonna work, by changing the encryption keys every update.
So if something, uses a 'deprecated' packet, it is detected.
And also a plugin for kore that detects that there is a new client available? (warning kore that it is unsafe to log in)
I know i am not doing 1% of all what you did here, but i try to do what i can in my spare time =).
Btw, I haven't done much around here as of lately, guess what, same problem.
I think that if anything were to draw my attention back to kore during the little free time i enjoy, it would be the challenge of learning how to do RE.
One ST0 to rule them all? One PE viewer to find them!
One ST_kRO to bring them all and in the darkness bind them...
Mount Doom awaits us, fellowship of OpenKore!
One ST_kRO to bring them all and in the darkness bind them...
Mount Doom awaits us, fellowship of OpenKore!
Re: a few questions for Fr3DBr & kLabMouse
By today in the afternoon or evening, i must have one more update/protect attempt of bRO solved .