Timeline for How do browsers negotiate SSL/TLS connection parameters?
Current License: CC BY-SA 3.0
15 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 17, 2017 at 13:14 | history | edited | CommunityBot | replaced http://security.stackexchange.com/ with https://security.stackexchange.com/ | |
| Jul 27, 2015 at 8:41 | vote | accept | boleslaw.smialy | ||
| Jul 25, 2015 at 14:21 | history | tweeted | twitter.com/#!/StackSecurity/status/624947593253097473 | ||
| Jul 24, 2015 at 14:58 | answer | added | gowenfawr | timeline score: 4 | |
| Jul 24, 2015 at 13:54 | comment | added | boleslaw.smialy | @gowenfawr : we can focus at the two most popular browsers: Chrome and FF. | |
| Jul 24, 2015 at 12:52 | answer | added | Thomas Pornin | timeline score: 6 | |
| Jul 24, 2015 at 12:51 | history | edited | RoraΖ | CC BY-SA 3.0 | Clarified the first question |
| Jul 24, 2015 at 12:38 | answer | added | HorstKevin | timeline score: 3 | |
| Jul 24, 2015 at 12:31 | comment | added | gowenfawr | Is there a particular browser you're interested in? They use different mechanisms. | |
| Jul 24, 2015 at 12:26 | comment | added | boleslaw.smialy | @raz: I know that all of them important (needed). But I assume that in the code one of them is chosen as the first, then there is second, third and fourth. I believe that choosing TLSv1.2 with DES is more secure than SSLv3 with AES256. So the question is how it is implemented in the browser. | |
| Jul 24, 2015 at 12:23 | comment | added | boleslaw.smialy | @raz: thanks, but it does not exactly answers my questions. | |
| Jul 24, 2015 at 12:14 | comment | added | RoraΖ | A related question/answer regarding cipher suites | |
| Jul 24, 2015 at 12:07 | comment | added | RoraΖ | They're all important. Without one of them the connection could be insecure. | |
| Jul 24, 2015 at 11:58 | history | edited | RoraΖ | CC BY-SA 3.0 | deleted 49 characters in body |
| Jul 24, 2015 at 11:54 | history | asked | boleslaw.smialy | CC BY-SA 3.0 |