Can I use different company ID in the payload?

Open
#54 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
25/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Tech stack
python, swift
Domain
documentation, networking, reverse-engineering

Research direction

Start with Firmware/Linux_HCI/HCI.py around line 15 and OpenHaystack/OpenHaystack/HaystackApp/Bluetooth/Advertisement.swift around line 38. Compare how the company ID is placed in advertisements and checked during nearby scanning, then verify whether reports depend on 0x4c00. Done means documenting the supported behavior and explaining why another ID stops reports.

Written by the indexing model from the issue text.

Description

question

As I can see, all the beacon examples use 0x4c00 (Apple) as a company ID in the advertisement payload.

There is also some code that checks if company ID equals 0x4c00, but only for nearby scanning.

My question: is it necessary to use 0x4c00?

I've tried changing it to 0x0100 and reports stopped appearing in OpenHaystack. Is it Apple's limitation or my fault?
If it's Apple's limitation, how would 3rd-party MFi beacons work then? I bet they won't use Apple's company IDs in adv packets.

Dominant language
Swift
Stars
13.6k
Forks
681
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from seemoo-lab/openhaystack

All issues in seemoo-lab/openhaystack

Similar issues

More Swift issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.