mirror of
https://github.com/malmeloo/FindMy.py.git
synced 2026-04-18 06:54:01 +02:00
docs: fix page reference
This commit is contained in:
@@ -7,7 +7,7 @@ by surrounding iDevices, and how generated location reports can be retrieved.
|
||||
```{note}
|
||||
While official AirTags (and compatible 3rd party tags) use the same principles as described
|
||||
in this document, they also offer a key rotation feature. To learn more about
|
||||
how this works, please check out the dedicated [AirTags](#10-AirTags) page.
|
||||
how this works, please check out the dedicated [AirTags](#11-AirTags) page.
|
||||
```
|
||||
|
||||
## Overview
|
||||
@@ -26,7 +26,7 @@ said reports using the private key, users are able to track their devices withou
|
||||
|
||||

|
||||
|
||||
*An overview of the FindMy-network. Source: [SEEMOO-LAB](https://www.petsymposium.org/2021/files/papers/issue3/popets-2021-0045.pdf)*.
|
||||
_An overview of the FindMy-network. Source: [SEEMOO-LAB](https://www.petsymposium.org/2021/files/papers/issue3/popets-2021-0045.pdf)_.
|
||||
|
||||
Fetching (encrypted) location reports still requires an Apple account. It is worth noting however, that anyone can download
|
||||
anyone else's location reports for any of their devices; however, due to the encryption scheme discussed above,
|
||||
@@ -34,8 +34,7 @@ doing this would be rather useless as none of the retrieved reports could be dec
|
||||
to operate without being linked to a specific Apple account. The below dependency diagram visually explains how this entire
|
||||
system hinges on the availability of the private key; without it, location reports could not be retrieved and decrypted.
|
||||
|
||||
|
||||

|
||||
|
||||
*A dependency diagram of data in the network. An arrow pointing from A to B means that in order
|
||||
to retrieve B, we first require A.*
|
||||
_A dependency diagram of data in the network. An arrow pointing from A to B means that in order
|
||||
to retrieve B, we first require A._
|
||||
|
||||
Reference in New Issue
Block a user