[What] is this part of DH Key Exchange

[badguy4you]

1- P&G are public keys that is known by server and client
2- P&G Are the public keys that actually make the secret shared answer
3- idk
4- ? what you mean
5- P&G i think must be the same at server and client
6- as Zero said . .. .

[Zeroxelli]

Originally Posted by romeoromeo

let me try to ask it in yes/no questions .
1- are P&G known by server only ?
2- does server send P and G and pubkey ?
3- is client have P & G saved somewhere if server did not send any ?
4- is P and G are send on connection request ? (or p &g request ?? )
5- can i tell server to use diff P and g ?
6- dkhey is used to set encryption ? !! is there any encryption b4 it

I already answered that.

Originally Posted by Zeroxelli

P and G are decided based on data sent to/from the server, and vice-versa. Based on the "secret" of the client and server being merged, you get your P and G. In most cases, the "secret" is your key.

To 3, no. It's decided based on data from both the server AND the client.

To 4, connection request (technically "secret exchange")

To 5, yes.

To 6, yes it is used to set up the encryption. No, there shouldn't be.

[romeoromeo]

Originally Posted by Zeroxelli

You can always check if it makes a difference by writing 23 blank bytes instead of the pad and junk. More likely than not, it won't, though.

23 only?? :O i thought it was lil more than that 26 or 28 i do not remember .(including the byts for length ?? )

[Zeroxelli]

According to what was posted, pad is 11 bytes and junk is 12 bytes. Thus, 23 bytes. That's all I'm going on.

[romeoromeo]

Originally Posted by Zeroxelli

I already answered that.



To 3, no. It's decided based on data from both the server AND the client.

To 4, connection request (technically "secret exchange")

To 5, yes.

To 6, yes it is used to set up the encryption. No, there shouldn't be.

yes i know you have answered that . , but the answers are conflicted to what i know . is why i ask again . what i know is . there is two pecies of information known . and send publicly . which is P and G and those have to be same for sender and reciever .
but who have them ? or who send them ? or how to decide them no ideal (1)
and then sender and reciever .. pick random key .. do the mix and send the publick hey . then both sender and reciever use the publick hey to generate the secret key ... >>>> anything wrong here ? <<<<<<<<<<<
if there is nothing wrong , it means p and G and public keys(result of mex) are general send
but the private key and secret key never sent .

[Zeroxelli]

Originally Posted by romeoromeo

yes i know you have answered that . , but the answers are conflicted to what i know . is why i ask again . what i know is . there is two pecies of information known . and send publicly . which is P and G and those have to be same for sender and reciever .
but who have them ? or who send them ? or how to decide them no ideal (1)
and then sender and reciever .. pick random key .. do the mix and send the publick hey . then both sender and reciever use the publick hey to generate the secret key ... >>>> anything wrong here ? <<<<<<<<<<<
if there is nothing wrong , it means p and G and public keys(result of mex) are general send
but the private key and secret key never sent .

There's a key that the client and server both know, that is their common point. Then each of them have their own secret, which is "mixed" with the common point. The result of that mixture is sent to the opposite (server sends to client, client sends to server. Hence, it's an exchange). That is then "mixed" with their secret again. The result is known as their common secret, which is the same for server and client.

[badguy4you]

I think epvp has a trouble with the host ... always @ 5:30PM it get Database error

and from time to time the whole site is down whats happening

[Zeroxelli]

Originally Posted by badguy4you

I think epvp has a trouble with the host ... always @ 5:30PM it get Database error

and from time to time the whole site is down whats happening

It's a common thing with ePvP. You get used to it.

[badguy4you]

i think its overload ...

[Zeroxelli]

Could be, most likely just ePvPs host.

[badguy4you]

Agree

[romeoromeo]

Originally Posted by Zeroxelli

There's a key that the client and server both know, that is their common point. Then each of them have their own secret, which is "mixed" with the common point. The result of that mixture is sent to the opposite (server sends to client, client sends to server. Hence, it's an exchange). That is then "mixed" with their secret again. The result is known as their common secret, which is the same for server and client.

i know that client and server both know . my question is HOW they know . you started from "they both know it" .... most of my questions are "Before they know it" . how to know it . and i do not mean the final result which is the secret key .... i mean the begaining keys which are known as P and G ....

[Zeroxelli]

Originally Posted by romeoromeo

i know that client and server both know . my question is HOW they know . you started from "they both know it" .... most of my questions are "Before they know it" . how to know it . and i do not mean the final result which is the secret key .... i mean the begaining keys which are known as P and G ....

I just told you, their common point is the key that the both know BEFORE HAND. I don't think you understand what P and G truly represent. Take another look at this description.

[romeoromeo]

Originally Posted by Zeroxelli

I just told you, their common point is the key that the both know BEFORE HAND. I don't think you understand what P and G truly represent. Take another look at this description.

well ... if they both know it why would i do such a packet to send them again over , if we both already have them . like that packet in first page of this threat ... which is >
public byte[] GeneratePacket(byte[] ServerIV1, byte[] ServerIV2, string P, string G, string ServerPublicKey)
.......
its thier common point ,, how it become common point ? by code ? or packet ? i hope you understand my question .
in wiki page ... its yellow color . isnt ? how did they know its yellow !!!!!!!!!!!

any idea ?

[Zeroxelli]

Originally Posted by romeoromeo

well ... if they both know it why would i do such a packet to send them again over , if we both already have them . like that packet in first page of this threat ... which is >
public byte[] GeneratePacket(byte[] ServerIV1, byte[] ServerIV2, string P, string G, string ServerPublicKey)
.......
its thier common point ,, how it become common point ? by code ? or packet ? i hope you understand my question .
in wiki page ... its yellow color . isnt ? how did they know its yellow !!!!!!!!!!!

any idea ?

Because, the common point isn't the key itself, it's just the beginning point. And it's by code. Yellow is just a representation, it has no color.