1 / 7

RFC6824bis draft-ietf-mptcp-rfc6824bis-00

RFC6824bis draft-ietf-mptcp-rfc6824bis-00. Alan Ford alan.ford@gmail.com. Rationale. Consensus to move to Standards Track Security Feedback from implementation experience. Security Issues. Thanks to Marcelo for the study Off-path ADD_ADDR hijack attack Medium risk, needs to be addressed

yamal
Télécharger la présentation

RFC6824bis draft-ietf-mptcp-rfc6824bis-00

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. RFC6824bisdraft-ietf-mptcp-rfc6824bis-00 Alan Ford alan.ford@gmail.com

  2. Rationale • Consensus to move to Standards Track • Security • Feedback from implementation experience

  3. Security Issues • Thanks to Marcelo for the study • Off-path ADD_ADDR hijack attack • Medium risk, needs to be addressed • DoS attacks • Can be mitigated outside of protocol • Eavesdropper of initial handshake • Accepted out of scope

  4. ADD_ADDR hijack • Solution: ADD_ADDR2! • We now add a HMAC of the new (addr, port) keyed against the sender’s connection key • As secure as MP_JOIN • Impact: • Addresses cannot be changed en route • Note that now no middleboxes can add addresses unless they have seen the initial handshake

  5. ADD_ADDR2 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +---------------+---------------+-------+-------+---------------+ | Kind | Length |Subtype| IPVer | Address ID | +---------------+---------------+-------+-------+---------------+ | Address (IPv4 - 4 octets / IPv6 - 16 octets) | +-------------------------------+-------------------------------+ | Port (2 octets, optional) | | +-------------------------------+ | | Truncated HMAC (8 octets) | | +-------------------------------+ | | +-------------------------------+ Figure 12: Add Address (ADD_ADDR2) Option

  6. Other updates • A number of textual clarifications • E.g. purpose of IDSN generation • Notably fallback • Note: fallback can be unidirectional but unlikely to be implemented as such • Plus the errata

  7. Next Steps…

More Related