Timeline for Are public/private keys needed when using Diffie-Hellman with TLS
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 6, 2017 at 3:34 | vote | accept | 1110101001 | ||
| Jun 6, 2017 at 3:34 | comment | added | 1110101001 | Ah that makes sense. So DH has to be combined with authentication by using RSA (or other asymmetric) for signing and verification. However, if you were to do straight RSA key exchange the authentication is implicitly built in since anyone who didn't have the private key couldn't decode the master key that was sent. | |
| Jun 6, 2017 at 3:11 | comment | added | Steffen Ullrich | @1110101001: First: this check of building the trust chain requires the public key of this CA to verify the signature as described in my answer. Second: this check is not enough, one also needs to make sure that the server actually owns the certificate (which means has the private key) because otherwise some man in the middle could just present the servers certificate. | |
| Jun 6, 2017 at 3:05 | comment | added | 1110101001 | I thought trust was established by means of checking whether the issuing authority is derived from a root CA? | |
| Jun 6, 2017 at 2:46 | history | edited | Steffen Ullrich | CC BY-SA 3.0 |
added 74 characters in body
|
| Jun 6, 2017 at 2:14 | history | answered | Steffen Ullrich | CC BY-SA 3.0 |