Giter Club home page Giter Club logo

continuity's Introduction

An Apple Continuity Protocol Reverse Engineering Project

A dolphin shooting WiFi from an Uzi

This is a project that seeks to understand the format and structure of Apple's proprietary "Continuity" BLE protocol. It is a continuation of work conducted at the US Naval Academy during the fall of 2018 and spring of 2019, culminating in a paper, Handoff All Your Privacy – A Review of Apple’s Bluetooth Low Energy Continuity Protocol, at the 2019 Privacy Enhancing Technologies Symposium (PETS 2019) July 16–20, 2019 in Stockholm, Sweden and most recently in a talk at ShmooCon 2020 (check out our website's presentations section for the slides). While our paper investigates myriad privacy concerns arising from Apple's use of the Continuity protocol across its ecosystem, including the ability to track devices despite the use of randomized BD_ADDRs, this project is focused on the reverse engineering of the Continuity protocol we began in "Handoff All Your Privacy".

In particular, we were the first to describe the wire-format for many of the following Continuity message types, and continue to update known field values as new versions of iOS/macOS emerge. All of the other message types, and many of the field meanings, were discovered by Guillaume Celosia and Mathieu Cunche in Discontinued Privacy: Personal Data Leaks in Apple Bluetooth-Low-Energy Continuity Protocols.

Wireshark Dissector

The latest Wireshark dissectors can be found here, as well as installation instructions here.

Contributing Dissector Updates

Apple updates Continuity frequently, adding new messages and field values. Help keep up to date by dropping us a line via our protonmail.com email address, mailbox FuriousMAC.

ShmooCon 2020

The Continuity reverse engineering effort and Wireshark dissector were presented at ShmooCon 2020 on January 31, 2020. The slides from the presentation are here. The full talk is also posted on YouTube.

Citations

continuity's People

Contributors

gigaryte avatar phrj avatar samteplov avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

continuity's Issues

Add message to the AirPods Pro 2 ?

With AirPods Pro 2, if you have engraving the case with Apple, the message is visible on the popup.

Is this a way to read the information ? Is there a specific protocol for that ?

nearby-info correct byte-type for Action-code?

Action-code is stated as uint8 (a full byte)?,
but deciphered only as 4-bit.

shouldnt it be type-marked as something like "uint4" ?

or clearly stated whats the high/low-part (from left to right/right to left?) of this divied byte?
maybe it could be clarified in clearly showing whats the low and high half-byte as nibbles?
https://en.wikipedia.org/wiki/Nibble#Low_and_high_nibbles

(the other half of the full byte (for the action-code) looks like as the 4-bit status-flags.)

image

Nearby-info structure different than in original paper

the document in the github here shows a different structure than in the original paper.
how come? what is the source of the github document here? some updates?

also the numbering 1-31 seems to be BITS, but the BT-Advertisment can not be longer than 31 BYTES?

image
https://petsymposium.org/2020/files/papers/issue1/popets-2020-0003.pdf

vs

image
https://github.com/furiousMAC/continuity/blob/master/messages/nearby_info.md

the 2019 Paper shows the byte for action code as nibbles , and here is one half location sharing, not status
image
https://petsymposium.org/2019/files/papers/issue4/popets-2019-0057.pdf

TxPower on Nearby Info

It seems like TxPower in the Nearby Info advertisements is not really TxPower and is instead a device type.

Apple Watches always seem to be 26 (0x1a). Have you been able to make any rhyme or reason to what TxPower means?

AirPlay source message has a purpose.

From what I've observed the AirPlay source message causes an AirPlay target to(if supported) start it's AWDL interface. I'd suggest further testing and then adjusting the description.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.