[Release] Current Cryptography

Content Removed.
I decided that this forum doesn't deserve or appreciate my work and I am not going to support it by releasing/maintaining my work and generating traffic for it.

Interesting. I had been considering doing a tinnyyy bit of work with the new client so if I ever decide to go ahead with it, this'll be useful.


I assume the legit password cryptography is still private? Not that it really matters seeing as there's a public bypass for it.

Quote:

Originally Posted by pro4never I assume the legit password cryptography is still private? Not that it really matters seeing as there's a public bypass for it.

Not anymore...

Secure Remote Password protocol - Wikipedia, the free encyclopedia

But they are not using it as is the made some major changes to the implementation... I'm pretty sure they edited WOW's implementation and used it on their servers.

I really can't tell you much about it because i didn't implement it on the server side i only reversed the client side implementation to use it in my clientless bot project which i never finished... And it still laying around somewhere on the hard drive.

"taban lak cristiano, qalbi el sagheer la yat7mal :D"
thanks adel

Thanks friend you is the best...

Thanks a lot man.

Thank you

Thanks Angelius

Quote:

Originally Posted by { Angelius } Not anymore... Secure Remote Password protocol - Wikipedia, the free encyclopedia But they are not using it as is the made some major changes to the implementation... I'm pretty sure they edited WOW's implementation and used it on their servers. I really can't tell you much about it because i didn't implement it on the server side i only reversed the client side implementation to use it in my clientless bot project which i never finished... And it still laying around somewhere on the hard drive.

Yeah, they do the sha1-interleave.

plus there is a bug in any c# implementation that stops it from working half of the time, well tq bugged the official implementation should i say.

Quote:

Originally Posted by Ultimation plus there is a bug in any c# implementation that stops it from working half of the time, well tq bugged the official implementation should i say.

Could be uninitialized variables :p When I reverse TQ's file formats, I often face 0xCD values which correspond to Visual Studio memory indicator... So, shitty implementations on their side...

u got the updated spawn packet (0x271E), they added something new now my entites arnt showing, cnat find the new values they added /removed?

nevermind got it, 2 new bytes before x,y

this is the update for ur evolution project? if so, the only 16 bit word in ur source code which looked like "the game key" to me was in this line:
#pragma comment(linker,"/manifestdependency:\"type='win32' name='Microsoft.Windows.Common-Controls' version='6.0.0.0' processorArchitecture='x86' publicKeyToken='6595b64144ccf1df' language='*'\"")


when i try to change that word with the new one, i get errors while debugging ( i dont even know what #pragma comment function is). so the general question is, where in ur source code should i update the new encrypt key?
Tnx

Quote:

Originally Posted by dusica ( i dont even know what #pragma comment function is)

it`s not a comment, it`s used to send directives to the compiler. It can also be used for other neat shit like disabling some warnings during the run time.

so that means i should insert the new encrypt key somewhere else in his source code i guess ... only if i had a little more knowledge ... Thank you for that info