network profile
| bio | website | le-moulin-studio.com |
|---|---|---|
| location | Taipei City, Taiwan | |
| age | 35 | |
| visits | member for | 1 year, 1 month |
| seen | Mar 21 at 10:16 | |
| stats | profile views | 1 |
FOSS developer - https://github.com/green-coder
|
Apr 8 |
comment |
My custom handshake In my application, I don't want Eve to know who is talking to who. |
|
Apr 8 |
comment |
My custom handshake 1) Now I see which 2 shared secrets you meant. I will consider your suggestion, thx. 4) Now I see what you mean. I think I am using a hash of K1/K2 as IV. |
|
Apr 8 |
comment |
My custom handshake I didn't use SSL because it seems that the server is giving away its public key during the handshake. 1) I don't understand which 2 shared secrets you mean. 2) I don't understand why the first 16 bits of those keys will be the same, I didn't experiment that issue. 3) I am using the standard RSA signature, and the timestamp has a fixed size. 4) I don't understand which IV you mean. |
|
Apr 8 |
comment |
My custom handshake And now, does it meet the requirements? |
|
Apr 7 |
comment |
My custom handshake You are right. I will edit my question to specify them. |
|
Apr 7 |
comment |
My custom handshake @IlmariKaronen: You guessed correctly, the 2 bytes are for this usage. For your second note, you are right, and in my implementation I used a SHA-256 hash of K2 as the key of a AES-256 cipher to encode the hash of C's signature. I just forgot to write it in my documentation - sorry. |
