[Workshop] Updating code to work post client V.5018

Well actually I'm at a small stump, but I'm working on it ;)

im now <-> close =D, got to compute the clients public key and im done =P

this sounds very good but i have no clue what to do even with your guide

Bump

I can't believe so few people have interest in this. This is perhaps the most important thread in this whole section and nobody cares enough to keep it alive?

-bump

I will bump it coz i know its important but the majority of people i the forum dont know what this is about, how to implement it or use it (including me)

Lets try something else than bumping.

#Sticky :)

BUMP

Quote:

Originally Posted by Beta Limit I will bump it coz i know its important but the majority of people i the forum dont know what this is about, how to implement it or use it (including me)

/agreed

@unknownone
maybe you can explain it little bit more:P

He's basically given out the code already. :P

Quote:

Originally Posted by tanelipe He's basically given out the code already. :P

Yeah i could copy and pate this and hope for the best but i wanna know how to work with it properly. I know that teaching us a bit more about it may lead to tonnes on 5018+ servers but there already is (TQ binary stuff). I Personally want to go to the best patch but if i don't understand anything in the block of code then i have no chance. I could wait till i know wtf is going on here but by then it will probably be released in a source.

P.S. - Nice one for stickying

There's really nothing else I can help you with - everything is here. I already told you, I'm not giving any implementation specific code, so don't expect me to take a look at LOTF (or w/e you use) and tell you how to fix it. Why are you running a server if you don't understand the very basics of how it works in the first place?

Simply put - you need to understand about encryption. What it does, why it's there, and where it is. Whatever server you're already using has it's own cryptography, because it existed before patch 5018, this just needs replacing with the new method, that's all. (although, the login server should remain unchanged). Read up on cryptography - wikipedia is the place to start.
Before you read up on encryption, you might wanna read up on networking, TCP, binary data, streaming, serialization/marshalling etc. They're the basic components that make up your server, if you don't understand them, you won't understand my code.

Basically, you replace the cryptography module, implement a check within your server to decide whether the packets you're sending to/receiving from are the first ones (the key packets already described), if not, enter your normal check for the packet type. You need to modify your packet splitting and sending code to compensate for the TQServer, TQClient padding too. I can't help you with that - because you don't appear to even know how your own server does it - but I can tell you this - if you're using code from this forum, you're doing it badly.

Quote:

Originally Posted by unknownone There's really nothing else I can help you with - everything is here. I already told you, I'm not giving any implementation specific code, so don't expect me to take a look at LOTF (or w/e you use) and tell you how to fix it. Why are you running a server if you don't understand the very basics of how it works in the first place? Simply put - you need to understand about encryption. What it does, why it's there, and where it is. Whatever server you're already using has it's own cryptography, because it existed before patch 5018, this just needs replacing with the new method, that's all. (although, the login server should remain unchanged). Read up on cryptography - wikipedia is the place to start. Before you read up on encryption, you might wanna read up on networking, TCP, binary data, streaming, serialization/marshalling etc. They're the basic components that make up your server, if you don't understand them, you won't understand my code. Basically, you replace the cryptography module, implement a check within your server to decide whether the packets you're sending to/receiving from are the first ones (the key packets already described), if not, enter your normal check for the packet type. You need to modify your packet splitting and sending code to compensate for the TQServer, TQClient padding too. I can't help you with that - because you don't appear to even know how your own server does it - but I can tell you this - if you're using code from this forum, you're doing it badly.

Thanks alot ill begin reading up on it.

Wow,You went public with this info.I clicked on the PS section for some reason and seen a thread started by you and knew I had to check it out.Thank for posting.

I love this, i'll try figure out what all these things mean and then i'll try understand your code, unknownone - and then i'll try and make a nice server ;) ty ty

How meny ppl have got this to work?Proxy side of it..?was it with a QO source or A fresh build?(Im not going to ask for the source,Im just wondering..btw)
I'm going to try it out,Should take me a while,I havent touched a computer in like 4 months(apartment burnt down :( ,and I just got a "new" computer/internet).
Any reason this is in the PS section and not the programming section?I never checked the PS section and almost missed this thread!