EOSERV Forum > Programming > Proper Packet Protocol
Topic is locked.
Page: << 1 2 3 4 >>
Proper Packet Protocol
Author Message
Post #166515 Re: Proper Packet Protocol

Am I understanding this correctly?

 


Client:

EmultiE: Value generated, encrypted

EMultiD: Value sent to server, server decrypts

Server:


EmultiE: Generated, encrypted with password (Password is in server files, correct?)

EmultiD: Generated, sent to client, client decrypts

---
Hail Satan!
12 years, 43 weeks ago
Post #166545 Re: Proper Packet Protocol

With public/private key cryptography (which I assume is the method of encryption you're talking about) a server would keep a "private key" which only the server knows and the clients would all have a "public  key" which their data is encrypted with. Only the server will be able to decrypt the message because it's the only data source of the private key that can decrypt the message for that specific encryption. The other way around would be that every client has a different "private key" so the server (if I'm understanding this right, correct me if I'm wrong) will store all of the public keys to encrypt the data for the different clients and so any information the server is sending out to specific clients cannot be decrypted by any other clients that the data wasn't meant for as they don't posses the correct decryption key. 

Another scenario could be that source A could encrypt the data with their private key and every source could decrypt it with source A's public key. This is used to verify the source of the information (companies like adobe use this kind of encryption so their end users know that any software updates etc are legit). 
---
If money doesn't grow on trees, then why do banks have branches?
12 years, 43 weeks ago
Post #166551 Re: Proper Packet Protocol


@danscott, close except that both have their own private keys. Server contains all the clients public keys. Clients contain the servers public key.

The technical term is asymmetric encryption for this specific thing if you want to learn more about it on google.

 

@omen, no, thats pretty wrong. Both keys are generated by and the public is sent to the receiver. The receiver uses the public key to decrypt messages but uses its own private key to send messages which is decrypted with the recievors public key.

---
Andrewbob - I would be on the fucking copter of rofls

Programmer, Web Developer, and Graphics Designer
12 years, 43 weeks ago
Post #166978 Re: Proper Packet Protocol

The main thing is to protect your clients executable from debugging; otherwise reverse engineers will be able to find the encryption or obfuscation routine.

---
https://www.youtube.com/watch?v=d_DFVzxsEUc
12 years, 42 weeks ago
Page: << 1 2 3 4 >>
Topic is locked.
EOSERV Forum > Programming > Proper Packet Protocol