Timeline for Attacks in SSL and SSH
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 7, 2021 at 6:47 | history | edited | CommunityBot |
replaced http://tools.ietf.org/html/rfc with https://www.rfc-editor.org/rfc/rfc
|
|
| Mar 21, 2017 at 4:30 | comment | added | user207421 | There is no such thing as the 'master key in SSL terminology'. There is a master secret, but it is not the session key. Those are derived from the master secret. | |
| Jan 2, 2013 at 21:57 | comment | added | Thomas Pornin | The sequence number is not encoded in the record itself; it is implicit. First record sent after activating the encryption+MAC has sequence number 0, second record has sequence number 1, and so on. Since sender and receiver agree "naturally" on the record order, there is no ambiguity (the inclusion of the sequence number in the MAC computation detects anything phony in that respect). See RFC 5246, end of section 6.1, and section 6.2.3.1. | |
| Jan 2, 2013 at 21:47 | comment | added | sanazz | Thanks a lot. Is sequence number both encrypted an MACed? | |
| Jan 2, 2013 at 19:40 | history | answered | Thomas Pornin | CC BY-SA 3.0 |